Skip to main content

Key Pointers During Data Migration to NAV 2013 R2.

Hi All,

As we all know that there is Document Shipped with every product DVD of Navision which list down the steps for Data Migration. In some new version it was not shipped in product and was released later in Microsoft Team Blog.

What we do is we follow the steps listed in the Document and do the data migration, but in certain cases we face issues for which we don't have any reference in the document shipped from Microsoft.

The Reason of Issues can be data related, Hardware Related & Service Related.

In this article i will try to add some of my findings during data migration and will keep of adding points in future whenever i stuck with issues. This article will act as checklist for data migration to NAV 2013 R2.

#Saurav - Added on 07-04-2015



Before starting data migration we need -

1. If Data migration is being done on a separate server then during restoration select the same SQL Collation as there in the actual database.

2. Check your deleted dimension if any & resolve. Steps & Query listed in the article. (Dimension Issue)

3. If Object re-numbering is required then complete it in old version & move data to new tables. Easy to do...

--------------------------------------------------------------------------------------------------------
>>RUN Step 1 for all companies, Take Backup and Open Database in NAV 2013.
>>After Conversion to NAV 2013 complete Take Backup.
--------------------------------------------------------------------------------------------------------

BEFORE STEP 2 -

1. Check Memory usage of Server, It might be at peak because of NAV 2013 Client conversion process. If possible restart the Server or at least the SQL Services to release memory.

** Make sure its feasible to do so, if the SQL server have other database then you cannot do above step.

2. A domain account that will be used for running NAV Services with sufficient permission on SQL Server.

3. NAV 2013 R2 Exe Build at Server and at client Should have at least Cumulative Update 6 Applied. Try to use to apply the Exe from the Latest Cumulative Update.

4. NAV 2013 R2 Service Instance Should have SQL Command Timeout Set to 24:00:00 (General Tab of Service).

5. Database should have NAV 2013 R2 License File saved or NAV 2013 R2 License file should be uploaded on server.

--------------------------------------------------------------------------------------------------------
Open Database in NAV 2013 R2 & Stop Before Data migration step Says import merged objects of NAV 2013 R2.
--------------------------------------------------------------------------------------------------------
DURING Importing Objects-

1. Check your service instance is Running.

2. Import all objects except tables in database first. Import tables but not all in one go.

Import table in Sets says 1..49999 and 50000..

** You can break set as per your feasibility.
** Reason - Only Table Metadata need to be updated on SQL Database so lets don't overload SQL in one go.

3. After Import is completed Run the Sync-Tenant Command as per article.

4. Wait till SQL is Removing the Old Metadata and Creating and Updating New Metadata.
  Refer Article

--------------------------------------------------------------------------------------------------------
Start the Client and Follow the Upgrade Steps.
--------------------------------------------------------------------------------------------------------

After Step 2 -

1. Read all the steps once step 2 is completed.

2. Mark unused & Toolkit objects, delete unused objects & Delete Unused Tables & Toolkit after deleting data.
**
--Most of us don't do these steps. Lets see how it helps.

--a. If there is some data in unused tables that acts as a check point that our migration is not complete.

--b. If makes life simpler when you plan to upgrade same customer again.

That it as of now & Stay tuned for more. Will try to update this article as per my findings.

Your comments are welcome.

Regards,
Saurav Dhyani
www.sauravdhyani.com

Comments

Popular posts from this blog

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 - 

Error After Restore SQL Backup of NAV 2013 Database

Hi all, we are facing a conman issue during restoring a SQL Database backup restored for NAV 2013. While Trying to run object from Object Designer we get below listed error (even the service is configured properly) - --------------------------- Microsoft Dynamics NAV Development Environment --------------------------- There are no NAV Server instances available for this database. You must ensure that a NAV Server instance is running and is configured to use the database before you perform this activity. --------------------------- OK    ---------------------------

Future - What Next After NAV 2016. Code Name - Madeira...

Hi All, While Browsing web I came across some article which says about next release of Microsoft Dynamics NAV. Let's see the History of Code Names Given to Previous Version  - NAV 2013 - Code Name 'Sicily' NAV 2015 - Code Name 'CRETE' NAV 2016 - Code Name 'CORFU' And as we all know that all these are the Islands.