Upgrade NAV5SP1 to NAV2013

Prerequisites:

The below database objects are required to go upgrade NAV5SP1 to NAV2013.

NAV5SP1 Base Database

NAV5SP1 customer Database

NAV2009R2 Base Database

NAV2013R2 Base Database

To Upgrade from NAV5Sp1 to NAV2009R2 Data Upgrade is not necessary, follow the steps below

·        Merge the customized objects

·        Open/Convert the database in Nav 2009 R2

·        Delete all the objects except tables

·        Cleanup the data which are not required. Like some add-ons might not require to upgrade,etc.

·        Import the latest merged Objects.

·        Transform Forms to page using Transformation Tool, if we find any matrix forms then we need to convert those matrix form to pages manually.

·        Customized Reports needs to be converted to RDLC

·        Compile the objects and resolve the compilation errors

1.   Update the Application Code.

Any customization in the customer’s old database must be implemented in the       new database

2.   Export all the objects in the new customized Microsoft Dynamics NAV 2013 database to an object file: objects.fob.

3.   Prepare for the data conversion.

a.   Make sure that you are the only user connected to the database.

b.   Back up the database and save the backup file in a safe place.

c.    Make a copy of the customer’s database in SQL Server Management Studio. You will upgrade the copy and keep the original.

d.   Verify that both your partner development license file and customer license file have been updated to Microsoft Dynamics NAV 2013.

e.   Identify a User ID and password for a superuser in the system or create a new superuser that you can use for the upgrade process. Log in as the superuser when you perform the upgrade.

f.     Verify that you have the dbcreator and securityadmin Server Roles for the Microsoft Dynamics NAV SQL Server instance, using SQL Server Management Studio. To manage companies, objects, and licenses within a Microsoft Dynamics NAV database you must also have the db_owner database permission.

g.   Disable integration properties for the database.

h.   Open the database in the Microsoft Dynamics NAV 2009 Classic with Microsoft SQL Server client.

i.     Run a database test to determine the state of the customer’s database.
Note: The database test can require a significant amount of time, depending on the size of the database.

4.   Import Upgrade Step 1 Objects

Import Upgrade601700.1.fob.

5.      Run the “Adjust Cost-Item Entries” batch job to ensure that the inventory cost data in the customer’s database is up to date.

6.   If your organization posts inventory costs to the Microsoft Dynamics NAV general ledger, run the “Post Inventory Cost to G/L” batch job.

Run the job for each company in the database.

7.      For the SCM feature, make the changes to tables 32, 83, 89, and 5841 described in the Update Guide.

8.   Perform Step 1 data conversion.

a.    In the Classic client, open Object Designer, and then open form 104001, Upgrade - Old Version.

2. Choose Run.
3. Choose Transfer Data.

Repeat the conversion for each company in the database.

9.   On form 104001, choose Delete Objects.

This runs codeunit 104002, Delete Old Objects, which deletes all of the objects that are not tables. It also deletes tables that belong to the features that are discontinued in Microsoft Dynamics NAV 2013.

10.Create the New Microsoft Dynamics NAV Database.

This involves installing Microsoft Dynamics NAV 2013, and then opening your database in the Microsoft Dynamics NAV 2013 development environment.

See the Upgrade Guide for details.

11.Change the compatibility level of the database.

For SQL Server 2008 and SQL Server 2008 R2 editions, verify that the compatibility level of the database is set to 100. For SQL Server 2012, the appropriate compatibility level is 110. To set the compatibility level, run a query like the following in Microsoft SQL Server Management Studio:

USE [master]; ALTER DATABASE [YourDatabaseName] SET COMPATIBILITY_LEVEL = 100

12.   Import all customized Microsoft Dynamics NAV 2013 objects.

13.   Compile all objects.

14.Import Upgrade Step 2 objects.

 Import Upgrade601700.2.fob in the development environment.

15.Set the language

In the development environment, choose Tools, choose Language, and then select the language of the old customer database.

16.Perform Step 2 data conversion.

1. Open page 104002, Upgrade - New Version.
2. Choose Run.
   This opens the Windows client and displays page 104002, Upgrade - New Version.

Choose Transfer Data.
This runs codeunit 104048, Upgrade NAV 2009 Step 2.

17.Update source codes.

Run page 257, Source Codes, in the Windows client. Note any source codes that have been added, and then update the Source Code and Source Code Setup tables for any additional source codes in the new version.

18.Initialize all companies.

For each company, run codeunit 2, Company-Initialize and open page 531, Setup Checklist.

19.Update data in tables that are not specific to a single company.

This includes tables 2000000003 (Member Of), 2000000004 (User Role), 2000000005 (Permission), 2000000053 (Windows Access Control), and 2000000203 (Database Key Groups).

20.   Upgrade Roles (Permission Sets) and Permissions.

21.Delete obsolete tables

a.    Open Object Designer

b.    Open form 104002.

c.    Run Upgrade - New Version.

d.    Choose Delete, and then choose Mark Unused Old Tables.

e.      Set a filter on the Version List column to select tables marked as “Old Unused Table - marked for deletion.

f.       The Edit menu, choose Delete to delete the tables.

22.Delete Upgrade Toolkit Objects

1. In form 104002, choose Delete, and then choose Mark/Delete Upgrade Toolkit.
2. All Upgrade Toolkit objects, except tables, are removed automatically. The tables are marked for deletion.
3. Set a filter on the Version List column to select tables marked as “Upgrade Toolkit Tables - marked for deletion.”

On the Edit menu, choose Delete to delete the tables.

23.Test the database

a.    Test everything except field relationships between tables. If the test fails, follow the workflow for repairing damaged databases.

b.    Run the remaining part of the database test, which is to test field relationships between tables.

Test the upgraded item ledger entry invoiced quantities to make sure that any date compressed item ledger entries have been upgraded correctly.

                                                     

                                          ***Thank you very much ***