Short answer: HubSpot Salesforce integration best practices come down to nine settings: a dedicated connected user with the right permissions, a sandbox test, an inclusion segment, selective sync, the lead-or-contact choice, field sync rules, owner mapping, the lifecycle stage setting and the API call allocation. Set each one on purpose before go-live, because defaults decide what overwrites what.
For marketing ops, RevOps and Salesforce admins connecting HubSpot to Salesforce, or inheriting a sync somebody else set up. Last reviewed November 2026 against HubSpot’s knowledge base.
1. Why the settings matter more than the connection
The integration is built for ongoing, two-way syncing, so every setup choice keeps running quietly in the background: which records cross over, which system wins a disagreement, and who owns what.
The integration needs a Professional or Enterprise HubSpot subscription (Marketing, Sales, Service, Data, Content or Smart CRM), and a Salesforce edition with API access or Salesforce Professional. Group Edition is not supported. You can connect only one Salesforce instance per HubSpot account.
Our sync audit covers a sync that is already drifting; this piece is about the settings to get right before you trust it.
| # | Setting | What it controls | What goes wrong if skipped |
|---|---|---|---|
| 1 | Connected user | What HubSpot can see and do in Salesforce | Objects silently fail to sync; changing users later is painful |
| 2 | Sandbox test | Whether you rehearse before production | First sync overwrites live data you cannot get back |
| 3 | Inclusion segment | Which HubSpot records may sync to Salesforce | Every HubSpot contact lands in Salesforce |
| 4 | Selective sync | Which Salesforce records sync to HubSpot | HubSpot fills with records marketing never needed |
| 5 | Lead or contact creation | What a new HubSpot contact becomes in Salesforce | Duplicates when companies are auto-created |
| 6 | Field sync rules | Which system wins for each field | Good data overwritten, or deletions spreading |
| 7 | Owner mapping | Record owner in both systems | Owners reverting, unassigned records |
| 8 | Lifecycle stage setting | Whether opportunity stages update lifecycle stage | Funnel reports that never match Salesforce |
| 9 | API call allocation | How much of the Salesforce API budget HubSpot may use | Sync competes with other tools for calls |
2. Use a dedicated connected user
HubSpot calls the Salesforce user you connect with the connected user, and its permissions decide what HubSpot can do through the sync. If that user cannot view leads, leads will not sync to HubSpot. Nothing warns you loudly; the records simply never arrive.
HubSpot’s install guide asks for a Salesforce system administrator with, among others, API Enabled, View Setup and Configuration, and Modify All on the objects you want to sync. If you later switch to a different user, the new one needs permissions equal to or greater than the old one and must sit in the same production organization.
That is why we connect with a dedicated integration user, not a person’s login. When the admin who set it up leaves, a personal login gets deactivated and the sync goes with it.
3. Rehearse in a sandbox first
The install flow has a checkbox to say you are connecting to a Salesforce sandbox. Use it. Two facts from HubSpot’s documentation make the rehearsal worth the time:
- On a first sync with no prior history, the Salesforce value can overwrite a more recent HubSpot value, depending on the sync rule.
- The updated deal sync cannot be switched back to the standard deal sync once it is on, and HubSpot itself recommends testing it in a sandbox.
Before installing in production, turn off any Smart Transfer sync connections, or the two will create duplicates. And if Salesforce enforces IP restrictions on every request, the integration cannot connect; HubSpot suggests a network IP range instead.
4. Set an inclusion segment before the first sync
The inclusion segment defines which HubSpot records are eligible to sync to Salesforce. It applies to contacts, companies, deals, tickets and custom objects. With no segment selected, all HubSpot contacts sync, which is rarely what sales wants: newsletter subscribers and old event lists turning up as Salesforce leads.
Points from the KB that catch teams out:
- Only active segments can be used, because they update as records change.
- Choosing a segment does not push its members across. They sync when a sync is triggered, so you may need to resync manually.
- When Salesforce leads or contacts create HubSpot contacts automatically, the match happens even if the contact is outside the segment. Later updates then stop syncing until the record meets the criteria.
Write the segment criteria down in plain language (“contacts sales should be able to work”), and get sales to agree before you build it.
5. Use selective sync for the other direction
The inclusion segment governs HubSpot to Salesforce. Selective sync filters what comes from Salesforce to HubSpot. If you set more than one filter, they are combined with AND logic, so test the filter on a sample before trusting the count.
Treat the two filters as a pair: most “why is this record here?” questions come from setting one direction and forgetting the other.
6. Decide whether new contacts become leads or contacts
In the contact sync rules you choose whether a HubSpot contact creates or updates a Salesforce lead or a Salesforce contact, and whether Salesforce leads and contacts create or update HubSpot contacts.
The choice interacts with company sync. Salesforce leads have no account, so creating leads while HubSpot auto-creates companies can produce duplicates; HubSpot’s own guidance is to sync contacts instead when that auto-create setting is on. If your sales team works a lead queue, settle the lead conversion process in Salesforce first and the HubSpot setting second.
7. Choose a sync rule for every mapped field
Each field mapping has one of four sync rules:
| Sync rule | Who wins | What deletions do |
|---|---|---|
| Prefer Salesforce unless blank | Salesforce; HubSpot fills a field only when Salesforce has no value | A deletion in Salesforce deletes the HubSpot value |
| Always use Salesforce | Salesforce, always; HubSpot never sends data | A deletion in Salesforce carries over to HubSpot |
| Two-way | The most recent value | A deletion in either system carries over |
| Don’t sync | Neither | No effect |
Good habits:
- Pick the rule per field, not per habit. Fields sales maintains (phone, title, account details) usually belong to Salesforce. Fields marketing collects (source, consent, form answers) usually belong to HubSpot. Two-way is for fields both teams genuinely edit.
- Never map one HubSpot property to several Salesforce fields. HubSpot warns that this can overwrite values or create sync loops.
- Resync after adding a mapping. Existing values in a new mapping do not sync retroactively.
- Watch reference fields and picklists. Salesforce reference fields sync as 18-digit record IDs, not labels, and new picklist options need a refresh and a matching HubSpot dropdown option.
Standard mappings cannot be deleted; set them to Don’t sync if you do not want them. There is a limit of 500 field mappings per object, which is a hint to map what you report on, not everything.
8. Get owner mapping right
The owner mapping is the one mapping that can only be two-way, and owner values have to match exactly between the systems. For contacts, Salesforce Owner ID syncs to the HubSpot owner property by default, and that cannot be turned off.
So every Salesforce owner who can hold synced records needs a matching HubSpot user, and routing has to be designed with the sync in mind, because an owner set in one system is written to the other. We walked through the routing side in HubSpot lead routing: assignment rules that don’t drop leads.
9. Decide what opportunity stages do to lifecycle stage
The integration can update a contact’s lifecycle stage in HubSpot when its Salesforce opportunity stage changes, or do nothing. Two details matter:
- The setting never moves lifecycle stage backward, and HubSpot stage changes do not alter Salesforce records.
- For a lead to reach Opportunity, it must first sync as a contact and be linked to the opportunity through contact roles.
If reps skip contact roles, the setting does nothing for those deals, and funnel reports stop matching Salesforce. If you sync deals as well, map each Salesforce opportunity record type to a HubSpot pipeline; only deals in mapped pipelines are eligible to sync. Why backward moves need their own design is covered in lifecycle stage vs lead status.
10. Allocate API calls on purpose
In Sync Health you set how many Salesforce API calls are allocated to HubSpot, alongside the limit Salesforce sets and the calls used in the last 24 hours. HubSpot notes that a contact sync can use up to four API calls per record, and recommends setting the allocation from your Salesforce limit and the usage of other tools in the org.
Ask the Salesforce admin what else draws on the API budget before you pick a number, then check Sync Health weekly for the first month; its error cards show each error type and the records affected.
11. A fifteen-minute pre-flight you can run today
- Open the integration settings and note the connected user. Is it a dedicated integration user or a person?
- Check whether an inclusion segment is selected. If not, every HubSpot contact is eligible to sync.
- Export the field mappings and count how many are Two-way. Ask who actually edits each one.
- Pick five recent Salesforce opportunities and check for contact roles. If none have them, the lifecycle setting is not doing what you think.
- Open Sync Health and compare API calls used against the allocation.
Questions we get asked
Can we connect two Salesforce orgs to one HubSpot account? No. HubSpot allows one Salesforce instance per HubSpot account. Several HubSpot accounts can connect to one Salesforce instance, each with its own install.
Does deleting a deal in HubSpot delete the Salesforce opportunity? No. With the deal sync, deleting a deal in HubSpot does not delete the opportunity, and that setting cannot be edited. Merging deals in HubSpot does not merge them in Salesforce either.
Will existing records sync as soon as we connect? Not all of them. Records sync when a sync is triggered, and HubSpot’s setup guidance points you to an import for existing Salesforce records.
Related reading: the HubSpot–Salesforce sync audit, HubSpot lead routing, lifecycle stage vs lead status and our HubSpot Salesforce sync repair service.
If your sync is live and you are not sure what it is overwriting, talk to us.
Source: HubSpot Knowledge Base, “Connect HubSpot and Salesforce”, “Manage your Salesforce integration settings”, “Map HubSpot properties to Salesforce fields”, “Create a Salesforce inclusion segment”, “Sync deals between HubSpot and Salesforce” and “Adjust your Salesforce API call limit” (checked 3 November 2026).