Migration guide
HubSpot to Salesforce migration: the complete guide
A HubSpot to Salesforce migration takes 6 to 14 weeks for most companies and costs $30,000 to $120,000 in partner fees. The work is 70% data and process and 30% configuration. The four things that decide whether it goes well: mapping HubSpot's flat contact-and-company model onto Salesforce's account-contact-opportunity model, deciding what to do with HubSpot's lifecycle stages, migrating engagement history rather than just records, and running both systems in parallel for a defined cutover window rather than flipping overnight.
Last updated July 30, 2026 · Skydog Ops
When the move is justified
If none of these apply, staying on HubSpot is often the better commercial decision. A migration that exists only because Salesforce feels more enterprise usually delivers a more expensive version of what the team already had.
- Sales process complexity has outgrown HubSpot deal pipelines — territory rules, approvals, multi-currency, or product-level quoting.
- Quote-to-cash requirements: CPQ, subscription amendments, and revenue recognition.
- An acquisition or parent company standardizing on Salesforce.
- Regulated industry requirements around audit trail, field history, and record-level access control.
- Integration depth with ERP, billing, or industry systems where Salesforce has mature connectors and HubSpot does not.
The data model translation
| HubSpot | Salesforce | Watch out for |
|---|---|---|
| Contact | Contact (or Lead) | Decide the lead-vs-contact rule before migrating, not after |
| Company | Account | HubSpot allows contacts with no company; Salesforce contacts need an account |
| Deal | Opportunity | Deal stages rarely map one-to-one; consolidate before migrating |
| Lifecycle stage | Lead Status + Contact/Account fields | No native equivalent — this is the most common mapping mistake |
| Ticket | Case | Requires Service Cloud licensing |
| Custom object | Custom object | Relationships must be rebuilt, not imported |
| Workflow | Flow | Rebuild, do not translate; automation logic rarely survives a literal port |
| Engagement / activity | Task, Event, EmailMessage | Frequently skipped; skipping it destroys pipeline history |
Migration sequence that works
- Weeks 1 – 2: audit. Export every object, count records, identify duplicates, and list every integration and workflow currently firing in HubSpot.
- Weeks 3 – 4: design. Salesforce data model, field mapping document, lead-vs-contact rule, stage consolidation, and access model.
- Weeks 5 – 8: build and test migration. Load into a full sandbox, validate record counts and relationship integrity, and have sales leadership review real pipeline in the sandbox.
- Weeks 9 – 10: integrations and automation rebuild. Marketing, billing, enrichment, and sequences.
- Week 11: parallel run. Both systems live, HubSpot read-only for new deals.
- Week 12: cutover and enablement. Freeze HubSpot, final delta migration, training, and a two-week hypercare window.
What goes wrong
- Migrating records without engagement history. Pipeline that has no emails, calls, or notes behind it is not trusted, and the team goes back to their inbox.
- Keeping HubSpot for marketing without deciding which system owns the contact. Two owners means two truths and constant sync conflicts.
- Porting every custom property. Most HubSpot properties are unused; migrating them all creates a cluttered org on day one.
- No parallel period. A hard cutover with no fallback turns a data issue into a revenue incident.
- Forgetting the forms and the website. HubSpot forms feeding a system nobody uses is the most common post-migration leak.
The hybrid option
Many companies keep HubSpot Marketing Hub and move sales to Salesforce, connected by the native HubSpot–Salesforce integration. This is a legitimate end state, not a compromise, and it is often cheaper than replacing marketing automation at the same time. It requires one decision to be made explicitly: Salesforce owns the account, contact, and opportunity records; HubSpot owns campaign, email, and web engagement. Sync rules follow that boundary.
How Skydog runs migrations
Skydog Ops is both a Salesforce Consulting Partner and a HubSpot Solutions Partner, which is unusual and directly relevant here — the migration is designed by people who know what is being left behind, not just what is being built.
Engagements are fixed-price by phase, staffed with a Forward Deployed Engineer, and include a parallel-run period and post-cutover hypercare.
FAQ
Common questions
How long does a HubSpot to Salesforce migration take?
Six to fourteen weeks for most companies. A simple migration with under 50,000 records and few integrations can complete in 6 weeks. Complex migrations with custom objects, heavy automation, and ERP integration take 12 to 14 weeks including a parallel-run period.
How much does it cost to migrate from HubSpot to Salesforce?
Partner fees typically run $30,000 to $120,000, plus Salesforce license costs. The main cost drivers are record volume and data quality, the number of integrations to rebuild, and whether engagement history is migrated alongside records.
Can you migrate HubSpot data to Salesforce automatically?
Records can be exported and loaded with standard tools, but the mapping is not automatic. HubSpot's flat contact-and-company model and lifecycle stages have no direct Salesforce equivalent, and workflows have to be rebuilt as Flows rather than translated.
Should we keep HubSpot for marketing after moving to Salesforce?
Often yes. Keeping HubSpot Marketing Hub connected to Salesforce via the native integration is a common and stable end state. The requirement is an explicit ownership boundary: Salesforce owns accounts, contacts, and opportunities; HubSpot owns campaigns and engagement.
What data gets lost in a HubSpot to Salesforce migration?
Nothing has to be lost, but engagement history, workflow enrollment history, and marketing email history are the things most often left behind to save time. Losing engagement history is the single biggest driver of poor adoption after cutover.
Is Salesforce better than HubSpot?
Not inherently. HubSpot is faster to adopt and cheaper to run. Salesforce is more configurable and handles complex sales process, quoting, and regulated requirements better. The right answer depends on whether your process complexity has genuinely outgrown HubSpot or whether the problem is how HubSpot was set up.
