To prepare a customer’s existing installation for upgrading, do the following.

Note
Use your solution developer’s license as you follow these steps and perform the actual upgrade. The customer’s license may be limited. If you have not already done so, locate or obtain new versions of both your solution developer’s license file and the customer’s license file that are for Microsoft Dynamics NAV 2013 R2.

• If you have been using a native Microsoft Dynamics NAV database with Microsoft Dynamics NAV 2009 (instead of a SQL Server database), you must migrate your database to SQL Server using Microsoft Dynamics NAV 2009 before you can upgrade to Microsoft Dynamics NAV 2013 R2. For more information, see chapter 5, "Migrating to Microsoft Dynamics NAV 2009 with Microsoft SQL Server,"” in the Microsoft Dynamics NAV 2009 Upgrade Toolkit Manual.
  
• Verify that the user performing the upgrade has the necessary roles and permissions in SQL Server Management Studio:
  
  • Verify that the user has the db_datareader, db_datawriter, and db_ddladmin database roles for the database. For information about how to grant these roles, see Provisioning the Microsoft Dynamics NAV Server Account.
    
  • Verify that the user has the sysadmin Server Role for the instance of SQL Server that is hosting your Microsoft Dynamics NAV database. For information about how to assign this role, see Setting Database Owner and Security Administration Permissions.
    
  • Verify that the default schema for the user's account is dbo. Do this by selecting the user account under Security/Users for the database to open the database user dialog box. Choose the AssistEdit button for the default schema field and then choose [dbo] as the default schema.
    
• Identify a User ID and password for a superuser or create a new superuser that you can use for the upgrade process. A superuser is a user who has been assigned the SUPER permission set. This permission set has all permissions. Log in as the superuser when you perform the upgrade.
  
• In Object Designer, verify that there are no locked objects in the Microsoft Dynamics NAV database.
  
• Make sure that you are the only user connected to the database.
  
• Back up the database and save the backup file in a safe location.
  
• Make a copy of the customer’s database. You will upgrade the copy and keep the original database.
  

© 2013 Microsoft. All rights reserved.