Plenty of support teams live in two CRMs. Sales and service history sit in Salesforce, while marketing, the help desk or the website chat runs on HubSpot. Every time a customer's details change in one system and not the other, someone on your team ends up working from the wrong record.
There are two common ways to connect them. HubSpot's native Salesforce integration keeps records in step over time. Zapier runs a specific action in one system when something happens in the other. They solve different problems, cost different amounts and need different owners, so it pays to decide which job you're doing before you buy.
In this guide, we'll compare the two routes, explain what each one needs, walk through one field from mapping to testing, and show how to prove the connection works before you roll it out.
Key takeaways
Choose the connection for the job
Start with what you need the two systems to do together.
Your requirement | Recommended route | Why choose it | Cost and ownership |
|---|---|---|---|
Keep contacts, companies, deals and cases aligned over time | HubSpot's native Salesforce integration | Built-in sync, field mappings and sync rules cover most standard records without extra software | An eligible HubSpot subscription, Salesforce API access and capacity, and a CRM administrator who owns the mappings |
Run a specific action in one system when something happens in the other | Zapier's HubSpot and Salesforce apps | A defined trigger and action suits a single workflow, such as updating one Salesforce field when a HubSpot property changes | A paid Zapier plan, enough tasks for each lookup and update, both CRM subscriptions and a named workflow owner |
For routine contact synchronisation, start with the native integration. For a specific event-driven handoff, start with a Zapier workflow and confirm that the trigger and action you need both exist.
The two can also work side by side. Many teams sync core records natively and add a Zap for one narrow job the sync doesn't cover.
How the native integration works
HubSpot built and maintains the integration, and it's included with eligible subscriptions rather than sold separately.
Who can install it. It's available with Marketing Hub, Sales Hub, Service Hub, Data Hub, Content Hub and Smart CRM, at the Professional or Enterprise tier. Starter subscriptions can't use it. On the Salesforce side, HubSpot supports any edition with API access, plus Professional Edition, but not Group Edition. The person installing it must be a Salesforce system administrator with permissions including API Enabled, View Setup and Configuration, and Modify All on the objects you sync. HubSpot's installation guide lists the full set.
What syncs. HubSpot contacts sync with Salesforce leads and contacts, companies with accounts, deals with opportunities and tickets with cases. HubSpot activities such as form submissions, emails and meetings can be logged as Salesforce tasks. Syncing custom objects needs an Enterprise subscription.
How often. HubSpot checks both systems for new or updated information about every 15 minutes. Some events, such as a form submission or a change to a mapped property, also trigger a sync. An inclusion list limits which HubSpot contacts are allowed to sync, which is useful for keeping test records or unqualified contacts out of Salesforce.
How conflicts are settled. Each field mapping uses one of four sync rules:
Limits to plan for. You can connect only one Salesforce instance to each HubSpot account, so settle your org structure before you choose this route. A single contact sync can use up to four Salesforce API calls per record, and those calls come out of your daily Salesforce API allowance. Dropdown values have to match: when you add a picklist option in Salesforce, refresh the mapping and add the same option to the HubSpot property.
How the Zapier route works
A Zap is a trigger plus one or more steps. For HubSpot and Salesforce, a typical Zap watches for a HubSpot change, such as the New Contact Property Change trigger, looks up the matching Salesforce record with Find Record, then changes it with Update Record.
Three requirements are easy to miss:
Zapier counts a task each time an action step completes successfully, such as a lookup or an update. Triggers, filters, formatters and paths don't count. If you run out, pay-per-task billing can keep Zaps running at a higher rate, or Zaps stop until the next cycle.
Select the workflow before the connector
Write the workflow down before you compare tools. These two scenarios show where each route fits.
Scenario | What to configure | How to check it before you buy |
|---|---|---|
A service team needs the same contact details in HubSpot and Salesforce | Native contact mapping, a sync rule for each field and an inclusion list | Change an approved field on a test contact and confirm the value and owner that arrive in Salesforce |
An approved HubSpot change should create or update one specific Salesforce record | A supported HubSpot trigger, a Salesforce record lookup and a Salesforce action in Zapier | Run one eligible event and one duplicate event. Confirm the right record updates once and errors reach a named person |
For each shared field, agree on four things: how records are matched (usually email, with the Salesforce record ID kept once a match is made), which system is authoritative, which way updates flow and who owns the record. If you're choosing more than one connection for your support team, our guide to HubSpot integrations for support compares phone, email, CRM and website options.
Example: sync a contact's support language
Say your support team serves customers in English and French, and the language preference is captured in HubSpot. Agents working in Salesforce need it on every contact so cases reach someone who speaks the customer's language.
Create the two fields first, with the same allowed values (EN and FR) on both sides.
Information | HubSpot contact property | Salesforce Contact field | Direction and ownership |
|---|---|---|---|
Record match | Match the existing contact by email and keep its Salesforce record ID. Review unmatched or duplicate records before anything is written | ||
Support language | support_language, a new custom property | Support_Language__c, a new custom field | HubSpot is authoritative. Updates flow from HubSpot to Salesforce |
Case owner | Contact owner stays managed in HubSpot | OwnerId stays managed in Salesforce | Each system keeps its existing owner. The service lead agrees which team receives French cases |

