Salesforce to HubSpot · migration readiness guide

Before moving CRMs, decide what the move must protect.

A Salesforce to HubSpot migration lives or dies on account structure, associations, ownership, stage history, integrations and the reports your team relies on. Contacts are the easy part.

This guide covers what needs a mapping, a test and a sign-off before you pick a cutover date.

Start the readiness check Or get a one-page teardown

Free to use. Last reviewed November 9, 2026.

Is moving the CRM the smallest fix?

Many problems that look like the platform are really the setup.

Repair what you have when

The problem is a rule, not the tool

  • A field owner, workflow or matching rule is causing the mess
  • Reports disagree because definitions disagree
  • Your team likes the tool but not the data in it

HubSpot repair · Salesforce repair

Move platforms when

The tool cannot do what you need

  • A requirement the current CRM cannot meet, written down
  • Running two systems costs more than it gives back
  • You have tested how the destination handles your hardest records

Otherwise the move risks rebuilding the same problem in a new interface.

Four sections · 13 checks

The migration readiness check

Thirteen checks to finish before choosing a cutover date.

0 checked

01 Records and objects

Decide what moves before deciding how.

02 Relationships and ownership

Contacts are easy. The links between them are what make the CRM useful.

03 History and reporting

A migration cannot recreate history that was never recorded.

04 Integrations and cutover

The move is not done until everything that wrote to Salesforce writes somewhere on purpose.

Last reviewed November 9, 2026 by Luis García Checked against HubSpot and Salesforce documentation linked in each check

Test the hard records before the import.

A mapping sheet lists every object, where it lands, what can go wrong and how you will know it worked.

Migration mapping sheet · excerpt Salesforce to HubSpot Illustrative

Five rows from a mapping sheet

SalesforceHubSpotRiskPasses when
AccountCompanyParent accounts and name-only duplicatesThe ten test accounts keep every contact and deal
OpportunityDealHistory exists only for tracked fieldsStage dates match Salesforce for a sample quarter
Contact roleAssociation labelRoles with no matching label disappearDecision-maker and billing contacts keep their role
LeadContact with lifecycle stageConverted and open leads get mixedLead counts by status match before and after
User (owner)OwnerInactive users own live recordsNo open record is left without an owner

Illustrative excerpt. Your objects and rules decide the real sheet.

Matching totals is not the same as a working CRM.

Count checks pass on day one. Usability checks are what your team notices.

Before

Counts match

Companies imported4,200 of 4,200
Contacts imported19,000 of 19,000
Deals imported2,300 of 2,300

Everything looks done. Nobody has opened an account yet.

After

The records are usable

Test accounts with every contact and deal10 of 10
Open deals with an active owner2,180 of 2,300
Last quarter’s closed-won totalMatches Salesforce
Decision-maker roles keptLabels missing

Two problems found before go-live, not after.

Illustrative, not a client result Made-up numbers to show the difference between counting and checking.

Plan the transition and the way back.

A backup file is not a rollback plan once new activity starts arriving.

  1. Map

    Every object, field and owner, with the Salesforce ID kept.

    Mapping sheet signed off
  2. Test

    The ten hardest accounts and the five leadership reports.

    Test results reviewed
  3. Freeze

    Final export, with a plan for changes made after it.

    Freeze window agreed
  4. Import and check

    Counts, links, owners and report totals.

    Differences explained
  5. Go live or pause

    The named owner signs off, or the pause conditions apply.

    Decision recorded

How a migration relates to the 21-day build.

The 21-day build makes one CRM work: data, routing, outbound and reporting. A migration is its own project, with its own scope, price and timeline, confirmed in writing before anyone commits to a move.

See what the 21-day build includes

Sources used in this guide

Migration questions

Can every Salesforce record and activity move unchanged?

Do not assume so. Verify mappings and destination behavior for each required record type, relationship and history item.

Does a HubSpot implementation include migration automatically?

Not automatically. Setup, repair and migration are scoped separately. Ask what is inspected, moved, rebuilt, tested and accepted.

How long should the move take?

There is no defensible universal timeline from the contact count alone. Dependencies, data quality, integration behavior and transition requirements must be established first.

What should an acceptance check include?

The records, relationships, ownership and reports the business agreed must remain usable, plus documented limitations and a named person authorized to sign off.

Not sure the move is the fix?

Send your website, your current CRM and why you are considering a move. The teardown tells you whether the problem is the platform or the setup.

Get a one-page teardown

Written by Luis, back within 1 business day. Includes which option fits. No call needed. Prefer to talk? Book a 20-minute fit call.

Sample teardown · real, anonymized Acquired customers are a migration, not a pipeline. One page for a new CRO, written from public information before any call: what public signals show, the likely gap, the fix order and one CRM pull to check it. Read the full page →