
HubSpotSalesforce Sales Cloud
HubSpot to Salesforce Sales Cloud migration
Migration specialists move your companies, contacts, deals and line items into Salesforce Sales Cloud, check a sample with you first, and count every record on both sides.
Free sample migration of 100 of your records, plus a fixed quote within 24 hours.
Last updated November 2026 · 15 object types mapped
- 1000+migrations
- 15 yearsof collective experience
SOC 2 Type IIGDPR compliantHIPAA compliant
HubSpot to Salesforce Sales Cloud at a glance
A HubSpot to Salesforce Sales Cloud migration sends companies to Accounts, deals to Opportunities and each contact to either a Lead or a Contact, chosen by lifecycle stage. The work sits on both ends: HubSpot's exports leave activities out, and Salesforce accepts original dates, Task subtypes and won or lost status only at insert. HubSpot stays in use until the final delta sync.
- Objects mapped
- 15
- in this route's mapping
- Typical timeline
- About 10 business days end to end
- 3 phases
- Free sample
- 100 records
- checked by your team first
- Quote
- Fixed
- within 24 hours
- Who it is for
- Growing sales teams moving from HubSpot onto Salesforce Sales Cloud, often when the company standardises on Salesforce or needs Sales Cloud forecasting, and wants every deal's history in the new org.
- What does not move
- HubSpot workflows, sequences, snippets, templates, playbooks, reports and saved views. We document each one so your Salesforce admin can rebuild it as flows, templates and list views.
- What sets the scope
- Contacts and companies, deals with line items, the calls, emails and notes on each timeline, inbox emails, file attachments, custom objects, and the validation rules your Salesforce org already enforces.
What moves
What moves from HubSpot to Salesforce Sales Cloud
Companies become Accounts, contacts become Leads or Contacts, deals become Opportunities with their products and contact roles, and calls, meetings, emails, notes and files land as Tasks, Events, email messages, notes and Files.
- 15 included
| HubSpot | maps to | Salesforce Sales Cloud | Status |
|---|---|---|---|
| Companies | AccountsThe HubSpot Record ID goes into an External ID field on Account, so re-runs and the delta sync upsert instead of inserting. | Included | |
| Contacts with a company | ContactsThe primary company sets AccountId. Lifecycle stage moves as a field for reporting. | Included | |
| Contacts without a company or not yet qualified | LeadsWhich lifecycle stages become Leads is agreed on the scoping call, and each person loads once. | Included | |
| Additional company associations | AccountContactRelationEvery company other than the primary one becomes an AccountContactRelation, whose AccountId cannot change after insert. | Included | |
| Deals | OpportunitiesDeal stage sets StageName, and with it IsWon and IsClosed. The original HubSpot create date is set as CreatedDate at insert. | Included | |
| Deal pipelines | Sales processes and record typesOne sales process and record type per pipeline, with the stages created before deals load. | Included | |
| Deal-to-contact association labels | OpportunityContactRoleEach label becomes the Role on the contact role. | Included | |
| Line items | Opportunity productsHubSpot products become Product2 records with a PricebookEntry per price, created first, because each OpportunityLineItem needs a PricebookEntryId. | Included | |
| Calls and tasks | TasksCalls load with the Call subtype, set at insert, linked to the Contact or Lead and to the Account or Opportunity. | Included | |
| Meetings | EventsThe attendee's Contact or Lead is the Event's WhoId, and the related Account or Opportunity its WhatId. | Included | |
| Email activities | Email messagesLoaded with the Sent status, the one Salesforce accepts for emails on sales records, and Salesforce creates the matching Task itself. | Included | |
| Notes | Enhanced notes (ContentNote)Linked to every Account, Contact and Opportunity the HubSpot note was associated with. | Included | |
| Attachments | FilesUploaded as ContentVersion and linked to the parent record, up to 2 GB a file through the REST API. | Included | |
| Owners and teams | Users, roles and queuesOwners who have left become inactive Users, so their records keep a named owner. | Included | |
| Custom objects | Custom objectsObjects, fields and lookups are created in Salesforce before the load. | Included |
- CompaniesAccounts
The HubSpot Record ID goes into an External ID field on Account, so re-runs and the delta sync upsert instead of inserting.
- Contacts with a companyContacts
The primary company sets AccountId. Lifecycle stage moves as a field for reporting.
- Contacts without a company or not yet qualifiedLeads
Which lifecycle stages become Leads is agreed on the scoping call, and each person loads once.
- Additional company associationsAccountContactRelation
Every company other than the primary one becomes an AccountContactRelation, whose AccountId cannot change after insert.
- DealsOpportunities
Deal stage sets StageName, and with it IsWon and IsClosed. The original HubSpot create date is set as CreatedDate at insert.
- Deal pipelinesSales processes and record types
One sales process and record type per pipeline, with the stages created before deals load.
- Deal-to-contact association labelsOpportunityContactRole
Each label becomes the Role on the contact role.
- Line itemsOpportunity products
HubSpot products become Product2 records with a PricebookEntry per price, created first, because each OpportunityLineItem needs a PricebookEntryId.
- Calls and tasksTasks
Calls load with the Call subtype, set at insert, linked to the Contact or Lead and to the Account or Opportunity.
- MeetingsEvents
The attendee's Contact or Lead is the Event's WhoId, and the related Account or Opportunity its WhatId.
- Email activitiesEmail messages
Loaded with the Sent status, the one Salesforce accepts for emails on sales records, and Salesforce creates the matching Task itself.
- NotesEnhanced notes (ContentNote)
Linked to every Account, Contact and Opportunity the HubSpot note was associated with.
- AttachmentsFiles
Uploaded as ContentVersion and linked to the parent record, up to 2 GB a file through the REST API.
- Owners and teamsUsers, roles and queues
Owners who have left become inactive Users, so their records keep a named owner.
- Custom objectsCustom objects
Objects, fields and lookups are created in Salesforce before the load.
Looking for another object?Field-level mapping is reviewed with you during scoping.
What does not move
What does not move from HubSpot to Salesforce Sales Cloud as-is
Workflows, sequences, snippets, templates, playbooks and reports are HubSpot configuration with no logic in its exports, so they are rebuilt in Salesforce.
- HubSpot Leads objectOn request
- In Salesforce Sales Cloud: Salesforce LeadsOnly for people who are not also loaded as Contacts, so no one exists twice.
- On request
- Survey responses (NPS, CSAT, CES)On request
- In Salesforce Sales Cloud: A custom object linked to the ContactHubSpot's survey API reads responses, so they move as custom records with their score, comment and date.
- On request
- Marketing emails and listsOn request
- In Salesforce Sales Cloud: Campaigns and campaign membersOnly where Campaigns are licensed: the object exists only in orgs with the marketing feature, for marketing users.
- On request
- Property historyOn request
- In Salesforce Sales Cloud: A note on the recordSalesforce History objects are read-only, so field history starts on the load date and earlier values follow as a note.
- On request
- Workflows and sequencesNot migrated
- In Salesforce Sales Cloud: Salesforce FlowsHubSpot's workflow export is a list of names, status and counts with no logic, so each workflow is described by hand for rebuilding.
- Not migrated
- Association labels beyond contact rolesNot migrated
- In Salesforce Sales Cloud: AccountContactRelation or OpportunityContactRole rolesLabels with no Salesforce role are mapped by hand on the scoping call or left out.
- Not migrated
- Snippets, templates and playbooksNot migrated
- In Salesforce Sales Cloud: Email templates and Quick TextHanded over with their text, for your admin to recreate.
- Not migrated
- Reports, dashboards and saved viewsNot migrated
- In Salesforce Sales Cloud: Salesforce reports, dashboards and list viewsRebuilt on the migrated fields, with the HubSpot Record ID kept on every record for matching.
- Not migrated
Free sample migration of 100 of your records. Fixed quote within 24 hours.
Scope my migrationTimeline
HubSpot to Salesforce Sales Cloud migration timeline
Estimated total
About 10 business days
end to end
- MigrateXwe run it
- Youyour team acts
- Bothon a call together
Preparation
Day 1-2
Scoping call
Both0.5 dayWe agree which lifecycle stages become Leads, how each deal pipeline maps to a sales process, which association labels survive, and whether property history follows as notes.
HubSpot read access and a Salesforce sandbox
You0.5 dayYou create a HubSpot private app with read scopes and a Salesforce integration user with API Enabled and the two audit field permissions, starting in a sandbox.
Org build and rule review
Both1 dayExternal ID fields, custom fields, stages, record types and price book entries are created, and your admin marks the validation rules, duplicate rules and flows that pause.
Migration
Day 3-7
Free sample in the sandbox
MigrateX1 day100 of your records, picked for won and lost deals, long notes, calls, inbox emails and contacts with several companies, loaded into the sandbox end to end.
You review the sample
You1 dayYour reps open Accounts and Opportunities as a sales user and check owners, created dates, stages, contact roles and activity history.
Full load into production
MigrateX2-3 daysUsers and products first, then Accounts, Contacts and Leads, then Opportunities with line items and roles, then Tasks, Events, emails, notes and files, paced to your allocation.
Delta sync
MigrateX0.5 dayHubSpot records changed since the full load are upserted on the HubSpot Record ID External ID field, so no Account or Opportunity is created twice.
Validation
Day 8-10
Reconciliation report
MigrateX1 dayHubSpot counts against Salesforce counts per object and owner, won and lost totals per pipeline, and rejected rows with their reason.
Spot checks and sign-off
You1-2 daysYour sales leads check their own pipelines, the paused rules and flows go back on, and HubSpot stays as it was, with a rollback plan ready, until you sign off.
An estimate. Record volume, API rate limits and how fast your team reviews the sample all move it.
Known risks
Every known risk on this route, with how we handle it
- 3 solved
- 5 handled
- 01HandledMost critical
Each HubSpot contact must become a Salesforce Lead or a Contact
The problem
HubSpot keeps every person as a contact and marks progress with a lifecycle stage. Salesforce splits people into Leads, which are unqualified prospects that later convert, and Contacts, which belong to an Account.
How we handle it
On the scoping call we agree which lifecycle stages become Salesforce Leads and which become Contacts, usually by whether the contact has a company and an open deal. Each person loads once, as a Lead or as a Contact, never both, with the HubSpot Record ID in an External ID field.
Source: Salesforce developer documentation, checked 15 Nov 2026
- 02Solved
Won and lost deals close through their stage, not a flag
The problem
Salesforce Opportunity IsWon and IsClosed cannot be set on create, so the StageName decides whether a deal is open, won or lost. A HubSpot pipeline with custom closed stages has to map each stage onto a Salesforce stage of the right kind, and each extra pipeline needs a sales process.
How we handle it
Every HubSpot deal stage is mapped to a Salesforce stage with its won or lost meaning, and each pipeline gets its own sales process and record type. Your admin creates the stages before the sample, and the reconciliation report compares won and lost totals per pipeline.
Source: Salesforce developer documentation, checked 15 Nov 2026
- 03Handled
A live Salesforce org turns away rows that break its rules
The problem
Validation rules run on records created through the API, and a duplicate rule set to block refuses the insert outright. HubSpot data that was never held to those rules, such as companies without an industry or contacts sharing an email, fails on load.
How we handle it
Before the sample, your admin and our engineer go through each validation and duplicate rule on Lead, Contact, Account and Opportunity. Rules either pause for the load or the HubSpot data is cleaned to pass them, and every rejected row is listed with its reason.
Source: Salesforce Help, checked 14 Nov 2026
- 04Handled
Long HubSpot notes do not fit a classic Salesforce Note
The problem
A HubSpot note body can run to 65,536 characters, while the body of a Salesforce Note is limited to 32 KB. Call write-ups and pasted email threads stored as HubSpot notes can be cut off if they go into the classic Note object.
How we handle it
Notes load as enhanced notes (ContentNote), which are stored as Salesforce Files rather than in a classic Note body. Where your team uses classic Notes, how a HubSpot note over 32 KB is carried is scoped with you during the free sample.
Source: Salesforce developer documentation, checked 15 Nov 2026
- 05Solved
A Task's subtype is fixed the moment it is created
The problem
Salesforce TaskSubtype can be set on create but has no update property. A HubSpot call loaded as a plain Task stays a plain Task in Salesforce reports unless it is deleted and loaded again.
How we handle it
HubSpot calls load with the Call subtype and HubSpot tasks as plain Tasks, set on insert. The free sample includes calls, tasks and logged emails, so your team checks how each one shows in Salesforce activity history before the full load.
Source: Salesforce developer documentation, checked 15 Nov 2026
- 06Solved
Inbox emails come out of HubSpot without their quoted history
The problem
For emails in the HubSpot conversations inbox, the Conversations API cuts off the reply history section, and the full message needs a separate call to the original content endpoint. A plain read would load shortened emails into Salesforce.
How we handle it
For every inbox email in scope, MigrateX fetches the original content and loads the full body as an EmailMessage on the matching Contact, Account or Opportunity. Logged email activities from the CRM timeline move with their stored body.
Source: HubSpot developer documentation, checked 15 Nov 2026
- 07Handled
Both CRMs ration requests across every connected app
The problem
HubSpot's daily API limit is shared by all apps in the account and resets at midnight in the account's time zone. On the Salesforce side, calls from managed packages count against the org's allocation, and production orgs allow 25 long-running requests at once.
How we handle it
We list the integrations live on both sides during scoping and schedule the heaviest reads after HubSpot's daily reset. Salesforce Bulk API 2.0 jobs are sized to stay well under 25 concurrent long-running requests, so your other integrations keep running.
Source: Salesforce developer documentation, checked 15 Nov 2026
- 08Handled
The Salesforce edition decides how data can get in
The problem
Data Loader runs on Enterprise, Unlimited, Performance and Developer editions, and Salesforce's pricing table lists Web Services API as an extra-cost add-on on Pro Suite. A team moving from HubSpot onto a smaller Salesforce edition may have no API access at all.
How we handle it
Your Salesforce edition and API access are confirmed on the scoping call, before anything is planned. If the edition has no API, we tell you what the add-on would add and what the Data Import Wizard alone can carry.
Source: Salesforce website, checked 15 Nov 2026
Technical profile
What makes this route technical
HubSpot gives no activity history in its export files and rations reads through one daily limit shared by every app, while Salesforce fixes original dates, Task subtypes and deal outcomes at the moment each record is inserted.
- Leaving HubSpot: a record export carries no calls, notes or emails
- HubSpot's record export leaves activities out and sends users to individual contact exports, activity reports or the engagements API instead. A HubSpot to Salesforce migration built on export files would load companies and deals without the history your reps logged on them.
Source: HubSpot Knowledge Base, checked 15 Nov 2026
- Leaving HubSpot: the Exports API runs one job at a time
- The HubSpot Exports API completes at most thirty exports in a rolling 24 hours, one at a time, and returns associated records only as IDs, four associated objects per request. MigrateX reads HubSpot objects and their associations through the CRM object APIs instead.
Source: HubSpot developer documentation, checked 15 Nov 2026
- Leaving HubSpot: CRM Search stops at 10,000 results
- HubSpot's CRM Search API answers five requests a second per account, returns no more than 10,000 results for any query, and never returns archived records. A HubSpot account with more contacts than that is read through list endpoints, page by page.
Source: HubSpot developer documentation, checked 15 Nov 2026
- Loading Salesforce: original dates are accepted only at insert
- Salesforce lets an integration user set CreatedDate and the creator only while a record is being created, and only once Set Audit Fields upon Record Creation and Update Records with Inactive Owners are granted. A HubSpot record loaded without them shows the load date in Salesforce for good.
Source: Salesforce Help, checked 15 Nov 2026
- Loading Salesforce: the Data Import Wizard stops short of deals
- The Salesforce Data Import Wizard loads accounts, contacts, leads, campaign members and custom objects, up to 50,000 records at a time, but opportunities are not on its list. HubSpot deals, line items and activities go in through Bulk API 2.0.
Source: Salesforce Help, checked 15 Nov 2026
- Loading Salesforce: Bulk API 2.0 ingest allowance
- Salesforce accepts up to 150,000,000 records a rolling 24 hours and 15,000 batches shared between Bulk API and Bulk API 2.0. Salesforce advises keeping each upload to about 100 MB of CSV, because base64 encoding inflates a job towards its 150 MB ceiling.
Source: Salesforce developer documentation, checked 15 Nov 2026
- Loading Salesforce: 200,000 new file versions a day
- Salesforce publishes at most 200,000 ContentVersion records in a 24-hour period. HubSpot attachments referenced by hs_attachment_ids on emails and notes are counted during the read, so a large file history gets its own days in the plan.
Source: Salesforce developer documentation, checked 15 Nov 2026
- Loading Salesforce: a Partial Copy sandbox for the rehearsal
- Salesforce Enterprise Edition includes one Partial Copy sandbox, which holds 5 GB of sample data and refreshes every 5 days. A Full sandbox copies all data but refreshes only every 29 days. Either one can hold a rehearsal load before production.
Source: Salesforce Help, checked 15 Nov 2026
Facts checked 15 Nov 2026 against HubSpot and Salesforce documentation. Each fact links its source.
HubSpot to Salesforce Sales Cloud questions
Still unsure? Ask the engineer who would run this migration, not a sales rep.
How do I migrate from HubSpot to Salesforce?
Prepare the Salesforce org first, then load records in dependency order. MigrateX agrees the Lead and Contact rule and the pipeline mapping, rehearses on a free sample of 100 of your records in a sandbox, loads Accounts, people, Opportunities and activities into production, and finishes with a delta sync from HubSpot.
Why can't HubSpot's export files carry our calls, notes and emails into Salesforce?
Because HubSpot's record export leaves activities out, and its Exports API returns associated records only as IDs. MigrateX reads every HubSpot call, meeting, email and note through the API with the records it belongs to, and loads it onto the matching Salesforce record.
Will original create dates and owners carry over into Salesforce?
Yes, when the Salesforce integration user holds Set Audit Fields upon Record Creation and Update Records with Inactive Owners before the first record loads, because Salesforce takes CreatedDate and CreatedById only at insert. On Professional Edition both come through a permission set. Reps who have left your company become inactive Users, so their HubSpot records keep a named owner in Salesforce.
Do HubSpot deal pipelines become Salesforce sales processes and record types?
Yes, one of each per pipeline. Salesforce record types give each team its own sales process and picklist values, so every HubSpot pipeline gets a record type whose sales process lists its stages. Won and lost stages are mapped to Salesforce stages of the same kind, since StageName is what closes an Opportunity.
Which HubSpot contacts should become Salesforce Leads and which Contacts?
Usually, HubSpot contacts with a company and an open deal become Salesforce Contacts, and early-stage people without one become Leads. You choose the cut-off lifecycle stage on the scoping call, and nobody is loaded as both.
Do we need to switch off validation rules and duplicate rules during the load?
Some of them, chosen with your admin before the free sample. Each Salesforce validation and duplicate rule on Lead, Contact, Account and Opportunity is either paused for the load or met by cleaning the HubSpot data, and paused rules go back on after the delta sync.
Can we test the HubSpot migration in a Salesforce sandbox first?
Yes, and we recommend it: the free sample loads into a Salesforce sandbox, so your team sees real Accounts, Opportunities and activity history before production is touched. Developer sandboxes copy metadata only, so the rehearsal uses a Partial Copy or Full sandbox.
Can HubSpot property history move into Salesforce field history?
Not as native field history. Salesforce History objects are read-only, so history in Salesforce starts on the day each record loads. On request, the earlier values of the fields you name follow as a dated note on each record, with what HubSpot returns for them confirmed during your free sample.
How long does a HubSpot to Salesforce migration take?
About 10 business days end to end is our default plan. On this route the read is paced by HubSpot's daily request limit and the load by Bulk API 2.0 and the 200,000 file versions Salesforce accepts a day. Most of the first two days goes on building the Salesforce org, and the free sample shows the real pace.
What does a HubSpot to Salesforce migration cost?
The cost of a HubSpot to Salesforce migration is set by the contacts, companies and deals in scope, the calls, emails and notes on their timelines, attachments, custom objects, and how much of the Salesforce org has to be built first. MigrateX migrates 100 of your records free, then sends a fixed quote within 24 hours.
How it compares
Four ways to run HubSpot to Salesforce Sales Cloud
The same data, moved four different ways. This is what changes between them.
Object coverage (accounts, contacts, deals, activities, files)
MigrateX
Every object in the mapping on this page, plus the ones you ask for during scoping.
Automated migration software
Contacts and accounts are covered. Deals, activities and their links often are not.
Vendor CSV import
One object per file, and only the fields the export template exposes.
In-house scripts
Whatever you have time to build before the cutover date.
Activities and notes on each record
MigrateX
Each email, call, meeting and note is loaded on its own and linked to the records it belongs to.
Automated migration software
Activities usually arrive, but their links to contacts, deals and owners can be lost.
Vendor CSV import
Notes collapse into one field on the record, if they come across at all.
In-house scripts
Possible, but it is the part teams most often run out of time for.
Files and attachments
MigrateX
Uploaded and linked to the record they belong to. How files over the Salesforce Sales Cloud size limit are handled is confirmed during your free sample.
Automated migration software
Supported up to the destination's file size limit. Larger files are skipped.
Vendor CSV import
Not carried by a CSV import.
In-house scripts
Needs its own download, retry and upload pipeline.
Original IDs cross-referenced
MigrateX
Every source id is stored on the destination record and handed back as a map.
Automated migration software
Often kept as a tag or a single text field.
Vendor CSV import
Lost once the file is imported.
In-house scripts
Only if you design the mapping table up front.
Delta sync before cutover
MigrateX
Included. Anything created or changed during the bulk pass is synced at cutover.
Automated migration software
Usually a paid upgrade on the top tier.
Vendor CSV import
You would re-export and re-import by hand.
In-house scripts
Requires change tracking and idempotent writes on both sides.
Rate-limit handling
MigrateX
Paced to your plan limits, honours Retry-After, and resumes from a checkpoint.
Automated migration software
Backs off, but a long run can still stall and leave partial records.
Vendor CSV import
Not applicable, and the file size limits bite instead.
In-house scripts
The most common reason a home-grown run dies overnight.
Validation report
MigrateX
Counts per object and per status on both sides, with every default and placeholder listed.
Automated migration software
A run log and an error list, rather than a reconciliation.
Vendor CSV import
Row counts in a spreadsheet.
In-house scripts
You write the reconciliation queries yourself.
Rollback plan
MigrateX
Every write is tagged, so a batch can be reversed without touching your own records.
Automated migration software
Some approaches can clear a migration, some cannot.
Vendor CSV import
Manual cleanup of everything the import created.
In-house scripts
Only if you built the tagging in from the start.
Who does the work
MigrateX
A MigrateX engineer runs it and stays on the cutover call.
Automated migration software
You run the software. The vendor's support team answers questions.
Vendor CSV import
Your admins, one file at a time.
In-house scripts
Your engineers, instead of your roadmap.
Guides
Guides for a HubSpot to Salesforce Sales Cloud migration
Related routes
Other routes we run
Built for your security review, from the first call.
Read how we handle your data
SOC 2 Type II
Independently audited controls over how we handle your data.
GDPR compliant
Data processing agreement available.
HIPAA compliant
Business associate agreement available.

Start your Salesforce Sales Cloud move with 100 of your records.
Scope my migrationFree sample migration of 100 of your records, plus a fixed quote within 24 hours.
