Upgrade from NAV 2009 SP1 to 2013 R2 Guide

This guide is designed to walk you through a standard Microsoft Dynamics upgrade from NAV 2009 SP1 to 2013 R2.


  1. Before starting, print out a few financial reports from the original 2009 database to compare with the upgraded 2013R2 database. A few good ones are Aged Accounts Receivable/Payable, Bank Acc. – Detail Trial Bal., and Detail Trial Balance.
  2. Take a backup of the database that you are going to upgrade in case of inconsistencies found later (user permissions, functionality, etc.). If the upgrade is in Live, you can create a copy of the database and upgrade the copy database.
  3. Confirm that all dimensions in the Dimension tables have a value and are not blank. This will cause issues when transferring data in the future.
  4. Take a backup of all the objects.

Open the database in 2009 SP1

  1. Import Upgrade601701.US.1.fob and Replace All.
  2. Run the Adjust Cost – Item Entries Codeunit.
  3. If the organization posts inventory costs to the Microsoft Dynamics NAV general ledger, run the Post Inventory Cost to G/L Codeunit.
  4. Run for 104001 Upgrade – Old Version and Transfer Data. You will have to do this for each company separately. This would also be a good time to remove any unwanted or unused companies.
  5. Open the Upgrade Error Log Page for errors.
  6. To see the size of your database, run Report 104001, Table Information. This will be used later when you set the size for your new database.
  7. Run for 104001 Upgrade – Old Version, and Delete Old Objects. This deletes all objects except for tables.

Change the compatibility level of the SP1 database

If SQL 2012: Computability Level is 110

If SQL 2008 or 2008 R2: Computability Level is 100

Open the database in 2013 RTM.

Convert database
Make sure to have all users to exit the system or else you will receive an error saying too many users are logged in.

Open the database in 2013 R2.

1. Convert database

  • This includes an upgrade of system tables, and an upgrade of all reports to support Report Viewer 2010.
  • After database conversion has completed, you will receive compilation errors in several standard Microsoft Dynamics NAV objects. You must resolve these errors before you continue. If you see errors about reports that are specific to this database, you must modify the objects in the original Microsoft Dynamics NAV 2013 database and then start the conversion again.
  • An error you may run into is “The table definition is invalid and cannot be validated.” This error will be resolved once the service is created and opened. Do not change the property “Prevent Data Loss from Table Changes” to No. It should always stay the defaulted Yes.


3.02. Compile the system tables

  • You can find the tables by setting a filter for table ID 2000000004..2000000130

3. Create a service instance

  • Go to Tools > Options >
    • Prevent Data Loss from Table Changes: YES (default is yes)
    • Server Name: Fill Out
    • Server Instance: Fill Out
    • Server Port: 7046
  • Assign the Server Instance to the Database
    • Open File > Database > Information > Select the dropdown for Server Instance.
    • Select the instance you want. If you do not see an instance to select, check these:
      1. Make sure that the server is a dbowner of the database
      2. Make sure that the user is a dbowner of the database
      3. Make sure that the service is running in both the Microsoft Dynamics NAV 2013R2 Administration Shell and the Windows Services.

4. Open Upgrade – Old Version

    • Choose Export Roles > Save it as PermissionSets.xml
    • Choose Export Permissions > Save it as Permissions.xml
    • No need to delete objects since they are already deleted.

5. Import and Replace all objects into database

  • Compile and solve issues. This needs to be done prior to importing the Upgrade601701.US.2.fob file.

6. Import Upgrade601701.US.2.fob

  • Replace all.
  • Tools > Language > select the language of the original customer database

7. Run page 104002 Upgrade – New Version

  • Test Database Connection
    • If your configuration is based on a named SQL Server instance, you must open the window in edit mode and then specify the name in the SQL Server Name field.
  • Transfer Data


  • Open the Upgrade Error Log to see errors and solve them.


5.1 5.2

8. Import Permission Sets and Permissions

  • Run Page 9802 Permission Sets
  • Delete all roles EXCEPT for SUPER
  • Run Page 104001 Upgrade – New Version
  • Import the Permission Sets and Permissions

9. Mark Old/Unused Tables

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

10. Mark Upgrade Toolkit Objects

  1. Set a filter on the Version List column to select tables marked as “Upgrade Toolkit Tables – marked for deletion.

11. Test the Database

Extra Tip

In some instances the RTC (RoleTailored Client) has a chart or graph that appears on the Home Page. However, when doing an upgrade, the chart is sometimes no longer located and the following appears on the Home Page:



  1. Open to this file path:
    1. C:\Program Files (x86)\Microsoft Dynamics NAV\71\RoleTailored Client\Add-ins\BusinessChart


  1. Select and Copy the name NOT including the extension. In this example it’s: Dynamics.Nav.Client.BusinessChart
  2. Run Table 2000000069 – Client Add-in
  3. Paste the Control Add-in Name to the table with the Public Key Token below. The Token Key is the same as the other two. (They should be there already). Then choose OK.


  1. Go to Page 869 – Cash Flow Chart. Open the properties for “BusinessChart” and make sure that the ControlAddIn is Dynamics.Nav.Client.BusinessChart;PublicKeyToken=31bf3856ad364e35. Compile and close.
  2. Open the RTC and the previously missing chart should be there.



June 24, 2015


Email [email protected] with any questions you have pertaining to this course.

New CPE Accredited Courses Now Available for Dynamics AX, GP, and NAVEARN CREDITS TODAY