---
title: "Dynamics 365 CRM data migration: to and from Salesforce | Rig"
description: "Dynamics 365 CRM data migration to and from Salesforce or HubSpot: map accounts, opportunities and activities, check sample records and keep reporting history."
canonical: "https://rig.so/migrate/dynamics-365-crm"
format: markdown
---

Migration

# Move Dynamics 365 CRM data and keep reporting history

Move Dynamics 365 Sales data to Salesforce or HubSpot, or bring Salesforce data into Dynamics 365. Rig maps accounts, contacts, opportunities and activities, checks sample records with your sales operations team, and keeps the reporting history in your warehouse.

By [Rig](https://rig.so/about) · Last updated 20 November 2026

[Request a migration readiness check](https://rig.so/book-demo)

[Download the migration checklist](https://rig.so/downloads/migration-checklist.csv)

## At a glance

- Rig agrees a fixed delivery price after scoping the data, logic and integrations.
- Data moves in checked waves, with a parallel run where the systems allow it.
- History and permission tests are part of acceptance.
- Your system owners approve the mappings and the cutover.

01**Inventory**

Records, logic and owners

02**Map and rebuild**

Source to target definitions

03**Run in parallel**

Counts, totals and access

04**Accept and switch**

Sign-off and rollback plan

Each wave ends with an acceptance check. This diagram shows the delivery process.

## Map the data and the logic it carries

The table is a starting inventory, and the target edition, customisations and API access decide the final mapping. Check each object even when the name matches, because an object with the same name can behave differently in the target.

| Source | Target or retained output | Checks and known traps |
| --- | --- | --- |
| Accounts and contacts | Salesforce accounts and contacts, or HubSpot companies and contacts | Keep the Dataverse GUIDs as source IDs; check parent accounts and duplicate rules. |
| Leads and opportunities | Salesforce leads and opportunities, or HubSpot contacts and deals | Map qualification status, currencies, owners and product lines separately. |
| Activities: emails, appointments, phone calls and tasks | Tasks and events, or HubSpot activities | Regarding links and party lists need their own mapping; test time zones. |
| Option sets and business process flows | Picklists, sales processes and pipeline stages | Map each option value explicitly; stages that share a label can mean different things. |
| Custom tables, plug-ins and Power Automate flows | Custom objects and rebuilt automation | Logic does not move with the data, so list each rule and rebuild it in the target. |

## Moving into Dynamics 365, or out of it

Into Dynamics 365, Microsoft’s import wizard takes Excel, CSV and XML files, maps columns to Dataverse columns, keeps relationships through lookup columns and can update existing rows by an alternate key. Files are limited to 8 MB, or 32 MB as a zip, so a large move runs as repeatable API loads. Microsoft’s Configuration Migration tool is meant for configuration and reference data between environments. Out of Dynamics 365, Rig Ingest syncs the Dataverse tables, including accounts, contacts, opportunities, activities and your custom tables, into your warehouse, where the data is checked before it loads into Salesforce or HubSpot.

## Keep the reporting history in the warehouse

Dynamics reporting often sits in Power BI on top of Dataverse. Rig keeps the closed opportunities, old stage changes and activity history in your warehouse, joined to the new CRM records by their source IDs, so the pipeline and win-rate reports keep their history. The reporting hub covers moving the Power BI reports themselves.

## Map the dependencies first

Rig Map lists which flows, plug-ins, reports and integrations read each field before anything changes. On the Salesforce side, Rig mapped every custom field and its dependencies for an education software company before its cleanup.

## How a migration runs in Rig

Rig maps the systems and data across your estate, connects the source and target, and maps one schema to the other with previews of real records. Rig engineers agree the objects and history in scope with your team, prepare the destination and rehearse the load before they reconcile the results. Sign-off, cutover and follow-up tasks sit in the same migration workspace.

## Agree a timeline against the actual scope

The table gives a planning allowance for each phase, and the assessment turns it into a dated plan for the whole project. Large estates need several waves, and application configuration can add time.

| Phase | Initial planning allowance | Exit check |
| --- | --- | --- |
| Assessment | 3 to 5 working days | Owners, access and inventory agreed |
| Sample and mapping | 5 to 10 working days | Sample records and exceptions reviewed |
| Build and parallel validation | 2 to 6 weeks per wave | Counts, totals and permissions accepted |
| Final sync and cutover | 1 to 3 working days per wave | Business owner signs off; rollback remains available |

## Keep the evidence for each migration wave

For each wave you receive the source-to-target mappings, a reconciliation report, an exception log and a cutover checklist. The checks cover duplicates, missing relationships, deleted records, time zones and permissions as well as headline totals, and the old system stays available until the agreed retention and rollback checks pass.

## Where Rig may fall short

A migration that only needs a supported CSV import may be simpler to do yourself. Sub-minute operational replication, a full ERP implementation and specialist application redesign need a separate scope or another provider. Where Rig Ingest moves the data, confirm connector coverage for each source before you commit.

Inside Rig Migrate

## Run the migration in Rig, from the systems map to cutover

Rig natively maps systems and data across your IT estate, connects source and target systems, scopes the move and maps one schema to another. The same migration workspace tracks destination preparation, rehearsals, reconciliation, sign-off and the work after cutover, so your team can review the decisions and progress in one place.

1. ### Map the IT estate
   
   Map systems, data and integration flows across the IT estate. See which reports, processes and teams depend on the systems you plan to change.
2. ### Set up the migration
   
   Create the migration in Rig and record the source, destination and work to deliver. Keep the migration tasks and progress together.
3. ### Connect and discover
   
   Connect the source and target systems, then inspect their schemas and available data. Confirm access before deciding how each object will move.
4. ### Scope the work
   
   Choose the objects, fields and history to migrate. Record what stays, what changes and the dependencies the migration needs to preserve.
5. ### Map schema to schema
   
   Map source objects and fields to the target schema. Preview records and review rules to copy, translate, calculate, link, look up and match owners.
6. ### Prepare the destination
   
   Track the target preparation needed before loading data, including its configuration and the relationships your mapped records will use.
7. ### Rehearse the load
   
   Dry run the whole load and rehearse it in the destination environment. Review the results and resolve issues before the production cutover.
8. ### Reconcile and sign off
   
   Compare source and target records, relationships and business totals. Review exceptions with the system owners and record acceptance before proceeding.
9. ### Cut over
   
   Work through the agreed cutover tasks in Rig. Coordinate the final load and user switch with the people who own the systems.
10. ### Check after cutover
    
    Track the checks after the switch, confirm that reporting and processes work, and resolve outstanding issues before retiring the old setup.

[![Rig migration task list showing the systems map, setup, connection, scope, design, destination preparation, rehearsal, reconciliation, cutover and after-cutover stages](https://rig.so/migration-stages.png)](https://rig.so/migration-stages.png)

Migration stages and task progress in Rig. [View the full-size screenshot](https://rig.so/migration-stages.png).

### Inspect source values and target previews

The migration workbench shows source fields, target previews and the rule for each mapping. Your team can review translated values, linked records and calculated fields before signing off the mapping and rehearsing the load.

[![Rig Migrate workbench mapping a Dynamics 365 CE quote to Salesforce CPQ, with source values, target previews and translation, link and calculation rules](https://rig.so/migration-workbench.png)](https://rig.so/migration-workbench.png)

A D365 CE to Salesforce CPQ example. The workbench shows mapping decisions and migration tasks; this is not a completed cutover. [View the full-size screenshot](https://rig.so/migration-workbench.png).

### Reporting migration at Birdie

Birdie reports rebuilding sales and marketing reporting in less than a day. Its team kept Snowflake and the existing Fivetran pipelines; retirement of the Looker licence is not confirmed.

[Read the migration case study](https://rig.so/case-studies/birdie)

## Common questions

Can you migrate Dynamics 365 CRM to Salesforce?

Yes. Rig maps Dynamics 365 Sales accounts, contacts, leads, opportunities and activities to Salesforce, checks sample records with your team, then loads in waves.

Can you migrate Salesforce to Dynamics 365?

Yes. Rig stages Salesforce data in your warehouse, maps it to Dataverse tables, and loads it through repeatable API loads with checks on each wave.

What happens to our Dynamics reporting?

The history stays in your warehouse, joined to the new records, so pipeline and win-rate reports keep their trend lines. Power BI reports are rebuilt or repointed as a separate item.

What moves in this migration?

Move Dynamics 365 Sales data to Salesforce or HubSpot, or bring Salesforce data into Dynamics 365. Rig maps accounts, contacts, opportunities and activities, checks sample records with your sales operations team, and keeps the reporting history in your warehouse.

How much does a migration cost?

Rig maps the work and agrees a fixed delivery price before the migration starts. Source access, custom logic, history and the number of integrations affect the scope. Platform and third-party licence costs are agreed separately.

Can we keep reporting history?

Yes, where the source lets you extract it. You decide which history the target system needs and which stays in a governed archive, and Rig reconciles both against the original records.

How do you check that the data matches?

Rig compares record counts, identifiers, relationships and business totals for each wave. Every exception goes in a log, and the business owner has to accept the results before cutover.

Will both systems run during the move?

Yes, where the systems and licences allow it. Before the parallel run starts, you agree which system is the source of truth, how final changes are handled, the rollback conditions and the point at which users switch.

Who does the implementation?

Rig engineers do the work with your system owners, and your team approves the mappings, permissions and acceptance checks. Application configuration and specialist ERP or CPQ work is either written into the scope or assigned to your application partner.

Is there a guaranteed completion date?

The assessment produces a dated plan. Access, data quality, target readiness and user acceptance can all move it, so treat any planning range given before the assessment as an estimate.

## Related guides and services

[Data migration services for revenue and reporting systems](https://rig.so/services/data-migration)[migrate](https://rig.so/products/migrate)[Revenue systems migration: CPQ, CRM and Dynamics](https://rig.so/use-cases/revenue-systems-migration)[CRM data migration services: Salesforce, HubSpot and Dynamics](https://rig.so/services/crm-data-migration)[HubSpot to Salesforce migration](https://rig.so/migrate/hubspot-to-salesforce)[Salesforce to HubSpot migration](https://rig.so/migrate/salesforce-to-hubspot)[dynamics business central](https://rig.so/dynamics-business-central)[Dynamics 365 Finance and Operations data migration](https://rig.so/migrate/dynamics-365-finance-operations)[Reporting systems migration](https://rig.so/use-cases/bi-migration)[connect dynamics 365](https://rig.so/guides/connect-dynamics-365)[rig map](https://rig.so/products/rig-map)[gateway](https://rig.so/products/gateway)[education software group](https://rig.so/case-studies/education-software-group)

## Sources and product details

Vendor information checked on 20 November 2026. Confirm current editions, licence terms and prices with the vendor before buying.

- [Microsoft: import data in model-driven apps](https://learn.microsoft.com/en-us/power-apps/user/import-data)
- [Microsoft: manage configuration data](https://learn.microsoft.com/en-us/power-platform/admin/manage-configuration-data)

Talk to Rig

## Plan the move around the work you need to keep

Tell us where your team spends time, loses money or needs better information.
In a 30-minute call, we’ll discuss the data and systems work that could help.

[Request a migration readiness check](https://rig.so/book-demo)Use the platform with your team, or add our engineers.

---

- [This page as HTML](https://rig.so/migrate/dynamics-365-crm)
- [Site map for language models](https://rig.so/llms.txt)
- [API and agent documentation](https://rig.so/developers)
