Microsoft Dynamics NAV 2017 - Data Migration.

Hi All,

As With Release of New Version of Microsoft Dynamics NAV 2017, we also need to look into the possibility of Upgrade Our Customer Base to it.

In this article, I will share my experience from a Mock Migration From 2016 To NAV 2017.

** Steps remain same if you plan to upgrade from 2013 or later.

So if something that you would be interested in Reading Please go Ahead.




1. From which version we can upgrade directly to Microsoft Dynamics NAV 2017 -

So as of today Microsoft Support Upgrade to Microsoft Dynamics NAV 2017 from below listed Versions -

NAV 2013.
NAV 2013 R2.
NAV 2015.
NAV 2016.

2. What are my Pre-requisites Before Starting Data Migration To Dynamics NAV 2017?

Sr. No.	Prerequisites
1	Upgrade Toolkit Objects.
2	A Merged Object File that is Created After Compare and Merge Process.
3	Microsoft Dynamics NAV 2017 Partner license.

3. Steps Before Starting Data Migration.

Sr. No.	Steps Before We Start Data Migration.
1	Make a copy of the old database or create the full database backup.
2	If a company name includes a special character, an error may display during the upgrade. In this context, special characters include the following:
	[ ~ @ # $ % & * ( ) . ! % - + / = ? ]
3	If you are going to upgrade a database where one or more company name includes a special character, Microsoft recommends that you rename the company before you start the upgrade process. After the upgrade is successfully finished, you can rename the company again.
4	In Object Designer, verify that no objects are locked.
5	On the Tools menu, choose Build Server Application Objects, and then choose the Yes button.
6	Upload the Microsoft Dynamics NAV 2017 Partner license to the database.
7	If you are converting a Microsoft Dynamics NAV 2013 R2 or Microsoft Dynamics NAV 2015 database or Microsoft Dynamics NAV 2016 database, then run the Sync-NavTenant cmdlet from the Administration Shell to synchronize the database schema changes.
8	Stop Navision Service If any pointing to Database and close all sessions.
9	Clear all Microsoft Dynamics NAV Server instance records from the dbo.Server Instance table in the database on SQL Server.
10	If a Workflow is incomplete, please either cancel this request or Approve all Workflow which are in-process. ** Only if you are using Microsoft Dynamics NAV 2016.

4. Data Migration (As per MSDN on 30-Jan-2017)

Sr. No.	Description
1	Create a full SQL backup of the old database on SQL Server.
2	Delete all objects except tables from the old database.
3	Uninstall the old product and install the new product NAV 2017.
4	Run NAV 2017 Developer Environment as Administrator. Convert the old database to the Microsoft Dynamics NAV 2017 format.
5	Connect Database to NAV 2017 Service. You use the Microsoft Dynamics NAV Server Administration tool to connect a Microsoft Dynamics NAV Server instance to the converted database. In addition, you must add the service account that is used by the Microsoft Dynamics NAV Server instance as a member of the db_owner role in the Dynamics NAV database on SQL Server.
6	Use the development environment to compile all system tables. System tables have IDs in the 2000000000 range.
7	Run the schema synchronization from the Microsoft Dynamics NAV Development Environment or Microsoft Dynamics NAV 2017 Administration Shell. Either - Tools menu, choose Sync. Schema for All Tables, and then choose With Validation OR Sync-NavTenant –ServerInstance <ServerInstanceName>
8	Import the application objects to the converted database. On the dialog box for selecting the schema synchronization, set the Synchronize Schema option to Later.
9	Import the Upgrade Toolkit Objects with Synchronize Schema option to Later.
10	Run the schema synchronization to synchronize the new tables. Run the Sync. Schema for All Tables – With Validation option from the development environment OR Run the Sync-NavTenant cmdlet from the Microsoft Dynamics NAV 2016 Administration Shell.
11	Run the data upgrade process. From Tools -> Data Upgrade -> Start the Upgrade Process.
12	Delete the upgrade objects. When you delete tables, on the Delete dialog box, set the Synchronize Schema option to Force.
13	Delete Tables - 470|824|825|826|827|828|829|830|1305|1510|5150|5371|5372|8640 When you delete tables, on the Delete dialog box, set the Synchronize Schema option to Force. ** This List of Table is only if you are upgrading from NAV 2016. For other versions, these can be other discontinued tables.
14	Import upgraded permission sets and permissions by using the Roles and Permissions XMLports
15	Set the language of the customer database
16	Register client control add-ins

5. Where I Find the Upgrade Toolkit?

Upgrade Toolkit objects are placed in the Product DVD. In Product DVD Folder "UpgradeToolKit" will contain objects for worldwide version (W1) and Localized Objects (as per product DVD), as shown below.

6. Shall we do Regular Upgrade?

Microsoft has introduced more events in Microsoft Dynamics NAV 2017. I still feel people are resistant to go upgrade with events. But I think we would also need to think about the cost to customers.

Upgrading with events is a one-time cost upgrade for the customer and will suggest to at least suggest both options to customers when you quote for an upgrade.

I would agree that yes till now all customization cannot be moved to events but all those which we can move will be the right step to move to events. For others I feel, use hooks pattern so that it's easy when we have events we can move them easily with very less cost.

7. MSDN Articles for Data Migration to Microsoft Dynamics NAV 2017 -

1. Upgrading to Microsoft Dynamics NAV 2017.
2. Upgrading the application code to Microsoft Dynamics NAV 2017.
3. Upgrading the Data to Microsoft Dynamics NAV 2017.

Your Comments and Views about article and Upgrade Approach are awaited. Do Suggest Your Views.

Regards,
Saurav Dhyani
saurav-nav.blogspot.com