HubSpot Data Migration: A Practical Plan for Scaling Teams

A HubSpot data migration succeeds or fails before the first record moves. The teams that get it right decide what to keep, define how every field maps, test on a small sample, and name one person who approves go-live. The import itself is the easy part. If your move involves Salesforce, Marketo or a stack of connected tools, the same plan applies, and having the people who design the plan also build it is what keeps it from drifting. That is how we run migrations at Quick To Impress, with senior strategists staying on through implementation.
TL;DR
- Audit data, integrations, customizations and workflows first, then sort every object into migrate, archive or leave behind.
- Build a field inventory before you build anything in HubSpot. Mapping is where most migrations quietly go wrong.
- Run a test import on a small sample and review field values, associations and activity history before the full load.
- Validate with record-count reconciliation, spot checks and sign-off from a handful of real users, and name the go/no-go owner on day one.
- Salesforce and Marketo moves are different problems: one is mostly about objects and relationships, the other about marketing assets that do not arrive as data.
Table of Contents
- What a migration into HubSpot actually involves
- Step 1: Audit before you move anything
- Step 2: Map objects and fields
- Step 3: Clean the data once, at the source
- Step 4: Run a test import and review it
- Moving from Salesforce to HubSpot
- Moving from Marketo to HubSpot
- Step 5: Validate before you cut over
- Cutover and hypercare
- A migration checklist you can copy
- Our perspective
- Where we can take it from here
- FAQ
- Sources
What a migration into HubSpot actually involves
Most people picture a CSV going in one end and contacts coming out the other. For a small list that is accurate. For a scaling company it is a small fraction of the work.
A real migration moves companies, contacts, deals and tickets, but also the relationships between them, the history of what happened to each record, the properties your reports depend on, and the automations that act on all of it. A multi-location brand has location records tied to parent accounts. A B2B SaaS company has product usage and subscription data tied to deals. Each of those relationships has to survive the move.
HubSpot’s own CRM data migration guide breaks the work into eight phases: assess, cleanse, map, test, migrate, validate, cutover and hypercare. It describes hypercare, the period of close monitoring after launch, as typically lasting two to four weeks. Plan your calendar around that whole arc, not around the import day.

