On this page (15)
Many companies run HubSpot for marketing and Salesforce for sales, connected by HubSpot's Salesforce integration. It works well when each system has a clear job and every synced field has one owner. Three settings decide most outcomes: the inclusion segment, which controls which HubSpot records sync to Salesforce at all; the sync rule on each field mapping, which decides which system wins; and the Salesforce API calls the sync consumes. Get those right before go-live and the two systems behave like one; leave them at defaults and duplicates and overwritten fields follow.
When does running both make sense?
- Marketing is productive in HubSpot and the cost and disruption of moving it are not justified yet.
- Sales, service or finance need Salesforce's data model, security or integrations.
- You can name an owner for the integration who will maintain mappings as both systems change.
If marketing and sales both want one system, or the integration keeps breaking, compare consolidating on Salesforce with Account Engagement or Marketing Cloud, or on HubSpot, instead of maintaining two.
What controls what syncs?
- Inclusion segment: HubSpot syncs records to Salesforce only if they are in the segment you select. Use it to send sales-ready contacts, not every newsletter subscriber.
- Object syncs: contacts and leads are the default; companies, deals, cases to tickets and custom objects each have their own settings in HubSpot.
- Field mappings: each HubSpot property maps to one Salesforce field, with matching field types.
- Sync rules: per mapping, choose Prefer Salesforce unless blank, Always use Salesforce, Two-way (the most recent value wins) or Don't sync.
| Data | Owner | Typical rule |
|---|---|---|
| Name, email, company, phone | Shared | Two-way, with duplicate rules in both systems |
| Lead source, original campaign, marketing engagement | HubSpot | Two-way, with the Salesforce field read-only so HubSpot's value is the one that changes |
| Lead status, owner, opportunity stage | Salesforce | Always use Salesforce |
| Lifecycle stage | Agreed definition | Set by rules in one system, mirrored in the other |
| Account fields such as industry and size | Usually Salesforce | Prefer Salesforce unless blank |
How much Salesforce API capacity does it use?
The integration reads and writes through the Salesforce API, so it counts against your org's daily API allocation alongside every other integration. HubSpot advises having at least three times the number of records in a segment available in API calls before a batch sync. Check your allocation in Salesforce before turning on a large segment, and set HubSpot's API usage limit so marketing syncs cannot starve other integrations.
What goes wrong most often?
- Syncing every HubSpot contact, which floods Salesforce with records sales will never work.
- Two-way sync on fields both teams edit, so values flip back and forth.
- Leads and contacts duplicated because matching rules differ between systems.
- Required Salesforce fields or validation rules blocking records HubSpot tries to create, with errors nobody reads.
- Owner assignment split between HubSpot workflows and Salesforce assignment rules.
A short setup checklist
- Document lead definitions, lifecycle stages and who owns each field.
- Create a dedicated Salesforce integration user with only the access the sync needs.
- Build the inclusion segment and test with a small set of records first.
- Set sync rules per mapping, not just defaults.
- Check API allocation and set HubSpot's usage limit.
- Review HubSpot's sync error list weekly for the first month, then monthly.
How do you set up the integration, step by step?
- Agree definitions first: marketing-qualified lead, sales-accepted lead, lifecycle stages and the handoff between teams.
- List every field that will sync, its owner and the sync rule it needs.
- Create a dedicated Salesforce integration user with only the access the sync requires.
- Build the inclusion segment so only sales-ready records sync, and test with a small set first.
- Align duplicate and matching rules in both systems before the first large sync.
- Check Salesforce API allocation and set the HubSpot usage limit.
- Turn on the sync in stages and review errors daily for the first week.
How do you report across both systems?
Decide where each report lives. Marketing performance, such as campaign engagement and conversion to marketing-qualified lead, usually lives in HubSpot. Pipeline, bookings and forecast live in Salesforce. For funnel reporting across both, sync the few fields that connect them, such as original source and lifecycle stage dates, and report from one system so leadership sees one number.
| Report | Usually built in | Fields it needs from the other system |
|---|---|---|
| Campaign and email performance | HubSpot | Opportunity created and won flags |
| Lead to opportunity conversion | Salesforce | Original source and campaign from HubSpot |
| Pipeline and forecast | Salesforce | None, beyond source attribution |
| Marketing-sourced revenue | Either, agreed once | Source, campaign and closed-won amount |
Frequently asked questions
Should HubSpot or Salesforce own the contact record?
Decide field by field rather than record by record. Marketing data such as campaign membership and email engagement usually belongs to HubSpot; sales data such as ownership, deal stage and account hierarchy belongs to Salesforce. Write the rules down and set the sync to match them.
When is it time to consolidate onto one platform?
When the integration needs more upkeep than either system, when teams argue about which numbers are right, or when reporting across marketing and sales requires exports. At that point a planned migration usually costs less than keeping both in step.
How do we clean up after a bad first sync?
Pause the sync, identify the records created or overwritten, restore values from backups or field history where possible, fix the mappings and inclusion segment, then re-enable with a small test set.
How often should we review the integration?
Weekly for the first month, then monthly: sync errors, API usage, duplicate rates and any new fields either team has added.
Glossary
- Inclusion segment: the HubSpot list that controls which records sync to Salesforce.
- Sync rule: the setting on each field mapping that decides which system’s value wins.
- Lifecycle stage: the stage a contact has reached, from subscriber to customer, defined once and mirrored in both systems.
- Integration user: the Salesforce user the sync runs as, with only the permissions it needs.
- API allocation: the number of Salesforce API calls your org can make each day, shared by every integration.
A 30-day stabilization plan
| Week | Focus | Check |
|---|---|---|
| Week 1 | Review sync errors daily and fix mappings | Errors trending down; no duplicate surges |
| Week 2 | Confirm lead handoff and owner assignment end to end | Every sales-ready lead reaches the right owner once |
| Week 3 | Validate reports in both systems against each other | Marketing and sales see the same numbers for shared measures |
| Week 4 | Review API usage and agree the ongoing review cadence | A named owner and a monthly checklist |
Red flags
- Every HubSpot contact syncing to Salesforce.
- Two-way sync on fields both teams edit.
- Sync errors nobody reviews.
- Owner assignment handled in both systems at once.

