Migration routes

    Microsoft Dynamics 365 Data Migration Routes

    Explore migration paths across Dynamics 365 Finance, Supply Chain and Customer Engagement, including migration to and from other enterprise platforms.

    Discuss Your MigrationAll Migration Routes

    All Microsoft Dynamics 365 migration routes

    Microsoft Dynamics 365→Oracle Fusion

    Microsoft Dynamics 365 to Oracle Fusion data migration

    Financials, Procurement, SCM, Master data

    View route →    Microsoft Dynamics 365→Salesforce

    Microsoft Dynamics 365 to Salesforce data migration

    Accounts, Contacts, Leads, Opportunities

    View route →    Microsoft Dynamics 365→SAP S/4HANA

    Microsoft Dynamics 365 to SAP S/4HANA data migration

    Financials, Procurement, Master data

    View route →    Oracle EBS→Microsoft Dynamics 365

    Oracle EBS to Microsoft Dynamics 365 data migration

    Financials, Procurement, SCM, Master data

    View route →    Salesforce→Microsoft Dynamics 365

    Salesforce to Microsoft Dynamics 365 data migration

    Accounts, Contacts, Leads, Opportunities

    View route →    SAP ECC→Microsoft Dynamics 365

    SAP ECC to Microsoft Dynamics 365 data migration

    Financials, Procurement, Master data

    View route →

    What extraction from Microsoft Dynamics 365 involves

    The characteristics that shape every migration off this platform.

    Two different products under one nameDynamics 365 Finance and Supply Chain (the former AX/Operations lineage) and Dynamics 365 Sales/Customer Engagement (the former CRM lineage) have different data models and different extraction surfaces. Naming which one is in scope comes first.
    Dataverse and the Web APICustomer Engagement data sits in Dataverse, extracted through the Web API, OData, or Azure Synapse Link for volume.
    Data entities in Finance and OperationsF&O exposes data entities rather than raw tables, through the Data Management Framework — which is also how data goes back in.
    GUID keysRecords are keyed by GUID. As with any system that generates its own keys, they mean nothing in a target and relationships must be rebuilt through a cross-reference.
    Option sets and choice fieldsCoded values validate against option sets defined in the model, so those definitions are extracted as reference data.

    How Microsoft Dynamics 365 accepts data

    Load order is part of the design on any inbound route.

    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.

    Planning a Microsoft Dynamics 365 migration?

    Tell us your source system, target platform and timeline.

    Discuss Your MigrationSee Delivered Projects