HubSpot data migration is the process of moving your contacts, companies, deals, and activity history from a previous CRM or spreadsheets into HubSpot in a clean, structured way. It covers mapping old fields to HubSpot properties, deduplicating records, validating data, and importing in the right order so associations hold and your team starts on records they can trust.
SourceLeadsWon
LINE14238
Website form9621
Facebook7112
Referral4419
What it does
A migration that lands clean, not just copied
The goal is a working CRM on day one, not a pile of imported rows nobody trusts.
Field mapping
Match every source column to a standard or custom HubSpot property before anything imports.
Deduplication
Merge duplicate contacts and companies so one person is one record, not three.
Association mapping
Keep contacts tied to their companies and deals tied to both, using a unique ID column.
Validation
Check formats, required fields, and value spelling before the records hit your live CRM.
Staged imports
Bring objects in the right order so associations resolve cleanly across files.
Leave the junk behind
Decide what stale, dead, or unusable data does not earn a place in the new system.
How to do it
A migration sequence that holds together
-
Export and audit your source dataPull contacts, companies, deals, and activities from your old CRM or spreadsheets. Open each file and note which fields are clean, which are messy, and which are empty. This audit is where you decide the scope of the cleanup.
-
Map fields to HubSpot propertiesMatch each column to a standard property where one exists, and create custom properties for the rest. Set the right field type early. A date stored as free text will not behave like a date once it is inside HubSpot.
-
Clean and deduplicate before importStandardise values like country and lifecycle stage, fix obvious format errors, and remove duplicates. Add a unique ID column to each file so contacts, companies, and deals can be associated to each other during import.
-
Import in order, objects firstBring companies in, then contacts, then deals, using the import flow with the association option so records link back to the right parent. Importing out of order is the most common reason associations break.
-
Validate the result in HubSpotSpot-check a sample of records, confirm associations resolved, and review property values on a saved list view. Fix anything off before your team starts working the data. A short validation pass now saves weeks of confusion later.
Related
Where migration fits in your setup
Data migration is one step inside a wider implementation, and the records you move power everything built on top.
FAQ
Common questions
What can I migrate into HubSpot?
Contacts, companies, deals, tickets, products, and notes or activity history can all move in. Most teams migrate from a previous CRM, a billing or e-commerce system, or a set of spreadsheets. You can import through the in-app import tool with CSV or Excel files, or move larger and more complex datasets through the API or a connector.
How does deduplication work in HubSpot?
HubSpot uses email as the unique identifier for contacts and domain for companies, so records sharing those values can be merged rather than duplicated. For records without those keys, a Record ID column lets you match and update existing records on re-import. Cleaning duplicates before you import is the cleaner path, since merging after the fact is slower and easier to get wrong.
Should I migrate all my historical data?
No. A migration is the best moment to leave junk behind. Dead contacts with no engagement in years, fields your team never used, and data you only kept out of habit do not need to come across. Bringing in less but cleaner data gives your team a CRM they trust from day one, which matters more than a complete archive of records nobody opens.
What usually breaks during a migration?
The two common failure points are associations and field types. Associations break when objects import in the wrong order or without a shared unique ID, leaving contacts floating with no company. Field-type errors happen when dates, numbers, or dropdown values import as plain text, so they will not sort, filter, or trigger automation correctly. Both are avoidable with mapping and a validation pass before go-live.
How long does a CRM migration take?
It depends on data volume, how many objects you are moving, and how messy the source is. A single clean spreadsheet of contacts can import in an afternoon. A multi-object migration from a legacy CRM with custom fields, deal pipelines, and years of activity history tends to run across a structured implementation phase, since the cleanup and validation work, not the import button itself, is where the time goes.