Data migration for Dynamics Nav / Navision

This refers to the conversion of data from legacy systems for loading into Nav using Excel and the Nav dataport / Data Migration / Rapidstart Services functionality. Data loads include master files (customer, vendor details for example), configuration files and transactions files (opening positions).
 
There are generally 2 stages to one off data migration process: master file and transaction file processing.

Master files refer to non transactional data for each module. As an example, the master files for Sales and Receivables would be customer details. These details would include name, address and contact details. These details may include account numbers if the account numbers are to be retained in Nav.

Transaction files are usually transactions representing a closing position for loading into Nav. In the example given, this would be all open (partly or fully unpaid or unsettled) items for customers as at a set date. The data required for loading into Dynamics Nav would typically include account reference, transaction reference, description, document and / or due date, currency code, amount for the currency code and amount for the ledgers base currency.
 
The data migration process presumes that data to be migrated can be provided in text or Excel format and includes conversion of data into a form acceptable to Dynamics Nav and data loads using Nav dataports / Data Migration / Rapidstart Services.
 
There should be no need to manually input any data to be mgrated into Navision as long as the data to be migrated can be provided in text or Excel format.

From version 5 onwards of Dynamics Nav, the data migration process can be managed through the Data Migration tool. In 2013 / 2015 this has been 'dressed up' as Rapid Start Services.

The Data Migration tool just requires a little end user tuition (half a day tops) to get them up and running loading master file data. We can provide this training if required. Just email us.

Prior to version 5, the process is:

• Receipt of data to be converted.
• Data conversion.
• Dataport development
• Data load test database
• Client sign off
• Data load into live database

 
For all data migrations, it is very important to ensure data integrity. All data migrations completed by FPC are fully checked against data provided before completion and load into the live environment. This presumes a test and live database exist and that the test database is a reasonably current copy of the live database. Data migration does not refer to any regular data transfers from, say, legacy systems.

Dynamics Nav includes a Data Migration / Rapidstart Services tool within the Administration module.

Very good for master file (customer, vendor, item, fixed asset) data migration as it:

• Loads data into temporary tables.
• Checks data against other linked tables.
• Confirms errors.
• Completes all validations on tables where data will be loaded.

The process itself is not perfect but very usable. Shallow learning curve.

To use:

• Confirm table id.
• Confirm fields required.
• Export to excel.
• Populate exported excel spreadsheet with data.
• Save excel file.
• Import from excel.

Not so good for open ledger transactions such as opening trial balance, opening customer ledger entries, open vendor ledger entries and open stock items.

This requires the use of dataports from Nav (pre v 2013)and some code within the dataport. Of course for Nav 2013 onwards, you can just create the journal in Excel and copy and paste into Nav.