Microsoft Dynamics 365 Data Migration Object Library

How Microsoft Dynamics 365 accepts data

Load order and mechanism apply across every object on this platform.

1. 1Data Management Framework for Finance and OperationsData entities, data projects and staging tables. Import runs into staging first, then into target tables, with errors surfacing per entity at each step.
2. 2Dataverse loads for Customer EngagementBulk loads through the Web API or dataflows, with alternate keys used so a reload updates rather than duplicates.
3. 3Number sequencesF&O assigns many keys from number sequences. Whether the legacy key is preserved or regenerated is decided per entity before mapping.
4. 4Entity dependency orderReference and setup entities, then masters, then transactions — the same shape as any ERP load, against a target where entity definitions rather than tables set the contract.
5. 5Work the staging-table errorsRows can pass into staging and still fail promotion into target tables, so both stages are reconciled rather than just the file load.