HubSpot ↔ Salesforce: Bi-Directional CRM Sync
Last updated: November 11, 2026
HubSpot's own Salesforce connector syncs records in both directions, and you choose per field which system wins a conflict. The catch is the plan: it needs HubSpot Professional or Enterprise, and Salesforce Group Edition can't connect at all.
The native connector syncs both ways
Checked November 11, 2026, against HubSpot's knowledge base.
| HubSpot | Salesforce | Direction | Plan needed |
|---|---|---|---|
| Contacts | Leads and contacts | ↔ Two-way | HubSpot Professional |
| Companies | Accounts | ↔ Two-way | HubSpot Professional |
| Deals | Opportunities | ↔ Two-way | HubSpot Professional |
| Tasks and activities | Tasks and activities | ↔ Two-way (timeline events go HubSpot → Salesforce only) | HubSpot Professional |
| Campaigns | Campaigns | Synced | HubSpot Professional |
| Custom objects | Custom objects | Synced | HubSpot Enterprise |
Sources: Install the HubSpot-Salesforce integration, custom object sync, sync triggers. "Professional" means Professional or Enterprise of any HubSpot hub (Marketing, Sales, Service, Content, Data, or Smart CRM).
Check both plans before you install
- HubSpot Free and Starter can't install the connector. Any one hub at Professional or Enterprise is enough.
- Salesforce needs an edition with API access, or Professional Edition. Group Edition is not supported.
- The connector uses the Salesforce org's daily API allowance. Syncing one contact can take up to 4 API calls, so a large first sync on a small org can hit the limit.
- HubSpot checks both systems for changes about every 15 minutes. Some events, such as a sales email logged on a contact, also trigger a sync.
Field rules decide which system wins
Each mapped property gets one of four rules. Pick them before the first sync, because a wrong rule overwrites good data in the other system.
| Rule | Use it for |
|---|---|
| Two-way | Fields both teams edit, such as phone or job title |
| Prefer Salesforce | Fields sales owns but HubSpot may fill first |
| Always use Salesforce | Record owner, account status, opportunity amount |
| Always use HubSpot | Lead source, lifecycle stage, form and email engagement |
Records match by email address, so a contact that exists in both systems with the same email updates in place. Use an inclusion list to control which HubSpot contacts are created in Salesforce; without one, marketing's whole database can flow into sales.
Use Make or n8n below Professional
If you're on HubSpot Starter or Salesforce Group Edition, the connector isn't available, and an automation platform is the way to sync. Build two scenarios, one per direction, and search by email before every create.
HubSpot → Salesforce
- Trigger: HubSpot contact created or updated
- Search Salesforce for the contact by email
- Update the match, or create a new contact
Salesforce → HubSpot
- Trigger: Salesforce contact created or updated
- Search HubSpot for the contact by email
- Update the match, or create a new contact
Each run uses Make credits or n8n executions, and two-way scenarios can loop: an update in HubSpot triggers the Salesforce scenario, which writes back and triggers HubSpot again. Store a "last synced by" field and skip records the other scenario just wrote. Make ↗ has a free plan with 1,000 credits a month. n8n ↗ is free to self-host if your data has to stay on your servers.
Three causes of missing or duplicate records
Duplicate contacts
The same person has different emails in each system, so the match fails. Merge the records in Salesforce and keep one email as the primary.
A HubSpot contact never reaches Salesforce
The contact isn't in the inclusion list, or the sync trigger for that activity type is off. Check the list membership first.
Sync stops partway through the day
The Salesforce org ran out of daily API calls. Lower the HubSpot API call limit in the connector settings, or narrow the inclusion list.