After upgrading the application code as noted in Part 1 of the series, the next step is to upgrade the data by using provisioned data conversion tools to convert the existing data with NAV 2009 R2’s table and field structure, so that it functions with NAV 2013 R2’s table and field structure.
Part 2: Upgrading the Data
Upgrading the Data [NAV 2009 R2 -> NAV 2013 R2]
Upgrading the NAV 2009 R2 database requires:
- Upgrading company-specific data
- Upgrading data common to all companies,
- Deleting unused tables
- Testing the new database
To upgrade company-specific data, follow the steps below. More details on the tasks below can be found in the Upgrading Company-Specific Data article.
- Open the NAV 2009 R2 Classic Client and make a copy/backup of the database that is being upgraded.
- Import the “Upgrade601701.1” .fob file found in the UpgradeToolKit directory of the NAV 2013 R2 installation files. The purpose if this import is to replace some tables to a clean state to prevent compilation errors in the future
- For each company in the database you will have to run the “Adjust Cost-Item Entries” batch job to make sure that the inventory cost data in the customer’s database is up-to-date
You are now ready to transfer the data. The following steps should be taken:
- Run form 104001 (Upgrade - Old Version) from the Object Designer in NAV 2009 R2. Chose Transfer Data once for every company in the database.
- The Upgrade Error Log window will show any errors that need to be corrected that may occur.
- Run report 104001 (Table Information) to see the size of your database and make note of it as it will be needed later on when you set the size of the new database.
Once data transfer is complete, delete all non-table objects in the database, as well as tables that belong to features not available in NAV 2013 R2. To do this, simply run form 104001 again and chose Delete Objects. This will make sure that no conflicts or compilation errors occur during later tasks. A list of removed tables can be found in the Eliminated Tables article.
The next task to perform is creating a new NAV database. Begin by creating another copy of the current database and then close and uninstall NAV 2009 R2. NAV 2009 R2 can be reinstalled later on. Ensure that the all the user permissions for the database are in place (see the “Preparing to Upgrade” section in Part 1). After that is done, it's time to install NAV 2013 R2 with the Developer Option. If using SQL Server 2008, set the compatibility level for the database to 100, otherwise set compatibility level to 110. This can be set from the SQL Server Management Studio after connecting the server instance that NAV is attached to.
Once installed, open the NAV 2013 R2 Development Environment and open the database that was copied before uninstalling NAV 2009 R2. This will prompt a database conversion which updates the system tables, enables Unicode in the database objects, upgrades to the newest Windows collation, and marks all objects in the database as not compiled. Once this step is complete, increase the size of the database to the size copied down earlier in this guide.
The next step is to upload your NAV 2013 R2 developer licence to the database and configure the NAV Server to connect to the new database. This can be done by starting the NAV Server Administration tool and selecting the appropriate NAV Server instance in the left pane. Choose Edit then update the database options to point to the converted database. Save once you are finished and restart the NAV Server instance.
Stay tuned for Part 3. More information can be found in the cited links below.
 Upgrading Company-Specific Data
 Upgrading Company-Specific Data - Step 1 Data Conversion
 Upgrading the Data - Eliminated Tables
 Upgrading Company-Specific Data - Create the New Microsoft Dynamics NAV Database
If you're finding this series helpful and would like us to lead the upgrade of your company's system, don't hesitate to contact us.