Figure 1. One field, two routes. The native integration syncs the mapped property on its regular cycle. The Zap reacts to the property change, finds the Salesforce contact by email and updates one field.
With the native integration, map support_language to Support_Language__c. None of the four sync rules sends HubSpot values only, so choose Two-way and make the Salesforce field read-only for agents in its field-level security. Changes can then only come from HubSpot, and HubSpot's value always lands in Salesforce.
With Zapier, use the HubSpot New Contact Property Change trigger on support_language, add a filter so only EN or FR continue, use Salesforce Find Record to match Contact.Email, then Update Record with the returned contact ID and the new Support_Language__c value. Send unmatched contacts and failed writes to the integration owner. Each change uses two tasks, one for the lookup and one for the update.
Either way, the language preference updates while the Salesforce owner stays as it was.
Compare the purchase requirements
Licences are the visible part of the cost. The rest is usage and the people who keep the connection working.
Cost category | Native integration | Zapier workflow |
|---|---|---|
CRM licences | An eligible HubSpot Professional or Enterprise subscription, plus Salesforce access for the integration user | Both CRM subscriptions, plus the permissions the trigger and action need |
Automation and usage | No extra licence. Check the sync scope against your daily Salesforce API allowance | A paid plan that includes premium apps, with enough tasks for every lookup and update |
Initial configuration | Object scope, field mappings, sync rules and the inclusion list | Trigger, filter, lookup, action, duplicate handling and the failure route |
Ongoing administration | A CRM administrator owns mappings, new picklist values and sync errors | A workflow owner maintains field changes, task usage and failed runs |
For reference, these are list prices in November 2026, in US dollars:
To budget the Zapier route, count the actions each run uses. The language workflow above uses two tasks per change, so 300 changes a month uses 600 tasks and fits the entry Professional tier. Compare that total, plus the time to maintain the Zap, with the native route's subscriptions and administration.
Prove the connection before rollout
Connect a Salesforce sandbox first: the installer asks whether you're connecting to one. If you have an Enterprise subscription, HubSpot's standard sandbox lets you test without touching live contacts, and an inclusion list keeps the first sync to a small test group. Then run these four records and record what happens.
Test record | Required outcome | Owner |
|---|---|---|
New eligible contact | Creates or matches exactly one Salesforce record using the agreed matching rule | CRM administrator |
Approved language update | Updates only the mapped field, in the agreed direction, and keeps the existing owner | CRM administrator |
Conflicting values or a repeated event | Applies the agreed source-of-truth rule without creating a duplicate | Integration owner |
A record the integration user can't access | Blocks the change and sends the failure to the named support route | Salesforce administrator |
If any test fails, fix the mapping or the Zap and run all four again. For installation steps, follow HubSpot's Salesforce integration guide and Zapier's Salesforce help article.
Scope the customer-support layer
Connected records are the foundation. The next question is how your support team uses them. With the same record in both systems, an assistant can pull a customer's history and preferences into the conversation instead of making an agent search for them.
Agent Assist from Expertise helps employees find approved answers, draft a reply and review the next action through connected tools, with the employee confirming every change. To see how that would work with your records, bring one real customer request, the records your team can access and your approval rules to a connected support workflow discussion.
Frequently asked questions
Does HubSpot's Salesforce integration cost extra?
No. It's included with eligible HubSpot Professional and Enterprise subscriptions. You still need Salesforce API access, and the sync uses part of your daily Salesforce API allowance.
Does the HubSpot Salesforce integration work with HubSpot Starter?
No. The native integration needs a Professional or Enterprise subscription of Marketing Hub, Sales Hub, Service Hub, Data Hub, Content Hub or Smart CRM. On Starter, a Zapier workflow is the usual alternative.
How often does HubSpot sync with Salesforce?
HubSpot checks both systems about every 15 minutes, and some changes, such as a form submission or an update to a mapped property, trigger a sync sooner.
Can one HubSpot account connect to two Salesforce orgs?
No. Each HubSpot account connects to one Salesforce instance. Several HubSpot accounts can connect to the same Salesforce instance, though.
Is Zapier enough for a full HubSpot Salesforce sync?
Usually not. Zapier works best for specific trigger-and-action workflows. Keeping whole objects aligned in both directions is what the native integration is built for.

