I have successfully upgraded my companies corporate intranet from 3.0.13 to 3.3.7 in my test environment. Now my attention is shifting to 4.4.0. Since my production site is still 3.0.13, and I have been tasked with upgrading to 4.4.0 anyway, I thought I should post a few facts about my situation and ask some questions before diving in.

Here is the twist: the technical lead I replaced did not follow any standard development practices. It seems that everything he developed was a 'flavor of the day'. The tables, stored procedures, and files all follow different naming conventions (if any); nothing has an actual deployment package; and his most recent code was never checked into our Vault repository. I need to bring the database and code back into common development practices for my team. For instance, the use of standard table and stored procedure prefixes would be nice... So I need to upgrade from no prefixes to 'dnn_' prefixes on all the core tables and stored procedures. I really don't want to change everything manually, and we don't have any tools (at present) to assist me with the task. (I am rallying for AdeptSQL w/DataDiff.).

Does a valid upgrade path exist from 3.0.13 to 4.4.0?

Can the upgrade process help me with the core database changes? 

Can the upgrade process help me address the problem of adding the 'dnn_' prefix in the database schema.

I would also like to gain the integraded/updated core Authentication module. I am still using a version from before the module became a core module, so its aging, is not a part of the admin menu, and is missing much of the newer authentication functionality - but it works as is...

Thank you for your comments,

Cheers!