If your current version is not Microsoft Dynamics NAV 2013, you must upgrade to Microsoft Dynamics NAV 2013 before you can upgrade to Microsoft Dynamics NAV 2013 R2.

You can print this topic and use it as a reference during the upgrade process. Note any additional steps required to perform your specific customer upgrade and the time it took to perform this action. This will help you plan and execute the production upgrade more efficiently and with less trouble.

Microsoft Dynamics NAV includes Windows PowerShell cmdlets and sample scripts that you can use to automate all stages of the data upgrade process. For more information, see Automating the Upgrade Process using Sample Windows PowerShell Scripts.

Quick Guide

The following table summarizes the actions required for upgrading to Microsoft Dynamics NAV 2013 R2. This Quick Guide does not replace the full Upgrade Guide, which you should see before initiating an upgrade. For the latest version of the full Upgrade Guide, see http://go.microsoft.com/fwlink/?LinkID=316365

Activity Time / Notes

Upgrade the application code.

For more information, see Upgrading the Application Code.

Exporting all objects from the new customized Microsoft Dynamics NAV 2013 R2 database to an objects.fob file.

For more information, see Upgrading the Application Code.

Convert the database by opening it in the Microsoft Dynamics NAV 2013 R2 development environment.

For more information, see Converting a Microsoft Dynamics NAV 2013 Database.

Prepare the data for the upgrade.

  1. Make sure that you are the only user connected to the database.
  2. Back up the database and save the backup file in a safe location.
  3. Make a copy of the customerís database in SQL Server Management Studio. You will upgrade the copy and keep the original.
  4. 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.
  5. Verify that you have the dbcreator and securityadmin Server Roles for the Microsoft Dynamics NAV SQL Server instance by using SQL Server Management Studio. To manage companies, objects, and licenses in a Microsoft Dynamics NAV database you must also have the db_owner database permission.
  6. Disable integration properties for the database.
  7. Open the database in the Microsoft Dynamics NAV 2013 R2 development environment.
  8. Run a database test to determine the state of the customerís database.
  9. 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.
  10. For each company in the database that posts inventory costs to the Microsoft Dynamics NAV general ledger, run the Post Inventory Cost to G/L batch job.

Import the Upgrade Step 1 objects, and then perform Step 1 data conversion.

For more information, see Upgrading the Data.

Export permission sets and permissions.

Delete all objects except tables.

Import the customized objects from the objects.fob file.

Import the objects for upgrade step 2, and then perform Step 2 data conversion.

Import upgraded permission sets and permissions.

Initialize all companies.

Delete obsolete tables.

Delete the upgrade toolkit objects.

Test the database.

See Also