The most unknown features to migrate master data to D365BC (Part 1)

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 unknow features to migrate master data to Dynamics 365 BC. As an practical example, it will be described the migration of Customers from the Data Template in Excel file to D365BC using Configuration Packages.

Official doc from MSFT: https://docs.microsoft.com/en-us/dynamics365/business-central/admin-migrate-customer-data.

How to know all related tables

After creating a new Data Package (Header) and selecting the TableID (18 for Customer), the record will be updated.

Some of the fields are related with other tables. To get a view of all the related tables, select the option Get Related Tables under Functions.

All sorted with one click!

How to have reduce the number of columns to cleanse and model (before importing)

After creating a new Data Package (Header) and selecting the TableID (18 for Customer), the record will be updated showing all the fields available to be imported.

In this case, 97 fields. We must be on same page saying it is too many fields! And some of them are always with the same value!

The way to move forward is to use the Data Template field on the line level.

After preparing one Data Template with all the fields and values to be applied, just select it.

This simple action will allow to remove all the fields to the Data Template and this way the cleansing and modelling of the data in Excel will be a lot less.

This approach will help you have less columns in Excel file before importing to BC! Less columns, less errors and less time!

How to improve performance

Using Configuration Packages to migrate data can take a lot of time depending on the number of records and complexity of the data to be imported. Not changing the scope of the migration, there are ways to improve the overall performance using Configuration Packages to migrate data to BC.

The first one, was precisely described before (remove all the fields that be migrated using a rule - Field Data Template).

The second is to untick the option to Validate Field in all possible the fields.

Important Notes:

• Not possible on Key table fields (No. on Customer table for example)
• Not suggested for Journals or Documents Data Migration. Only use this action for Master Data tables.

This approach will help you have less errors and reduce the migration time!

Not convinced? Try yourself. All free to use.

Stay tuned for the next parts with more unknown features.