Custom Software
Salesforce to HubSpot Migration: Step-by-Step Plan and Field Mapping
Teams move from Salesforce to HubSpot to cut licence costs, simplify a CRM that only admins understand, or bring sales and marketing into one tool. The move itself is mostly a data-mapping exercise. Done carefully, nothing is lost. Done in a hurry, you lose activity history, deal associations and reporting. This guide gives you the mapping table and a step-by-step plan.
Related service: CRM migration services
By Touseef · October 30, 2026 · 4 min read · Updated October 30, 2026
Salesforce to HubSpot object mapping
| Salesforce object | HubSpot object | Notes |
|---|---|---|
| Lead | Contact | Set lifecycle stage to Lead; keep lead source and status as properties |
| Contact | Contact | Associate to the Company; keep the Salesforce ID |
| Account | Company | Use the domain to de-duplicate; keep parent accounts as parent companies |
| Opportunity | Deal | Map stages to a HubSpot deal pipeline; associate to Company and Contacts |
| Opportunity Stage | Deal stage | Recreate each stage with matching win probability |
| Case | Ticket | Needs Service Hub; map status and priority |
| Task, Event, Activity history | Tasks, meetings, calls, notes | Import as engagements linked to the right records |
| Product, Price Book | Product library, line items | Recreate products first, then line items on deals |
| Campaign | Campaign or list | Campaign object depends on the HubSpot Marketing Hub tier |
| Custom object | Custom object or properties | HubSpot custom objects require Enterprise |
| User, record owner | User, owner | Create users first so ownership maps correctly |
When does moving from Salesforce to HubSpot make sense?
Moving from Salesforce to HubSpot makes sense when your team finds Salesforce too complex, you pay for features nobody uses, or marketing already runs in HubSpot. It makes less sense if you depend on heavy Apex code, complex territory rules or deep Salesforce-only integrations, which need rebuilding or replacing.
List every automation, integration and report you use today before deciding. That list becomes the rebuild scope, and it is often larger than expected.
How do you map Salesforce fields to HubSpot properties?
Map fields by exporting the Salesforce field list for each object, deciding for each field whether to keep, merge or drop it, and creating a matching HubSpot property with the same type. Picklists must have matching options, and lookup fields become associations, not text.
Create a property such as salesforce_id on every object. It lets you match records during import, link associations, and trace any record back after the move.
Common field mappings
| Salesforce field | HubSpot property | Watch out for |
|---|---|---|
| Lead Status | Lead status | Option values must match exactly |
| Lead Source | Original source or custom property | HubSpot’s Original source is set automatically |
| Owner | Contact / Company / Deal owner | Owners must exist as HubSpot users first |
| Amount, Close Date | Amount, Close date | Currency settings if you sell in several currencies |
| Stage | Deal stage | Stage names and probabilities per pipeline |
| Record Type | Pipeline or custom property | Several record types often map to several pipelines |
| Created Date | Custom property | HubSpot sets its own create date on import |
What are the steps in a Salesforce to HubSpot migration?
A Salesforce to HubSpot migration has seven steps: audit, clean, map, build, test import, cutover and validate. Each step has a clear output, and skipping the test import is the most common cause of lost data.
- 1. Audit: list objects, record counts, fields in use, automations, integrations and reports.
- 2. Clean: remove duplicates, empty fields and dead records in Salesforce before export.
- 3. Map: object and field mapping sheet, signed off by sales and marketing.
- 4. Build: create HubSpot properties, pipelines, users, teams and workflows.
- 5. Test import: import a sample, check associations, owners, stages and activities.
- 6. Cutover: freeze Salesforce edits, run the full import, switch integrations.
- 7. Validate: compare record counts, spot-check records, rebuild key reports, train the team.
How long does the migration take and what does it cost?
A Salesforce to HubSpot migration for a small or mid-sized team usually takes two to six weeks, depending on record volume, custom objects, automations and integrations. Data import is fast; mapping, rebuilding automations and testing take most of the time. WebsNexus CRM data migrations start from $300, with a fixed quote after a short audit.
Budget separately for HubSpot licences, any integration rebuilds and team training. Run both systems in parallel for a short period so nothing is missed at cutover.
What data is most often lost in a CRM migration?
The data most often lost is activity history, associations between records, attachments and anything stored in custom objects. These do not come across in a simple CSV import. Ownership and created dates are also commonly overwritten unless they are mapped to properties.
- Emails, calls and notes not linked to the right contact or deal.
- Deals no longer associated with their company.
- Attachments and files left behind in Salesforce.
- Original created dates replaced by the import date.
- Picklist values that did not match and were dropped.
Should you use a migration tool or an agency?
Use HubSpot’s import tools or a migration app for a simple move with standard objects and little history. Use an agency when you have custom objects, many automations, integrations to rebuild, or years of activity data. The mapping and validation work is where errors happen, and tools do not make those decisions for you.
Note that HubSpot’s native Salesforce connector syncs data between two running systems; it is not designed as a one-time migration tool, although it can help during a parallel-run period.
Frequently asked questions
Can you migrate Salesforce to HubSpot without losing data?
Yes, if every object and field is mapped, record IDs are kept, a test import is checked and record counts are compared after cutover.
How long does a Salesforce to HubSpot migration take?
Usually two to six weeks for a small or mid-sized team. Large data volumes, custom objects and many automations add time.
Does HubSpot have a Lead object like Salesforce?
HubSpot stores leads as Contacts and uses lifecycle stage and lead status to separate them. Salesforce Leads and Contacts both become HubSpot Contacts.
Can I migrate Salesforce custom objects to HubSpot?
Yes, to HubSpot custom objects, which require an Enterprise subscription. Otherwise, custom object data has to be stored as properties or associated records.
How much does CRM migration cost?
It depends on record volume, objects, automations and integrations. WebsNexus CRM data migrations start from $300 with a fixed quote after an audit.
Should we run Salesforce and HubSpot in parallel?
A short parallel run, often one to two weeks, helps catch missing data and gives the team time to switch. Freeze edits in Salesforce at final cutover.
Sources
Related articles
- How to Build a Custom CRM for Your Business: Steps, Modules, Stack and Cost
How to build a custom CRM: build vs buy, a requirements checklist, core modules, tech stack, 8 build steps, timeline, cost, and no-code vs custom code.
- Custom CRM vs HubSpot vs Salesforce: 3-Year Cost and When to Choose Each
Custom CRM vs HubSpot vs Salesforce compared on 3-year cost with seat fees, setup time, fit and data ownership, with a simple rule for when to choose each.
- How Much Does a Custom CRM Cost in 2026? Prices, Timelines and Hidden Costs
Custom CRM development costs from $2,000 for a focused first version to $5,000+ for multi-role platforms. See what drives the price and when it beats HubSpot.