
Salesforce Sales CloudHubSpot
Salesforce Sales Cloud to HubSpot migration
Migration specialists move your accounts, contacts, opportunities and open leads into HubSpot, 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 · 13 object types mapped
- 1000+migrations
- 15 yearsof collective experience
SOC 2 Type IIGDPR compliantHIPAA compliant
Salesforce Sales Cloud to HubSpot at a glance
A Salesforce Sales Cloud to HubSpot migration turns Accounts into companies, Opportunities into deals and open Leads into contacts with a lifecycle stage. What needs care is HubSpot's side: only deals keep an original Create date, imported activities cannot be corrected by a second import, and line items belong to one deal. Salesforce stays live until the final delta sync.
- Objects mapped
- 13
- 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
- Sales and revenue operations teams leaving Salesforce Sales Cloud for HubSpot, often at a Salesforce renewal, who need deals, contact roles and years of call and meeting history to arrive intact.
- What does not move
- Flows, Process Builder, Apex, validation and duplicate rules, formula and roll-up fields, sharing rules and reports. Each is documented so it can be rebuilt as HubSpot workflows, calculated properties and reports.
- What sets the scope
- Opportunities with line items, activities older than 365 days, contacts with no email, Salesforce Files, custom objects, and whether your HubSpot subscription imports association labels.
What moves
What moves from Salesforce Sales Cloud to HubSpot
Accounts become companies, Contacts become contacts, open Leads become contacts with a lifecycle stage, and Opportunities become deals with their line items, contact roles, calls, meetings, emails, notes and files.
- 13 included
| Salesforce Sales Cloud | maps to | HubSpot | Status |
|---|---|---|---|
| Accounts | CompaniesThe Salesforce Account ID is stored in a unique property and used as the match key; the website domain is kept as the company domain. | Included | |
| Contacts | ContactsAssociated to their main Account's company as the primary company. Original CreatedDate goes into a custom date property. | Included | |
| AccountContactRelation | Extra company associationsEach further Account becomes a second company association, labelled where your subscription imports labels. | Included | |
| Open Leads | Contacts with a lifecycle stageLead status sets the lifecycle stage. A HubSpot lead record is added on request. | Included | |
| Opportunities | DealsStageName becomes the deal stage in the matching pipeline, and the original CreatedDate becomes the deal Create date. | Included | |
| Products and opportunity line items | Products and line itemsProducts load first; each line item is created on its deal and linked to its product through hs_product_id. | Included | |
| OpportunityContactRole | Deal-to-contact associationsThe role name becomes an association label on Professional and Enterprise. | Included | |
| Tasks | Calls and tasksTasks logged as calls become calls and the rest become tasks, archived Tasks included. | Included | |
| Events | MeetingsAssociated to the attendee's contact and to the related company or deal, archived Events included. | Included | |
| Emails (EmailMessage) | Email activitiesBody into hs_email_text and hs_email_html, MessageDate into hs_timestamp, attachments into hs_attachment_ids. | Included | |
| Notes and enhanced notes | NotesA Salesforce Note body is at most 32 KB, well inside HubSpot's 65,536-character note body. | Included | |
| Files | Files on the recordFound through ContentDocumentLink, uploaded to HubSpot and attached to the matching company, contact or deal. | Included | |
| Users | Users and ownersHubSpot creates owners from users, so users are added first. Owners assigned by import receive no notification. | Included |
- AccountsCompanies
The Salesforce Account ID is stored in a unique property and used as the match key; the website domain is kept as the company domain.
- ContactsContacts
Associated to their main Account's company as the primary company. Original CreatedDate goes into a custom date property.
- AccountContactRelationExtra company associations
Each further Account becomes a second company association, labelled where your subscription imports labels.
- Open LeadsContacts with a lifecycle stage
Lead status sets the lifecycle stage. A HubSpot lead record is added on request.
- OpportunitiesDeals
StageName becomes the deal stage in the matching pipeline, and the original CreatedDate becomes the deal Create date.
- Products and opportunity line itemsProducts and line items
Products load first; each line item is created on its deal and linked to its product through hs_product_id.
- OpportunityContactRoleDeal-to-contact associations
The role name becomes an association label on Professional and Enterprise.
- TasksCalls and tasks
Tasks logged as calls become calls and the rest become tasks, archived Tasks included.
- EventsMeetings
Associated to the attendee's contact and to the related company or deal, archived Events included.
- Emails (EmailMessage)Email activities
Body into hs_email_text and hs_email_html, MessageDate into hs_timestamp, attachments into hs_attachment_ids.
- Notes and enhanced notesNotes
A Salesforce Note body is at most 32 KB, well inside HubSpot's 65,536-character note body.
- FilesFiles on the record
Found through ContentDocumentLink, uploaded to HubSpot and attached to the matching company, contact or deal.
- UsersUsers and owners
HubSpot creates owners from users, so users are added first. Owners assigned by import receive no notification.
Looking for another object?Field-level mapping is reviewed with you during scoping.
What does not move
What does not move from Salesforce Sales Cloud to HubSpot as-is
Flows, Apex, validation rules, formula fields, sharing rules and reports are Salesforce configuration, so they are rebuilt in HubSpot from the list we hand over.
- Converted LeadsOn request
- In HubSpot: Scoped during the free sampleRead-only in Salesforce once converted. They move on request, and the Accounts, Contacts and Opportunities they became carry their data either way.
- On request
- Campaigns and campaign membersOn request
- In HubSpot: Static lists or a contact propertyMembers are read per campaign. Salesforce asks to be contacted before CampaignMember audit dates are set, so membership dates travel as a property.
- On request
- Record types and sales processesOn request
- In HubSpot: Deal pipelinesOne pipeline per sales process is common. A seat-based HubSpot Professional account allows 100 custom pipelines across objects, Starter 15.
- On request
- Opportunity and account field historyOn request
- In HubSpot: A note on the recordSalesforce History objects can be read but not recreated, and HubSpot property history starts on the load date.
- On request
- Custom objectsOn request
- In HubSpot: HubSpot custom objectsHubSpot custom objects need an Enterprise tier. On lower tiers, where these records go is scoped with you during the free sample.
- On request
- Flows, Process Builder, workflow rules and Apex triggersNot migrated
- In HubSpot: HubSpot workflowsLogic is rebuilt, not copied. We hand over each automation with the object it runs on and what it changes.
- Not migrated
- Formula and roll-up summary fieldsNot migrated
- In HubSpot: Calculated propertiesRecreated as HubSpot calculated properties. Today's value can be copied into a plain property on request.
- Not migrated
- Validation and duplicate rulesNot migrated
- In HubSpot: Required properties and HubSpot deduplicationEach rule is listed with its condition, so your admin can decide what HubSpot should enforce.
- Not migrated
- Profiles, permission sets, roles and sharing rulesNot migrated
- In HubSpot: Teams and user permissionsSet up before cutover from our list of who sees which Salesforce records today.
- Not migrated
- Reports, dashboards and list viewsNot migrated
- In HubSpot: HubSpot reports, dashboards and viewsRebuilt on the migrated properties, with the Salesforce ID property available for matching old report rows.
- Not migrated
Free sample migration of 100 of your records. Fixed quote within 24 hours.
Scope my migrationTimeline
Salesforce Sales Cloud to HubSpot 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 settle where open Leads go, which record types become pipelines, how price books collapse into one product library, and whether field history follows as notes.
Read-only Salesforce, writable HubSpot
You0.5 dayYou create a read-only Salesforce integration user and a HubSpot private app with write scopes, and add your reps as HubSpot users so every record has an owner.
Properties, pipelines and labels
Both1 dayCustom properties for Salesforce IDs and original dates, deal pipelines and stages, association labels for contact roles, and the product library are created in HubSpot.
Migration
Day 3-7
Free sample
MigrateX1 day100 of your records, chosen for deals with line items, contacts without email, archived meetings and large files, loaded into HubSpot end to end.
You review the sample
You1 dayYour reps open companies and deals and check the timeline order, owners, deal Create dates, line item prices and contact roles before you approve the activity mapping.
Full load
MigrateX2-3 daysProducts, companies and contacts first, then deals with line items, then associations, calls, meetings, emails, notes and files, paced to your HubSpot daily limit.
Delta sync
MigrateX0.5 daySalesforce records changed since the full load are matched on their Salesforce ID property and updated in HubSpot, so no company or deal appears twice.
Validation
Day 8-10
Reconciliation report
MigrateX1 daySalesforce counts against HubSpot counts per object, owner and year, Opportunity amounts against deal amounts, and Salesforce Files against HubSpot attachments.
Sign-off
You1-2 daysYour sales leads spot-check their own pipelines, HubSpot workflows are switched on, and Salesforce stays read-only 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
- 4 handled
- 01HandledMost critical
Salesforce Leads have no single HubSpot home
The problem
In Salesforce a Lead is a separate prospect record that converts into an Account, a Contact and an Opportunity, and a converted Lead becomes read-only. HubSpot tracks the same journey on the contact itself through lifecycle stage.
How we handle it
Converted Leads move on request, scoped with you during the free sample, and the Accounts, Contacts and Opportunities they became carry their data either way. Open Leads become contacts with a lifecycle stage, or contacts plus a HubSpot lead record if your team works a leads pipeline. You choose on the scoping call.
Source: Salesforce developer documentation, checked 15 Nov 2026
- 02Solved
A wrong activity load cannot be patched in HubSpot
The problem
HubSpot cannot update emails, meetings, notes or tasks that already exist through any kind of import. If thousands of Salesforce Tasks land with the wrong type, owner or date, the only fix is to delete them and load them again.
How we handle it
Task subtypes, Event attendees, owners and dates are mapped on the free sample first, and your team signs that sample off before a single production activity is created. Each activity carries its Salesforce ID in a property, so a reload removes exactly the records it replaces.
Source: HubSpot Knowledge Base, checked 15 Nov 2026
- 03Solved
Salesforce contacts without an email address merge or duplicate
The problem
HubSpot recognises an existing contact by Email, Record ID or a unique custom property. In a multi-object import, rows that carry no identifier and hold identical data are treated as one record, so two Salesforce Contacts with no email and the same name can collapse into one HubSpot contact.
How we handle it
Every Salesforce Contact and Lead ID goes into a unique custom property, and that property, not the email, is the match key for the load. The free sample report lists contacts without email, so your team decides which ones to keep.
Source: HubSpot Knowledge Base, checked 15 Nov 2026
- 04Solved
Salesforce Files do not all show up in a plain query
The problem
Salesforce says a ContentDocument or ContentVersion query that names no ID does not return every file a user can open. A file export built that way leaves contracts and proposals behind on Accounts and Opportunities without any error.
How we handle it
Files are listed record by record through ContentDocumentLink, uploaded to HubSpot (up to 2 GB a file on paid plans) and attached to the matching company, contact or deal through hs_attachment_ids. The reconciliation report counts files per Salesforce record against attachments per HubSpot record.
Source: Salesforce developer documentation, checked 15 Nov 2026
- 05Handled
Price books need a decision before line items load
The problem
Each Salesforce OpportunityLineItem points at a PricebookEntry, so one product can carry a different price in each price book or currency. A HubSpot line item belongs to exactly one parent record and links to its product through hs_product_id.
How we handle it
Products load into the HubSpot product library before any deal, and each Opportunity's line items are created on its deal with the price and quantity they had in Salesforce. For multi-currency or multi-price-book catalogues we agree on the scoping call which price becomes the library price.
Source: HubSpot developer documentation, checked 15 Nov 2026
- 06Handled
Contact roles and second accounts need association labels
The problem
Salesforce OpportunityContactRole records name the role each person plays on a deal, and AccountContactRelation links one Contact to several Accounts. HubSpot allows only one primary company on a record and stores roles as association labels, and importing labels needs a Professional or Enterprise subscription.
How we handle it
On Professional or Enterprise, every contact role becomes a labelled deal-to-contact association and every extra account a labelled company association. On Starter, roles move into a property on the contact and extra accounts become unlabelled associations, agreed before the sample.
Source: HubSpot Knowledge Base, checked 15 Nov 2026
- 07Handled
The HubSpot-Salesforce sync can double every record
The problem
HubSpot warns that running Smart Transfer and its Salesforce integration at the same time creates duplicate records in both HubSpot and Salesforce. A sync left running while a one-time migration loads the same Accounts and Contacts carries the same risk.
How we handle it
Your admin pauses or disconnects the HubSpot-Salesforce integration before the full load. If both CRMs must run side by side for a while, the sync is reconnected after sign-off with matching on the migrated Salesforce IDs.
Source: HubSpot Knowledge Base, checked 15 Nov 2026
Technical profile
What makes this route technical
Salesforce paces the read through its daily API allocation and archives activities older than 365 days, while HubSpot accepts a Create date only on deals and will not correct an activity once it is imported.
- Reading Salesforce: installed packages spend the same calls
- An Enterprise Edition org with 15 Salesforce licences can make 115,000 API calls a day, and every installed managed package spends calls from that same total. MigrateX paces the Sales Cloud read so the packages your reps rely on keep working during the move.
Source: Salesforce developer documentation, checked 15 Nov 2026
- Reading Salesforce: query results last 7 days
- Salesforce Bulk API 2.0 runs up to 10,000 query jobs and returns up to 1 TB of results a day, and each job's results can be fetched for only 7 days. The Leads, Opportunities and activity tables are queried in the same week the HubSpot load runs.
Source: Salesforce developer documentation, checked 15 Nov 2026
- Reading Salesforce: the weekly backup is the wrong source
- Salesforce's Data Export Service never includes formula or roll-up summary fields, and its zip files are deleted 48 hours after the notification email, weekends aside. A Sales Cloud backup therefore misses calculated deal values and cannot be the input for a HubSpot load.
Source: Salesforce Help, checked 15 Nov 2026
- Reading Salesforce: meetings older than a year are archived
- Salesforce archives any Event that ended more than 365 days ago and any closed Task due more than 365 days ago, and archived activities never appear in Salesforce reports. An export built from a Sales Cloud report gives HubSpot only the last year of calls and meetings.
Source: Salesforce Help, checked 15 Nov 2026
- Loading HubSpot: daily import ceiling on paid accounts
- A paid HubSpot account takes import files of up to 512 MB, with no more than 1,048,576 rows in one file, and accepts 500 imports or 10,000,000 rows a day. Large Salesforce activity tables are split into several files to fit.
Source: HubSpot Knowledge Base, checked 15 Nov 2026
- Loading HubSpot: deals are the only object with an editable Create date
- HubSpot makes Create date read-only on every object except deals. Every Salesforce CreatedDate is kept in a custom date property, Opportunities also take it as the HubSpot deal Create date, and Create date on accounts, contacts and leads is confirmed during your free sample.
Source: HubSpot Knowledge Base, checked 15 Nov 2026
- Loading HubSpot: each Task and Event keeps its place on the timeline
- HubSpot activities created through the API take hs_timestamp, which decides where the activity sits on the record timeline, and hubspot_owner_id, which decides the user shown as its creator. Salesforce ActivityDate and OwnerId values map onto those two properties.
Source: HubSpot developer documentation, checked 15 Nov 2026
Facts checked 15 Nov 2026 against Salesforce and HubSpot documentation. Each fact links its source.
Salesforce Sales Cloud to HubSpot questions
Still unsure? Ask the engineer who would run this migration, not a sales rep.
How do I migrate from Salesforce to HubSpot?
Read Salesforce through its API, build HubSpot's properties and pipelines, then load parents before children. MigrateX starts with a scoping call and a free sample of 100 of your records, loads products, companies and contacts, then deals, associations and activities, and finishes with a delta sync, after which Salesforce goes read-only.
How do Salesforce objects map to HubSpot objects?
Accounts map to companies, Contacts to contacts, Opportunities to deals, OpportunityLineItems to line items and Product2 to products. Tasks become calls or tasks, Events become meetings, EmailMessage records become email activities, and contact roles become labelled associations. Open Leads become contacts with a lifecycle stage, plus a HubSpot lead record where your team works a leads pipeline.
Do Salesforce created dates carry over to HubSpot?
Yes, in a custom date property on every record, and in Create date itself on deals, the one object whose Create date HubSpot lets you edit. Create date on accounts, contacts and leads is confirmed during your free sample, and every Salesforce Task, Event and email keeps its original time on the HubSpot timeline.
What happens to Salesforce opportunity products and price books?
They move as HubSpot products and line items: the catalogue first, then each Opportunity's line items on its deal at their Salesforce price. A Salesforce catalogue with several price books or currencies needs one decision before the load, which price the HubSpot product library holds.
Can Salesforce calls and meetings from earlier years come across?
Yes. MigrateX queries archived Salesforce Tasks and Events directly, because a Sales Cloud report export stops at the last 365 days, and places each one on the HubSpot timeline at its original time.
Should the HubSpot Salesforce integration stay on during the migration?
No. Your admin pauses or disconnects the HubSpot-Salesforce integration before the full load, because HubSpot warns that its Salesforce integration and a one-time transfer running together create duplicates in both systems.
Will Salesforce contacts without an email address duplicate in HubSpot?
Not when the load matches on a Salesforce ID property instead of email, which is how MigrateX loads every Salesforce Contact and Lead into HubSpot. The free sample report lists each contact with no email address, so your team decides which ones to keep.
Can Salesforce custom objects move to HubSpot, and on which plan?
Yes, as HubSpot custom objects, on an Enterprise tier of Smart CRM, Sales Hub, Service Hub, Data Hub, Content Hub or Revenue Hub. Each object is created with its properties and associations before the load. On Professional or Starter, where those records go is scoped with you during the free sample.
How long does a Salesforce to HubSpot migration take?
Plan for about 10 business days end to end. On this route the read is paced by your Salesforce org's daily API allocation and the load by your HubSpot account's daily request limit, which every connected app shares. Deals with many line items and years of archived activities take the longest, and the free sample shows the real pace.
What does a Salesforce to HubSpot migration cost?
The price follows what moves out of Salesforce: Accounts, Contacts, Leads and Opportunities, their line items and contact roles, archived activities, Files and custom objects, plus the HubSpot pipelines and properties they need. You get a fixed quote within 24 hours, after a free sample migration of 100 of your records.
How it compares
Four ways to run Salesforce Sales Cloud to HubSpot
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 HubSpot 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 Salesforce Sales Cloud to HubSpot 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 HubSpot move with 100 of your records.
Scope my migrationFree sample migration of 100 of your records, plus a fixed quote within 24 hours.



