Moving From HubSpot to Salesforce? What the Migration Actually Involves
What a HubSpot to Salesforce migration actually involves, how long it takes, and the decisions that make it bigger or smaller.
A HubSpot to Salesforce migration is mostly about setting up Salesforce to match how your team sells, not a data move. The records come across in days. The real work is deciding how HubSpot's simple model of contacts, companies and deals maps onto Salesforce's leads, accounts and opportunities, then rebuilding the automation and reports your team relies on. For a typical B2B sales team, expect three to six weeks from access to a working org where leadership can see pipeline and forecast reports from the first day.
Most of my migration work goes the other way, from Salesforce to HubSpot. But teams do outgrow HubSpot, and when they do, the same rule applies: plan the Salesforce build before you move a single record. Here's what's involved and what makes it bigger or smaller.
Why teams move from HubSpot to Salesforce
The reasons are usually specific, and worth writing down before you start:
- Your data no longer fits contacts, companies and deals. Contracts, sites, programs or assets need their own records, and custom objects in HubSpot need an Enterprise subscription.
- Your sales process got more complex. Territories, approval chains, partner channels, complex quoting or several business lines with different processes.
- Finance, product or support need to work in the same system. Salesforce's ecosystem of apps and integrations is often the deciding factor.
- You're hiring a sales ops team that already knows Salesforce.
If none of these apply and the real complaint is messy pipelines or reports nobody trusts, fix HubSpot first. Moving won't clean anything up for you.
How HubSpot data maps to Salesforce
This is where most of the decisions live. The objects look similar but don't behave the same way.
| HubSpot | Salesforce | What to decide |
|---|---|---|
| Contacts | Leads and Contacts | Which HubSpot contacts are still prospects (Leads) and which belong to a customer or active deal (Contacts) |
| Companies | Accounts | Your duplicate rules, and how to handle companies without a domain |
| Deals | Opportunities | Stage names, probabilities, and how pipelines become record types or sales processes |
| Tickets | Cases | Queues, assignment rules and service processes |
| Associations | Lookups, Contact Roles | HubSpot lets one contact link to many companies freely; Salesforce wants a primary account |
| Workflows and sequences | Flows and sales engagement tools | Rebuild from what the business needs, not step by step |
| Lifecycle stages | Lead status plus opportunity stages | One HubSpot property often splits into two Salesforce concepts |
The Leads question deserves its own meeting. HubSpot keeps everyone as a contact and tracks where they are with lifecycle stage. Salesforce keeps unqualified prospects as Leads and converts them into an Account, Contact and Opportunity when they qualify. Decide the rule up front, or reps will find half their customers sitting in the Leads tab.
Should you keep HubSpot for marketing?
Often, yes. Many teams move sales to Salesforce and keep marketing in HubSpot, connected by HubSpot's native Salesforce integration (it needs a Professional or Enterprise HubSpot subscription). Marketing keeps its emails, forms and lead scoring, and sales gets Salesforce. The trade-off is a sync to own: field mappings, which system wins a conflict, and who fixes errors. If nobody will own that, moving everything at once can be simpler.
How the migration usually runs
- Requirements and design (week 1). Why you're moving, what reports leadership needs on day one, and the object map above, agreed with sales and marketing.
- Salesforce build (weeks 1 to 3). Fields, page layouts, record types, sales processes, duplicate rules, and an integration user for every connected tool.
- Export, clean and load (weeks 2 to 4). Export from HubSpot, dedupe, and load in order: accounts, then contacts and leads, then opportunities, then activity history. Salesforce's Data Import Wizard handles up to 50,000 records per import; larger orgs use Data Loader.
- Automation and integrations (weeks 3 to 5). Rebuild workflows as Flows, reconnect tools, and test the HubSpot sync if marketing stays put.
- Validate and cut over (weeks 5 to 6). Record counts by object, open pipeline by stage, a handful of real accounts checked by hand, then training and a freeze date.
What makes it bigger
- Lots of activity history. Emails, calls and notes are the slowest part to move and match to the right records.
- Dirty company data. Companies without domains and duplicates turn into duplicate accounts that quietly break integrations.
- Many pipelines. Every HubSpot pipeline needs a decision: its own sales process, a record type, or merged into one.
- Custom objects and calculated properties. These need a design in Salesforce, not just a field.
- No owner after go-live. Salesforce rewards ongoing care. Plan who will run it before you move.
How to tell if this is you
- You've signed Salesforce, or you're close, and HubSpot holds years of customer history
- Your deals involve approvals, territories, partners or complex quoting
- You're adding teams (finance, support, product) who need to work in the same system
- You want to keep HubSpot marketing but move sales
- You'll have someone to own Salesforce after launch
FAQ
How long does a HubSpot to Salesforce migration take?
For a typical B2B sales team, three to six weeks from access to a working org with day one reports. The data load takes days. Design, the Salesforce build and validation take the rest.
Can I keep HubSpot for marketing and use Salesforce for sales?
Yes. HubSpot's native Salesforce integration syncs contacts, companies and deals between the two, with a Professional or Enterprise HubSpot subscription. Plan who owns the sync and which system wins a conflict.
Do HubSpot workflows transfer to Salesforce?
No. Workflows, sequences and calculated properties have to be rebuilt in Salesforce, usually as Flows. Rebuild from what the business needs rather than copying each step.
Should HubSpot contacts become Leads or Contacts in Salesforce?
It depends on your rule. A common one: contacts tied to a customer or an open deal become Contacts, and unqualified prospects become Leads. Decide it before the first load.
If you're planning a move to Salesforce and want a second opinion on scope, I'm happy to look at your HubSpot portal. Here's more on my Salesforce consulting, the five decisions I make before any migration (most apply in this direction too), or let's talk.
Eric Rodriguez spent 16 years running revenue and operations teams before building the systems behind them. He runs Scalable Operations, a Salesforce and HubSpot consultancy that does the hands-on work.
More about EricIs your CRM getting in the way?
Start with the free funnel check to see where deals stall. If you would rather talk it through, a 30-minute call is usually enough to tell whether I can help.