Migrate data using the Copy data from company function in the configuration worksheet
In many cases, to migrate customer data to Business Central online, use the built-in migration tools to migrate data from specific product versions.
Alternatively, you can migrate to Business Central on-premises using Excel or the data migration tools of RapidStart Services, and then switch to the cloud.
You can choose to use the configuration package approach to migrating customer data, such as if the customer is coming from a product that isn't supported by the Migrate On-Premises Data to Business Central Online tools, nor by an app for Business Central online, such as Microsoft's own apps to migrate from QuickBooks app.
From both the Configuration Worksheet page and the Configuration Package page, you can import data from Excel or a .rapidstart file. If you prefer to use Excel, the data must be in an Excel workbook that is exported from the Configuration Packages page. This way, the Excel workbook complies with the Business Central data structure. In the Configuration Package page, you can map tables and fields if the data structure is different between where the data came from and where it's going. Business Central treats and handles the mapping based on table relations:
If you define a mapping directly for a field in a table, then Business Central uses it.
If the field has a relation to another table, Business Central searches for the mapping defined for the primary key field in the related table. The related table, however, must be part of the configuration package.
If mapping information is defined in both places, for the field directly and for the primary key in the related table, then Business Central searches for the mapping in both places.
If the same mappings are defined directly for a field and in the related table, but have different new values, the mapping that is defined directly for the field takes priority over the mapping that is defined for the table that the field is referencing.