Step 1: Audit before you move anything
Start with an inventory of what exists today. HubSpot’s CRM migration guide recommends auditing four areas:
- Data: record volumes, duplicate rates, empty fields and stale records.
- Integrations: every connected tool, which direction it syncs and whether anyone still uses it.
- Customizations: custom fields, custom objects and automations, and the reason each one exists.
- Workflows: active automations, sequences and the reports people open every week.
The last question in each area is the useful one: does anyone still need this? A Salesforce org that has run for eight years usually carries fields nobody has filled in since the last admin left. Moving them costs time and clutters HubSpot from the first day.
Sort what you find into three buckets: migrate, archive and leave behind. Legal and retention requirements, reporting needs and plain business use decide which bucket each item lands in. Email history is a common example. If conversations live in mailboxes rather than in the CRM, the scope of what you carry over is a retention decision, and a look at mailbox migration tools helps frame which of that history is worth moving at all.
Name the person who says go
HubSpot’s staff guidance argues that the most common failure point in a migration is ambiguity over who approves the go/no-go decision, and that this person should be defined before the project starts (HubSpot). Pick one accountable owner, usually the head of revenue operations, marketing or sales. Give them the validation results and let them decide.
Step 2: Map objects and fields
Mapping is the document that every later step depends on. Build a field inventory spreadsheet with, for each field:
- source field name and type
- source picklist values
- destination field name and type
- destination picklist values
- whether a transformation is needed
- migration status
That list comes from HubSpot’s migration process overview. The picklist columns matter more than they look. If your old system has twelve values for lead source and HubSpot should have six, someone has to decide how twelve become six before the data moves, not after. If your lead source values are already inconsistent, fix the taxonomy first; our guide to building a lead source taxonomy shows how to make one that holds up.
Choose the right HubSpot structure
HubSpot’s Salesforce implementation planning guide separates four kinds of destination:
- Standard properties for basic contact, company, deal and ticket data.
- Custom properties for fields specific to your business.
- Custom objects for complex relational data that does not fit the standard four.
- Activities for calls, emails, meetings and notes.
If you have objects such as subscriptions, locations or installed products, decide now whether they become custom objects. Our practical setup guide to HubSpot custom objects covers when that is the right call and how to design the associations.
Plan for how the file is built
HubSpot’s import tool needs a .csv, .xlsx or .xls file with one sheet and a header row in which each column matches a HubSpot property. Limits depend on your subscription: on free tools, files up to 20 MB and up to 500,000 rows per day, and on Smart CRM, Starter, Professional or Enterprise, files up to 512 MB and 500 imports per day (HubSpot import file requirements). A large database therefore becomes several files, and the order matters, because associations need the records they point to.
Step 3: Clean the data once, at the source
Cleaning in the source system is cheaper than cleaning in HubSpot, because you fix a problem once instead of after it has multiplied across associations. The checks that pay off most:
- Email as the contact key. Contacts without an email address cannot be deduplicated reliably, so decide how to treat them.
- Company domains. A consistent website or domain field is the cleanest way to match contacts to companies and catch duplicate accounts.
- Property types. A date stored as text or a number stored with currency symbols will fail or distort on import.
- Name fields. Split full names into first and last name if the source stores them together.
- Stale records. Merge or archive what nobody has touched, using the rules you set in the audit.
HubSpot’s import checklist puts cleaning right after export and before mapping, which is the order that saves rework.
Step 4: Run a test import and review it
The same checklist ends with two steps people skip when the deadline looms: prepare import files with object associations, run a test import, then review the test objects for field mappings, associations and engagement data.
Take a sample that includes your ugly cases: a company with many contacts, a deal with several associated people, a record with a long activity history, a contact with unusual characters in the name. Then check in HubSpot:
- Did every value land in the right property?
- Are contacts attached to the right companies and deals?
- Does the activity timeline show calls, emails, meetings and notes where they belong?
- Do the lists and reports that depend on these fields return sensible results?
Fix the mapping document, not the records. Every correction you make by hand in the test portal will have to be repeated on the real run.
Moving from Salesforce to HubSpot
Salesforce moves are the most common request behind this topic, and they are mainly about relationships. Opportunities, accounts, contacts, campaigns and custom objects each need a home, and the logic that connects them lives partly in Salesforce’s own configuration.
HubSpot’s pre-switch checklist for Salesforce users recommends documenting existing sales processes; recording records, integrations, workflows, lead assignment rules, views, dashboards and reports; merging stale records and removing underused fields; and starting a change-management plan early. That last item is not a formality. Reps who cannot find their pipeline on day one will keep a spreadsheet, and your data quality decays within a quarter.
Decide the source of truth field by field
Some teams run both systems side by side for a period, or permanently. HubSpot’s planning guide defines five sync rules: use Salesforce unless blank, always use Salesforce, two-way, always use HubSpot, and use HubSpot unless blank. It also notes that one platform does not have to be the source of truth for everything (HubSpot). Assigning a rule per field prevents the overwrite loops that make people distrust the data. If you are running both systems during the transition, our admin’s setup guide to the HubSpot and Salesforce integration walks through the configuration.
What to rebuild
Records move as data. Salesforce flows, validation rules, approval processes, assignment rules and reports do not become HubSpot workflows on their own. They are documented in the audit, then redesigned for how HubSpot works, which is often an opportunity to simplify. Handoff rules between marketing and sales deserve particular attention; our MQL to SQL process guide and the sales and marketing SLA guide cover what to define before you rebuild the automation.
Moving from Marketo to HubSpot
A Marketo move differs from a Salesforce move because so much of what you value is not a record. People, companies and their fields move as data. Programs, smart campaigns, forms, landing pages, email templates, scoring models and nurture logic have to be rebuilt in HubSpot to suit its structure.
Plan it in three tracks:
- People data: leads and contacts with their key properties, subscription and consent status, and the lifecycle stage each person should carry in HubSpot.
- Lists and segments: decide which static lists you still need, and recreate dynamic segments from their criteria rather than exporting their membership.
- Marketing assets and automation: inventory every active program, form and email, retire the ones that no longer perform, and rebuild the rest.
Two cautions apply to any marketing platform move. Carry over opt-out and consent status with the contact, so nobody who unsubscribed is emailed again. And preserve original source and campaign information in dedicated properties, because attribution history is very hard to reconstruct later. If reporting is your reason for moving, our practitioner’s guide to HubSpot attribution reporting shows what to capture.
Step 5: Validate before you cut over
HubSpot’s validation guidance gives measurable gates (HubSpot):
| Check | What it asks for |
|---|---|
| Record counts | Reconcile counts per object between source and HubSpot |
| Discrepancies | Investigate any difference over 0.1% before go-live |
| Spot checks | Review 50 to 100 records per object type |
| High-volume objects | Compare automatically by ID |
| User acceptance testing (UAT) | Sign-off by 3 to 5 users as the go/no-go gate |
UAT means the people who will use the system every day try their real tasks in it. Choose users from sales, marketing and service, not only admins. Ask them to build a list, update a deal, find an old email thread and run the report they send to leadership every Monday.
Also confirm the things that are not records: that integrations still sync in the right direction, that workflows trigger on the new properties, that forms create contacts correctly, and that dashboards match the numbers finance recognizes.
Cutover and hypercare
Cutover is the moment the old system becomes read-only and HubSpot becomes the place where work happens. Freeze changes in the source system shortly before the final load so the data does not move under you, communicate the switch date to every team, and keep a rollback plan until the go/no-go owner closes the project. Then use the hypercare window to watch for duplicates, broken automations, sync errors and user questions, and fix them quickly while the move is fresh.
A migration checklist you can copy
- Name the go/no-go owner and the project lead.
- Audit data, integrations, customizations and workflows.
- Sort items into migrate, archive and leave behind, with retention rules.
- Build the field inventory, including picklist transformations.
- Decide standard properties, custom properties and custom objects.
- Clean the source data: duplicates, emails, domains, types.
- Prepare destination properties in HubSpot.
- Prepare import files with associations, in dependency order.
- Run a test import and review mappings, associations and activity history.
- Run the full migration in stages.
- Reconcile counts, spot check records and run UAT.
- Cut over, then run hypercare for several weeks.
Our perspective
Most migrations are scoped as a data project and then discovered to be a revenue operations project. The records are the visible part. The invisible part is the definition of a lead, the handoff to sales, the attribution logic and the reports leadership trusts.
That is why we embed senior strategists with the client team and keep them involved in the build. The person who decides how the pipeline should work is the same person who sees the mapping fail on a Tuesday and adjusts it. Planning and implementation stay in one accountable partnership, so nothing is lost in a handoff between a consultancy that designs and a team that executes.
For scaling teams with complex stacks, a migration is the best moment to simplify. Retire the fields nobody uses, rebuild the automations the right way, and leave with a system your team can grow on.
Service
Where we can take it from here
If your migration touches the CRM, the marketing platform and the integrations between them, our revenue operations service covers HubSpot, Salesforce, Pardot and ActiveCampaign architecture and implementation. Engagements run as monthly capacity on our pricing page: Core capacity at $3,500 to $5,999 per month, Growth capacity at $6,000 to $9,999 per month, and Scale capacity from $10,000 per month.

