Hoppa till innehåll
All guides
CRMHard

Migrating from Salesforce to HubSpot: Complete Playbook

A battle-tested, step-by-step guide covering data mapping, migration execution, validation, and team training. Written from 20+ real migrations.

From

Salesforce

To

HubSpot

4-8 weeks 25 min read Simon AxelssonUpdated 2026-04-02
1.1

Audit your Salesforce org

Run a full object and field inventory. Export metadata using Salesforce Inspector or Workbench. Identify custom objects, formula fields, validation rules, and Apex triggers that may need equivalents in HubSpot.

Watch for Person Accounts

If your Salesforce org uses Person Accounts (B2C model), this significantly complicates mapping to HubSpot's Contact + Company model. Budget an extra 1-2 weeks.

1.2

Define HubSpot target architecture

Decide which HubSpot hubs you need (Marketing, Sales, Service, Operations) and which tier (Starter, Professional, Enterprise). Map Salesforce concepts to HubSpot equivalents.

1.3

Stakeholder alignment

Get sign-off from sales leadership, marketing, and IT. Define success criteria: what does a successful migration look like? Set a freeze date for Salesforce changes.

Pro tip

Run a 2-week parallel period where both systems are active. This builds confidence and catches edge cases before the cutover.

Common Pitfalls

#1

Ignoring Salesforce Lead vs Contact model

Salesforce separates Leads and Contacts. HubSpot merges them into a single Contact object. If you don't plan this merge, you'll end up with duplicates.

Fix: Merge Salesforce Leads and Contacts by email address before import. Decide which record wins when fields conflict.

#2

Breaking deal stage history

Importing deals with a current stage but no stage history loses pipeline velocity data. You can't report on time-in-stage after migration.

Fix: Use HubSpot's timeline API to create historical stage change events. This preserves the full deal progression timeline.

#3

Forgetting activity associations

Emails, calls, and notes in Salesforce are associated to Leads/Contacts AND Opportunities. If you only migrate the activity but not the association, they appear as orphaned.

Fix: Migrate activities with explicit associations to both Contact and Deal records using the HubSpot Associations API.

#4

Not testing picklist value mapping

Salesforce picklist values rarely match HubSpot dropdown options exactly. Values like 'Closed Won' vs 'closedwon' will silently fail.

Fix: Build a value mapping table for every picklist/dropdown field. Test with real data before full migration.

#5

Skipping user adoption training

Technical migration s쳮ds but the team reverts to spreadsheets because they don't know HubSpot. This is the #1 reason migrations 'fail'.

Fix: Budget 30% of project time for training. Create role-specific guides and run weekly Q&A sessions for the first month.

Cost Comparison

Estimated monthly costs for a 50-user sales organization. Actual pricing depends on contract terms, feature requirements, and negotiation. All prices in USD.

ItemSalesforceHubSpot
CRM Platform (50 users)$7,500/mo$1,600/mo
Marketing Automation$2,000/mo (Pardot)Included
Service/Ticketing$1,500/mo (Service Cloud)$450/mo
API / Integration costs$300/mo (MuleSoft lite)Free (Operations Hub)
Admin overhead1 FTE ($8,000/mo)0.25 FTE ($2,000/mo)
Total Monthly Cost$19,300/mo$4,050/mo

* Estimates based on publicly available pricing as of April 2026. Does not include one-time migration costs.

Need help with this migration?

SIAX has completed 20+ Salesforce-to-HubSpot migrations for companies ranging from 10 to 500 users. We handle the technical migration, data validation, workflow rebuilds, and team training - so you can focus on selling.