A CRM Migration Plan That Keeps History, Owners and Automation Intact

Plan it in five stages: audit and clean the existing data, map objects, fields and relationships to the new CRM, test the import on a sample, migrate in dependency order with stable IDs, then validate counts and relationships before switching users over. History survives when associations and activity records are carried across with their original dates and owners, which needs planning before the first import.

The import tool is rarely the hard part. The hard part is deciding what the data means and which of it is worth keeping.

Merge duplicates, standardise values such as countries and industries, retire fields nobody uses, and decide a cut-off for old records — for example, contacts with no activity and no deal in five years. Agree with sales and marketing which history they genuinely use: open deals and recent activity usually matter; a decade of email opens rarely does.

Document every field mapping, including picklist values that change and fields that merge. That document becomes the reference when a user asks where something went.

Import parent records before children so associations can be made: users and owners, then companies, then contacts, then deals or opportunities, then activities and notes. Carry a stable external ID from the old system on every record so later imports and fixes can match reliably.

Both HubSpot and Salesforce document multi-object imports and data import tools. Test each step on a sample first and compare counts and associations with the source before running the full load.

List every workflow, assignment rule, integration and report in the old system, and for each one decide: rebuild, redesign or retire. Copying automation one-for-one often reproduces problems the migration was meant to fix. Rebuild integrations against the new CRM and test them before cutover.

Freeze changes in the old system during the final load, switch integrations over, then open the new CRM to users with training and a short list of known differences. Keep the old system read-only for a defined period so nobody loses access to history they need.