Skip to main content

NAV 2013 Upgrade Part III - Data Upgrading.

Hi all,

As per agenda we need to discuss the data upgrade in NAV 2013. The process is similar to what used to be till NAV 2009 R2 but with some changes.

Let's start the process.

Remember - 
1) You can only upgrade a database to NAV 2013 from NAV 2009 SP1 / R2 SQL Only.
2) The Synchronization of users with SQL Server is no more required.



Steps -
1) Update the Application Code (Already Discussed in Part 1 & Part 2).

2) Export all the objects from new customized Microsoft Dynamics NAV 2013 database to an object file: MergedObjectNAV2013.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 Upgrade601700.1.fob. (This can be found in Product DVD under Upgrade Toolkit -->Data
    Conversion Tools\601)

5) Perform Step 1 data conversion. (IN OLD VERSION 2009 SP1 / R2)

a. In the Classic client, open Object Designer, and then open form 104001, Upgrade - Old Version.
b. Choose Run.
c. Choose Transfer Data.
Repeat the conversion for each company in the database.

6) On form 104001, choose Delete Objects.

7) 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.

8) Change the compatibility level of the database to 100 in SQL Server.


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

9) Import all customized Microsoft Dynamics NAV 2013 objects. (MergedObjectNAV2013.fob.)
10) Compile all objects.
11) Import Upgrade601700.2.fob.(This can be found in Product DVD under Upgrade Toolkit -->Data Conversion Tools\601)

[Step 2 To be performed in NAV 2013]

12) Perform Step 2 data conversion.
  a. Open page 104002, Upgrade - New Version.
  b. Choose Run.
This opens the Windows client and displays page 104002, Upgrade - New Version.
  c. Choose Transfer Data.
  d. Run Page 257 Source Codes.
  e. Initialize all companies (run codeunit 2).

13. Upgrade Roles (Permission Sets) and Permissions.

14. 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. On the Edit menu, choose Delete to delete the tables.

15. Delete Upgrade Toolkit Objects
  a. In form 104002, choose Delete, and then choose Mark/Delete Upgrade Toolkit.
  b. All Upgrade Toolkit objects, except tables, are removed automatically. The tables are marked for
     deletion.
  c. Set a filter on the Version List column to select tables marked as “Upgrade Toolkit Tables - marked for
      deletion.”
  d. On the Edit menu, choose Delete to delete the tables.

Let me know if you face any issues.

Regards,
Saurav Dhyani
http://saurav-nav.blogspot.in/

Comments


  1. Great thoughts you got there, believe I may possibly try just some of it throughout my daily life.

    Data Conversion Company in Chennai

    ReplyDelete

Post a Comment

Popular posts from this blog

BC 21 and Higher - PowerShell Cmdlet (Replacement of Business Central Administration).

Hi Readers, As discussed in last article about deprecating of Business Central Administration, there are few common actions that we use in administration till Business Central 20. For our on-prem customers, we will still require doing activities. As Microsoft suggest we need to start using PowerShell cmdlet.    Let's see how to do those via PowerShell, or Administration Shell. I will be keep adding commands as you comment to this article.

Send Mail with Attachment From Navision.

Hi all, We have seen how to save a report into PDF and how to send mail to a customer. Let's link these two post in one i.e. Mailing statement to a customer into PDF Format. This article is part of the Series. Please Refer  Table of Content here . If you have the old objects set let me brief you what I will be changing - 

MSDYN365BC - Data Upgrade To Microsoft Dynamics 365 Business Central on premises.

Hi Readers, We have already talked about the number of steps for upgrading to Business Central on Premises from different NAV versions. After that article, I received multiple requests for an article which list down steps for Data Migration. In this article, we will discuss steps of data migration to MSDYN365BC (on-Prem) from NAV 2017. For this article, I am considering a Cronus Demo Database without any customization. For an actual upgrade project, we will have to complete object merge using compare and Merge process. After the Merge Process, the next step is data migration. Let's discuss those steps. Direct Upgrade to Microsoft Dynamics 365 Business Central (on-Prem) is from following versions - 1. NAV 2015. 2. NAV 2016. 3. NAV 2017. 4. NAV 2018.