The data migration for a new ERP is always a challenging task. It starts with the collection of the data from the legacy system, the cleansing of the data, the data modelling to the desired new format, and the upload to the new ERP.
There are several studies that states "The data migration phase of a project can consume up to 30% of the total project resources".
This post will describe the most unknown features to migrate master data to Dynamics 365 BC (part 2). All explained with practical examples using Configuration Packages.
Official doc from MSFT: https://docs.microsoft.com/en-us/dynamics365/business-central/admin-migrate-customer-data.
How to apply a filter to the data to be exported/imported?
After creating a new Data Package (Header) and selecting the TableID (18 for Customer), the record will be updated.
If the import/export from/to Excel needs to be filtered, use the Filter functionality.
Example to import/export the Customer with Name starting with A letter:
It is possible to apply several filters at the same time.
How to import related tables with the correct sequence?
After creating a new Data Package (Header) and selecting the several tables at line level, if the tables are related, it will important to link them with the correct sequence.
Example with Vendor and Vendor Bank Account:
The important field to use is "Parent Table ID".
For the dependent record, it is important to select the parent record to guarantee the correct order when importing.
How to know how many records exists before exporting/importing?
Before exporting/importing, it will be very nice to know how many records exists per table to validate the correct export/import.
The answer to this question can be found at column "No. of Database Records".
Not convinced? Try yourself. All free to use.
Stay tuned for more unknown features to migrate your legacy data to D365BC.