FAQ
How long does a HubSpot data migration take?
It depends on data volume, how many objects and integrations are involved, and how much cleanup the audit uncovers. The import is usually the shortest phase. HubSpot’s guidance allows for a two to four week hypercare period after launch, so plan beyond the cutover date.
Can I migrate Salesforce activity history to HubSpot?
Yes. HubSpot’s planning guidance lists activities such as calls, emails, meetings and notes as a category you can bring over, alongside standard properties, custom properties and custom objects. Test a sample with long histories first and confirm they appear on the right timelines.
What is the biggest risk in a Marketo to HubSpot migration?
Treating it as a data move only. Contact data transfers, but programs, forms, emails and scoring logic need rebuilding. Carry consent status and original source information with each contact, and inventory your active assets early.
What should I clean before importing into HubSpot?
Deduplicate on email address and company domain, correct property types so values match their destination fields, split combined name fields, and archive stale records. Cleaning at the source means you fix each problem once.
Sources
- CRM data migration: A practical process overview (HubSpot)
- CRM migration guide: Steps, data, and team alignment (HubSpot)
- CRM Data Migration Import Checklist (HubSpot)
- Switching from Salesforce to HubSpot (HubSpot)
- Plan your HubSpot-Salesforce implementation (HubSpot Knowledge Base)
- Format import files (HubSpot Knowledge Base)