HubSpot and Salesforce integration: the setup decisions that decide whether your pipeline reports can be trusted
Installing the HubSpot and Salesforce integration is quick. Making it trustworthy is not, because the defaults do not decide which system owns each field, which records should sync, or how campaign and source data reach the opportunity. Decide those rules before you sync, test them in a sandbox, and judge the result by one number: the share of new opportunities that carry a reliable original source and campaign.
Key takeaways
- The connector moves data. It does not decide which system is the source of truth for each field. That is your job.
- HubSpot requires a Professional or Enterprise subscription, and Salesforce needs an edition with API access or Professional. Group Edition is not supported.
- One contact can use up to four Salesforce API calls, and the integration has a daily limit. Sync only the records sales should work.
- Records do not sync on their own after setup. Plan the first import and the sync triggers on purpose.
- Measure success by source and campaign coverage on new opportunities, not by whether the sync status is green.
Why this integration is where marketing credit gets lost
Most B2B companies run marketing in HubSpot and sales in Salesforce. The integration is the only bridge between the campaign that created interest and the opportunity that closed. When it is set up with defaults, three things usually happen: original source values get overwritten, duplicate leads appear, and opportunities reach Salesforce with no link back to the campaigns that influenced them.
The result is the argument every CMO knows. Marketing reports strong lead numbers in HubSpot, sales reports thin pipeline in Salesforce, and finance trusts neither. The problem is rarely the tools. It is a set of setup decisions nobody owned.
What you need before you connect
HubSpot’s documentation sets the requirements. On the Salesforce side you need an edition with API access, or Salesforce Professional, and Group Edition is not supported. The connected Salesforce user must be a system administrator with API Enabled and Modify All on every object you plan to sync, such as leads, contacts, accounts, campaigns and opportunities. On the HubSpot side you need a Professional or Enterprise subscription in one of the hubs.
Two details trip up enterprise teams. HubSpot notes that a Salesforce instance with Enforce IP Restrictions on Every Request turned on will block the connection, because HubSpot’s IP addresses cannot be allowlisted. And if several HubSpot accounts connect to one Salesforce instance, HubSpot recommends setting contact creation to Don’t automatically create HubSpot contacts, or records created by one account can appear in another.
The six decisions that matter more than the install
| Decision | What goes wrong with defaults | What we recommend |
|---|---|---|
| Which records sync | Every contact syncs, including students, competitors and junk, and burns API calls | Sync only records that meet a written sales-ready rule, using an inclusion list or a clear lifecycle trigger |
| Field ownership | The last system to edit a field wins, so source and lifecycle values drift | Name one owning system per field. Marketing owns source and campaign fields, sales owns stage, amount and close date |
| Original source protection | Sales edits overwrite how the record first arrived | Keep a read-only original source field that nothing overwrites after creation |
| Lead or contact creation | New HubSpot contacts create Salesforce leads for existing accounts, creating duplicates | Decide when HubSpot creates a lead versus a contact on an existing account, and document it |
| Campaign association | Opportunities close with no campaign history | Map HubSpot campaigns to Salesforce campaigns and add contact roles to opportunities so influence is reportable |
| API budget | The daily limit runs out and syncs queue up | Estimate calls before go-live and reserve headroom for other Salesforce integrations |
None of these are technical edge cases. Each one decides whether your attribution report shows marketing’s contribution or hides it.
We fix source data, routing and attribution so sales and finance trust the numbers.
The API budget is a real constraint
HubSpot states that the integration is subject to a daily API call limit and that syncing one contact can use up to four API calls, depending on your settings. For a company with hundreds of thousands of contacts, an unfiltered first sync can compete with every other system that calls Salesforce, from enrichment tools to a data warehouse connector.
HubSpot also notes that records do not sync automatically when you finish setup. You either import existing Salesforce records or let them sync gradually as sync triggers fire. Plan that first load like a migration, with a sample, a dry run and a count you can check afterwards.
Common symptoms and their usual cause
- Duplicate leads in Salesforce: contacts created in HubSpot for people who already exist as Salesforce contacts on an account, or HubSpot Smart Transfer used alongside the integration, which HubSpot says creates duplicates because the two use different identifiers.
- Marketing source missing on opportunities: no contact role on the opportunity, or campaigns that were never mapped across.
- Lifecycle stages jumping backwards: two systems both allowed to write the same field.
- Sync errors piling up: required Salesforce fields or validation rules that HubSpot data does not satisfy.
How to test before you trust it
- Write the field ownership table and the sync rule, and get sales operations and marketing operations to sign it.
- Connect a Salesforce sandbox first, with the same validation rules and required fields as production.
- Push 50 test records through every path: new lead, existing contact, existing account, form fill from a target account, and a closed-won opportunity.
- Check each record in both systems: owner, lifecycle, original source, campaign and opportunity contact role.
- Go live with a filtered sync, then compare record counts and source coverage after one week and after one month.
How to measure whether it works
Track three numbers each month: the share of new opportunities with a reliable original source and at least one campaign, the duplicate rate on new leads, and the number of open sync errors. Our bar is 80%: if fewer than 80% of new opportunities carry a reliable source after the first quarter, we do not let the attribution report guide budget, whatever model sits on top of it.
Why teams bring in a specialist
The connector is easy to install, and that is the trap. The decisions above sit between marketing operations, sales operations and finance, and they are hard to undo once months of data have synced with the wrong rules. An experienced RevOps team brings a tested field ownership model, a sandbox test plan and the reporting that proves the bridge works.
At PlanConversion we start from the report the CFO needs and work backwards to the sync rules. For KNIME, rebuilding measurement end to end meant 100% of paid leads were traceable to closed deals. That traceability starts with integration decisions like these.
Frequently asked questions
Which Salesforce editions work with the HubSpot integration?
HubSpot requires a Salesforce edition with API access, or Salesforce Professional. Group Edition is not supported.
Which HubSpot plan do I need for the Salesforce integration?
A Professional or Enterprise subscription in Marketing Hub, Sales Hub, Service Hub, Data Hub, Content Hub or Smart CRM, according to HubSpot.
Why does the integration create duplicate records?
Usually because contact creation rules do not account for existing Salesforce contacts and accounts, or because Smart Transfer runs alongside the integration. Decide when HubSpot should create a lead and test it in a sandbox.
How many Salesforce API calls does the integration use?
HubSpot says one contact can use up to four API calls, and the integration is subject to a daily limit. Filter what syncs and estimate usage before go-live.
Sources
Related service: RevOps and marketing operations. See also pricing and client results.
We run enterprise B2B demand generation for teams in Montreal, Toronto, Ottawa and the United States.
