Salesforce Sales Cloud to HubSpot
Salesforce's core CRM for leads, accounts, contacts, opportunities and activities, with custom objects and automation.
Salesforce Sales Cloud data can move into HubSpot, landing mainly in Sales Hub. 3 of 8 mapped objects move directly (Accounts, Leads and Contacts and Opportunities); 5 items need manual work and 3 do not move. Plan roughly 2-4 weeks for a small move and 12-26 weeks for a large one.
Migration checklist for Salesforce Sales Cloud
Three phases, specific to this system. Tick steps off as you go.
Before
0 of 5 doneDuring
0 of 5 doneAfter
0 of 5 doneWhat will it take?
No price list: cost follows volume, custom objects and how much logic must be rebuilt. Answer four quick questions for a planning range.
The three scenarios
Small migration
Under 50k records, standard objects
Native import or CSV, with a few workflows.
Mid migration
50k-500k records, some custom objects and activities
Includes automation and reporting rebuild.
Large migration
500k+ records, many custom objects, heavy automation, multiple record types
Usually partner-led, with phased cutover.
What moves the number
Timeline ranges are planning estimates, not a quote. A partner confirms scope after discovery.
Access, mapping and limits
Start with how data leaves Salesforce Sales Cloud: what you need to get in, what lands in HubSpot, and what will not.
REST-based Bulk API 2.0 for high-volume query and ingest, plus REST and SOAP APIs
A Salesforce user login or connected app for OAuth. HubSpot's Salesforce integration needs a connected Salesforce account.
The API Enabled permission on the user's profile. Bulk API 2.0 is on by default in Performance, Unlimited, Enterprise and Developer editions.
Bulk API and Bulk API 2.0 share an allocation of 15,000 batches per rolling 24 hours, and only ingest jobs consume batches. Each org also has a 24-hour API request cap.
Choose your route
How will you move the data?
HubSpot offers an integration for importing records from Salesforce Sales Cloud.
- You need: A Salesforce user login or connected app for OAuth. HubSpot's Salesforce integration needs a connected Salesforce account.
- Permission: The API Enabled permission on the user's profile. Bulk API 2.0 is on by default in Performance, Unlimited, Enterprise and Developer editions.
Native imports often bring over only some data, so check coverage per object in the mapping below.
Export each object, clean it, then import it into HubSpot.
- Bulk API 2.0 SOQL query jobs, also via the Salesforce CLI 'sf data export bulk'
- Data Loader, which routes exports through the Bulk APIs
- Data Export Service for org-wide backups
- Report export, capped at about 2,000 rows
- Report-based export of activity data, which HubSpot can read as a spreadsheet
Limits: Bulk API and Bulk API 2.0 share an allocation of 15,000 batches per rolling 24 hours, and only ingest jobs consume batches. Each org also has a 24-hour API request cap.
Migration and sync tools can move more than a plain import. Confirm which objects each one supports before you choose.
Best when volume is high, custom objects are many or automation is heavy. That is the Large scenario: 12-26 weeks, usually phased.
Talk to a partnerWhere each object lands
In Salesforce Sales Cloud
In HubSpot
Hover or tap anything on the left to see where it lands.
| Source object | In HubSpot | Moves | Notes |
|---|---|---|---|
| Accounts | Companies | yes | Import first so associations can be created. |
| Leads and Contacts | Contacts | yes | HubSpot has no Lead object, so use lifecycle stage and lead status. Plan deduplication. |
| Opportunities | Deals | yes | Rebuild pipelines and stages first. Record types often become separate pipelines. |
| Tasks and Events (activities) | Tasks | partial | Tasks, calls, meetings, notes and emails can be imported from files. Historical imports are limited, and Salesforce activity sits in several objects. |
| Users (owners) | Contacts | partial | Owners map only if the matching users already exist in HubSpot. |
| Cases | Tickets | partial | Needs Service Hub. Ticket pipelines and statuses must be recreated. |
| Custom objects | Custom objects | partial | Create the objects and associations before import. Needs a suitable HubSpot tier. |
| Campaigns | Custom objects | manual | No direct equivalent. Often remodeled as lists, properties or HubSpot campaigns. |
What to expect
Automation does not migrate and must be recreated as workflows.
Salesforce field history does not import as HubSpot property history.
Logic does not carry over. Recreate it as a calculation property or export the values.
Access models differ and no tool in the sources moves them.
Salesforce reports export as data only, not as report definitions.
Many-to-many relationships need deliberate modeling.
Fields must be created and typed before mapping.
Activity history sits in several Salesforce objects and associations need explicit ID columns.
Import companies, then contacts, then deals, then activities, or use multi-object import files.
Export Tasks, Events and email records explicitly and test them in a sandbox.
Use Bulk API 2.0 or Data Loader CSV exports for full field coverage.
Deduplicate in Salesforce first and use unique identifiers for matching.
Audit what has been used in the last 6 months and decide whether to rebuild, drop or archive each item.
Data governance and compliance
Decide what is allowed to move before anything is exported. Tick each gate once it is agreed.
How we researched this page
How much to trust each section, and where it comes from.
Export paths (Bulk API 2.0, CLI) are backed by Salesforce docs. HubSpot's Salesforce import and file import are backed by HubSpot docs. Some object-mapping detail comes from partner guides.
Sources
Related migrations
Frequently asked questions
How do I migrate Salesforce Sales Cloud to HubSpot?
1. Inventory custom objects, fields, validation rules, record types and flows in Salesforce. 2. Confirm the API Enabled permission and an OAuth-capable integration user. 3. Create HubSpot properties, pipelines and users to match, so owners resolve. 4. Add a Salesforce 18-character ID property in HubSpot for each object as the match key.
What data can move from Salesforce Sales Cloud to HubSpot?
These objects move directly: Accounts, Leads and Contacts and Opportunities. Check the mapping table for partial and manual items.
What does not move from Salesforce Sales Cloud to HubSpot?
Flows and Process Builder automation, Field history and Formula field logic. Plan to rebuild or retire these.
How long does a Salesforce Sales Cloud to HubSpot migration take?
Small (Under 50k records, standard objects): 2-4 weeks. Mid (50k-500k records, some custom objects and activities): 6-12 weeks. Large (500k+ records, many custom objects, heavy automation, multiple record types): 12-26 weeks. These are planning estimates, not a quote.
What access do I need to export from Salesforce Sales Cloud?
A Salesforce user login or connected app for OAuth. HubSpot's Salesforce integration needs a connected Salesforce account. The API Enabled permission on the user's profile. Bulk API 2.0 is on by default in Performance, Unlimited, Enterprise and Developer editions.
Is there a native HubSpot connector for Salesforce Sales Cloud?
Yes. Confirm the supported objects in discovery.
What compliance issues apply when moving Salesforce Sales Cloud data?
Check: Possible health, financial or minors' data in custom fields or notes, depending on the org and Free-text notes and emails may contain sensitive data. Agree consent, retention and access rules before exporting.
Moving Salesforce Sales Cloud into HubSpot?
A network of 153+ tiered HubSpot partners and 1,800+ accounts of experience. Tell us what you are moving and which hub matters most.
Talk to a partner