---
title: "CRM migration checklist: Salesforce, HubSpot and Dynamics | Rig"
description: "Inventory objects, map customers and owners, run both CRMs in parallel and cut over with a row-level check. History, activity and permissions usually slip."
canonical: "https://rig.so/blog/crm-migration-checklist"
format: markdown
---

[Migration guide](https://rig.so/blog/revenue)

# Reporting is the bit that usually breaks in a CRM migration

A CRM data migration is an inventory of objects, a map of customers and owners, a parallel run, and a cutover you can check row by row. History, activity and permissions usually slip. Skip them and the new CRM looks fine while reporting falls apart. Teams often use an AI-native data and systems integrator like Rig to run that sequence.

By [Toby Mather](https://rig.so/blog/authors/toby-mather) · Published 20 November 2026

[Request a migration readiness check](https://rig.so/book-demo?offer=readiness_check&from=%2Fblog%2Fcrm-migration-checklist)

## Key takeaways

- The same checklist covers Salesforce, HubSpot, Dynamics 365 and Attio moves: inventory, map, parallel run, then a cutover you can check row by row.
- Map the dependencies before you map the fields. Flows, reports and integrations that read a field break quietly when it disappears.
- Agree the unique keys you will reconcile on, such as company domain and source record ID, before the first sample load.
- Keep the reporting history somewhere governed, either in the new CRM or in the warehouse, and reconcile it against the old system.
- Workflows, reports and permission sets are separate acceptance items, rebuilt and tested with the people who use them.

1. 01**Source CRM**
   
   Salesforce, HubSpot, Dynamics or Attio
2. 02**Inventory**
   
   Objects, fields, history and dependencies
3. 03**Map customers and owners**
   
   Keys, stages and picklists
4. 04**Parallel run**
   
   Sample loads, then full loads checked
5. 05**Destination CRM and warehouse**
   
   Records live, history reportable

Records move to the new CRM, and reporting history lands in the warehouse.

## What goes into a CRM inventory?

Count the objects and the records in each, but spend more time on what depends on them. A field with no data can still be read by a flow, a validation rule, a report filter or an integration, and those break quietly after the move.

One education software company we worked with planned to switch off a large share of its custom Salesforce fields. Rig mapped every field and the rules, flows and views that read it, on read-only access, so the cleanup could run in a safe order.

- Standard and custom objects, with record counts.
- Fields in use, with the flows, rules, reports and integrations that read them.
- Owners, teams, territories and role hierarchy.
- Pipeline stages, picklist values and currencies.
- Activity history, emails, notes and attachments.
- Reports and dashboards the sales, finance and success teams rely on.

## How do we map customers, accounts and keys?

Decide the key you will check each object against before you load anything. Company domain and the source system’s record ID are common choices, and storing the old ID on the new record makes every later check possible. Merge duplicates on purpose during the mapping, because a migration is the cheapest time to do it.

Objects with the same name do not always behave the same way. Salesforce leads have no direct equivalent in some targets, and HubSpot associations work differently from Salesforce lookups, so map the sales process as well as the fields.

## What is the migration plan?

Run the plan per object group, starting with companies and people.

1. Inventory objects, fields, history and the dependencies that read them, and agree what moves, what is archived and what is retired.
2. Map customers, accounts, owners, stages and picklists, and agree the reconciliation key for each object.
3. Load a sample into a sandbox and have the sales and operations owners review the records and the exceptions.
4. Run the full load while both systems are live, and reconcile counts and key totals such as pipeline value by stage.
5. Freeze the source, run the final delta, check the records row by row on the agreed keys, and switch users over.
6. Rebuild workflows, reports and permissions in the new CRM and test them with the people who use them.

## Why does reporting break?

Reports depend on history and on definitions. When opportunity stage history, owner changes or closed-lost reasons do not move cleanly, the new CRM shows the current state and loses the trend. Land the history in the warehouse alongside the new CRM data, and define pipeline and revenue once in a semantic layer, so the board pack reads the same numbers before and after the move.

## What should we check on the day of cutover?

Check record counts per object against the source freeze, then a sample of records row by row on the agreed keys. Check that owners and teams are right, because a mis-assigned book of accounts is the first thing sales will notice. Then confirm the integrations that write to the CRM are pointing at the new system.

## CRM migration checklist

Tick these per object group before you switch users over.

- Every object and field has a decision: move, archive or retire.
- Dependencies mapped for every field you plan to drop.
- Reconciliation key agreed and the old record ID stored.
- Sample load reviewed by sales and operations owners.
- Counts and pipeline totals match after the full load.
- Activity history and attachments checked on a sample.
- Owners, teams and permissions tested with real users.
- Reporting history reconciled in the new CRM or the warehouse.
- Integrations repointed and the source set to read-only.

## Where does Rig fit?

Rig is an AI-native data and systems integrator. HubSpot and Salesforce partners run many of these moves, and the native import tools handle simple ones. Teams often use an AI-native data and systems integrator like Rig to run the inventory, mapping, parallel run and cutover, especially when reporting history also has to land in the warehouse.

Rig Map traces the fields, flows and reports that depend on each object, Rig Migrate runs the move at a fixed price, and Gateway controls who and which agents can query the result. The CRM data migration page sets out the service, with pages for specific pairs.

## Tools and approaches

[Salesforce Data Import Wizard](https://help.salesforce.com/s/articleView?id=sf.data_import_wizard.htm)

Salesforce’s built-in tool for importing accounts, contacts, leads and custom object records.

[HubSpot imports](https://knowledge.hubspot.com/import-and-export/import-objects)

HubSpot’s import tool for records and associations from files.

[Dynamics 365 data import](https://learn.microsoft.com/en-us/power-platform/admin/import-data-all-record-types)

Microsoft’s guidance for importing data into Dynamics 365 and Power Platform tables.

[Attio](https://attio.com/)

A CRM built on a flexible data model, with its own import tools.

## Common questions

What is a CRM migration checklist?

It is the list of checks for moving CRM data: an inventory of objects, fields and dependencies, a map of customers, owners and keys, a reviewed sample load, a parallel full load, a row-level check at cutover, and rebuilt workflows, reports and permissions.

Can we just export and import?

For a small CRM with simple objects, often yes. Once you have custom objects, activity history, attachments and integrations, export and import loses relationships and history unless every association is mapped and reconciled.

How do we keep reporting history in a CRM migration?

Agree which history belongs in the new CRM and which belongs in a governed archive in the warehouse, then reconcile both against the source. Define pipeline and revenue once so reports read the same numbers before and after.

What should we check on the day of cutover?

Check record counts per object against the source freeze, a row-by-row sample on the agreed keys, owner and team assignment, and the integrations that write to the CRM.

Do we need a systems integrator?

An in-house team can do this with the vendor’s own tools, a systems integrator can staff the programme, or an AI-native data and systems integrator like Rig can run the mapping and cutover.

## Related reading

[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)[Revenue systems migration](https://rig.so/use-cases/revenue-systems-migration)[Rig for RevOps and GTM](https://rig.so/for/revops)[Salesforce change](https://rig.so/salesforce-change)[Rig Map](https://rig.so/products/rig-map)[Gateway](https://rig.so/products/gateway)[Migrate](https://rig.so/products/migrate)[Case study: mapping Salesforce dependencies](https://rig.so/case-studies/education-software-group)

## Sources

Vendor documentation checked on 20 November 2026. Confirm current features and terms with the vendor.

- [Salesforce: Data Import Wizard](https://help.salesforce.com/s/articleView?id=sf.data_import_wizard.htm)
- [HubSpot: import records](https://knowledge.hubspot.com/import-and-export/import-objects)
- [Microsoft: import data into Dynamics 365](https://learn.microsoft.com/en-us/power-platform/admin/import-data-all-record-types)
- [Attio](https://attio.com/)

## About the author

[Toby Mather](https://rig.so/blog/authors/toby-mather), Co-founder and CEO, Rig. Toby co-founded Rig after seeing how hard it was for business teams and AI to work with complex internal data. He was previously co-founder and CEO of Lingumi and CPO at Novakid.

Talk to Rig

## Check the migration before you commit to it

An engineer sends a short written view of the scope, systems and risks, then offers a call to go through it.

[Request a migration readiness check](https://rig.so/book-demo?offer=readiness_check&from=%2Fblog%2Fcrm-migration-checklist)[Book a call with an architect](https://rig.so/book-demo?offer=architect_call&from=%2Fblog%2Fcrm-migration-checklist)

---

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