Key takeaways
- Move to Salesforce because of a real constraint, like complex territories, approvals or reporting, not because HubSpot feels small.
- Map the data model first. HubSpot's contacts, companies and deals don't line up one-to-one with Salesforce's leads, contacts, accounts and opportunities.
- Rebuild automations from scratch on purpose. Copying every workflow across means copying every old mistake.
Picture a 60-person sales team on HubSpot. Territories keep changing, finance wants approval steps on discounts, and the forecast lives in a spreadsheet because the reports can’t slice it the way the CFO asks.
That’s a normal reason to look at Salesforce. This is the plan we’d follow for a HubSpot to Salesforce migration, from the decision to move through to cutover.
Decide whether you should move at all
HubSpot is a good CRM. Plenty of teams outgrow it in specific ways, and plenty don’t.
Moving usually makes sense when you need:
- Complex territory, account hierarchy or partner models.
- Multi-step approvals and quoting rules.
- Custom objects and reporting beyond what your HubSpot tier handles comfortably.
- A tighter fit with a Salesforce-based finance, service or ERP stack.
If the main complaint is “reps don’t update it”, a new CRM won’t fix that. You’ll just have the same problem in a more expensive tool. Our Salesforce vs HubSpot vs Zoho comparison is a good sanity check before you commit.
Map the data model first
This is where most surprises live. HubSpot has contacts, companies and deals. Salesforce has leads, contacts, accounts and opportunities, and the split matters.
| HubSpot | Salesforce | Watch out for |
|---|---|---|
| Contact (lifecycle: lead) | Lead | Decide your rule for when a person is a lead vs a contact |
| Contact (customer or opportunity) | Contact on an Account | Every contact needs an account, so orphans must be fixed |
| Company | Account | Parent/child hierarchies don’t carry over by default |
| Deal | Opportunity | Pipelines become record types or stages, plan them |
| Associations | Lookups and contact roles | Many-to-many links need a clear design |
| Custom objects | Custom objects | Rebuild only the ones still in use |
Here’s an illustration (not a quote): a team has 40,000 HubSpot contacts, but only 9,000 are tied to a company with activity in the last two years. Those 9,000 become contacts under accounts. The rest go into a lead table or an archive, so nobody has to decide record by record.
Write the mapping in one sheet: source field, target field, transformation, owner of the decision. Then get sales leadership to sign it off before anyone builds anything.
Clean the data before you move it
Dirty data is cheaper to fix in HubSpot, where people still know what each field means. Merge duplicate companies, fix contacts with no company, standardise country and industry values, and reassign records owned by people who’ve left.
Our CRM data hygiene checklist covers the order to do it in. For a migration, dedupe first, then required fields, then formats.
Weighing a move from HubSpot to Salesforce?
Book a free 30-minute consultation. We'll review your current HubSpot setup, your integrations and your timeline, and show you how a low-risk migration would work for your team.
Decide how much history to bring
This is a scoping decision, not a technical one. The more you bring, the longer every trial import takes and the more old mess you inherit.
You don’t need everything. A sensible default:
- All active accounts, contacts and open opportunities.
- Closed-won deals you report on, usually the last two to three years.
- Notes and logged activities for active accounts.
- Everything else archived in a spreadsheet or warehouse.
Marketing history is a separate question. If you keep HubSpot Marketing Hub, form fills and email engagement stay there, and you sync only the fields sales needs. If you’re leaving HubSpot entirely, plan where campaign history will live.
Rebuild automations on purpose
HubSpot workflows don’t convert to Salesforce Flow. You rebuild them.
Treat that as a cleanup, not a chore. List every active workflow, mark each as keep, merge or retire, and rebuild only the ones that still earn their place. In our experience, a good share of old workflows turn out to be dead or duplicated.
Rebuild list for each automation
- What triggers it, and does that trigger still exist in Salesforce?
- Who owns it and who relies on its output?
- Does it touch an integration, like email, calendar or billing?
- Can it be simpler as a Flow, an assignment rule or a validation?
- How will you test it before reps see it?
Lead routing is the one to get right first. If it’s a pain point today, our lead routing best practices walk through designing rules that don’t break.
Run the migration in stages
Set up objects, fields, record types, users and permissions before any data goes in.
Load a full copy, then have reps check their own accounts and open deals.
Put HubSpot into read-only for a day or two, then load what changed.
Point forms, email, calendar and enrichment at Salesforce.
Keep someone on call for the first week for permission and field issues.
Check record counts for every object after each trial, compare open pipeline value with HubSpot, and review a sample of 50 deals for owner, stage and close date. Expect the first trial to look rough. That’s what it’s for.
We cover the general version of this in our CRM migration checklist.
Plan adoption before go-live
A migration isn’t finished when the data lands. It’s finished when reps stop keeping notes elsewhere.
Train each role on the three things they do daily, not on every feature. Retire old HubSpot dashboards so there’s one source of truth, and review usage after 30 days. Keep HubSpot read-only for a few months as a safety net.
If you’d like experienced help, our Salesforce implementation team handles migrations like this, and we’re happy to work from your current HubSpot setup.
The bottom line
A HubSpot to Salesforce migration is a data-model and process project with a software switch at the end. Be clear on why you’re moving, map objects before you build, rebuild automations deliberately, and trial twice before cutover.
If you’d like a second opinion on scope or timing, book a free 30-minute consultation and we’ll go through it with you.
Want this working for your team?
Book a free 30-minute consultation. We’ll review your current setup and use cases, show you how it would work for you, and leave you with a recommended plan.