The Salesforce HubSpot integration is not hard to switch on — HubSpot ships a native connector and it installs in an afternoon. What is hard is deciding what should sync, in which direction, and who wins when both systems change the same field on the same record. That decision layer is the integration. The connector is just the pipe.
Trusted by 500+ organizations — including B2B SaaS and technology companies running marketing in HubSpot and revenue in Salesforce with Twopir Consulting.
Built for Revenue Operations
Almost nobody calls us because the connector stopped running. They call because it kept running — faithfully syncing the wrong records, in the wrong direction, for eight months. These are the six failures we are hired to undo.
The integration matches leads and contacts on email address, and only on email address. A prospect who filled in a form with a personal address and was later entered by a rep with a work address becomes two records in both systems, permanently.
Without an inclusion list, HubSpot pushes newsletter subscribers, webinar no-shows and competitor researchers into Salesforce alongside real buyers. Reps stop trusting the queue, then stop working it.
HubSpot's lifecycle stage tracks funnel progression; Salesforce lead status tracks what is happening to that person right now. Mapped to each other without translation, they overwrite one another and neither means anything.
A required field, a validation rule or an unmatched picklist value rejects the update. The record sits in the error queue. Nothing alerts anyone, so divergence compounds silently for months before a report finally exposes it.
Campaign influence is captured on the HubSpot contact, then the lead converts to an opportunity in Salesforce and the link is gone. Marketing can prove it created leads and can prove nothing about revenue.
A bulk import, a re-scored list or a large workflow burns the daily API allocation. Records queue instead of syncing, and the integration can be suspended until calls free up — usually discovered at the worst possible moment.
The Salesforce HubSpot integration is a native, bidirectional connection between HubSpot and Salesforce, installed as a managed package on the Salesforce side and administered from HubSpot. It syncs contacts, leads, companies, accounts, deals, opportunities, tasks and activities, and on HubSpot Enterprise it extends to a limited number of custom objects. HubSpot documents the supported editions and the permissions the integration user needs in its installation guide.
In a properly designed stack the two platforms are not peers. HubSpot owns demand — campaigns, forms, email, content engagement and scoring. Salesforce owns revenue — accounts, opportunities, pipeline stages and the closed-won number the board sees. The integration exists so each system can see what the other knows without either trying to become the other.
That distinction is the whole job. Every real decision in an integration project is a consequence of it: which object a HubSpot contact should become in Salesforce, whether a field syncs two-way or one-way, which system wins a conflict, and which records are allowed across at all. Get those four right and the connector is uneventful for years. Get them wrong and no amount of re-syncing will help. Each of those four has its own depth: the model behind them is Salesforce HubSpot architecture, the field-level layer is Salesforce HubSpot data sync, the failures they prevent are catalogued in common integration challenges, and the pre-launch gates are in our integration checklist. If one platform is replacing the other rather than joining it, see Salesforce HubSpot migration. What the work costs is set out in integration cost, and who owns it afterwards in integration support and managed services.
Twopir Consulting builds and governs that decision layer. We are a Salesforce Partner and a HubSpot Partner, and we work with growing and mid-market companies solving complex CRM, integration and business system challenges — alongside enterprise organisations running the same stack at larger volume. If you are still choosing a partner rather than a configuration, start at our Salesforce and HubSpot integration services page.
The native integration maps HubSpot objects to Salesforce objects on a fixed set of correspondences. Direction, though, is a decision — set per object and then refined per field. This is the default shape of a well-governed build; yours should differ where your process differs.
| HubSpot object | Salesforce object | Direction we usually set | Why |
|---|---|---|---|
| Contact | Lead or Contact | Two-way | Marketing owns engagement and scoring fields; sales owns status and ownership. Which Salesforce object a HubSpot contact becomes depends on whether you run a lead-object process. |
| Company | Account | Salesforce → HubSpot | Account hierarchy, ownership and territory are CRM facts. Letting HubSpot write them back creates account sprawl no one owns. |
| Deal | Opportunity | Salesforce → HubSpot | Pipeline is the CRM's job. HubSpot needs to read stage and amount for attribution reporting, not to author them. |
| Marketing email, form submission, page view | Activity / Task timeline | HubSpot → Salesforce | Reps get engagement context on the record they already work in, without a second login. |
| Campaign | Campaign | Two-way | Associating the two lets Salesforce cost and member data reach HubSpot reporting, which is what makes closed-loop attribution possible. |
| Custom object (Enterprise) | Custom object | Configurable | HubSpot supports mapping a limited number of custom objects. Direction follows whichever system is the authoring system for that record type. |
"We work with HubSpot and Salesforce" hides three services with three different buyers, timelines and prices. Here is where each one starts and stops — and if you want the decision assessed before you buy any of them, that is a consulting engagement rather than a build.
For teams connecting the two platforms for the first time. We install and configure the native integration properly the first time, rather than accepting defaults and discovering the consequences in month six.
For teams already live where the sync technically works but the data does not reflect how the business actually operates. This is the majority of what we do.
For requirements the native integration cannot express: bespoke routing, rollups across lookup relationships, enrichment, or error handling that has to page a human.
The integration is not a project that finishes. Fields get added, workflows change, volume grows, and drift restarts. Ongoing governance is what keeps month twelve looking like week one.
Integrations fail because they are designed around how people believe data flows rather than how it actually flows. The first week of every engagement is spent establishing the difference.
We reconcile both systems record by record and quantify the divergence, then map every field that is supposed to sync against every field that actually does. The output is a written findings document, not a verbal summary.
A field-level specification: authoritative system, sync direction, and the conflict rule for every mapped field. This document is the deliverable your admin keeps long after we leave.
Everything is configured and tested in a Salesforce sandbox against representative data. Nothing reaches production until the behaviour is proven, including the failure behaviour.
Controlled rollout by object and by segment, with a dedicated integration user isolating sync activity from individual logins. Integrity is validated at each stage rather than after all of them.
Error alerting, API allocation monitoring, an ownership model, and a scheduled audit cadence — so the architecture survives the next person to add a field.
A Salesforce HubSpot integration rarely lives alone. These are the connections that most often sit alongside it, and what actually moves across each one.
The core connection. Marketing engagement and lifecycle flow into Salesforce; account, opportunity and closed-won data flow back for attribution reporting.
Firmographic and intent data appended to lead records at creation, feeding scoring and routing so reps stop researching accounts by hand.
Inbound meeting booking and routing. Meeting outcomes write back to the CRM record so speed-to-lead is measurable rather than anecdotal.
Quote and contract generation driven from opportunity data, with execution status returning to the record that triggered it.
Where volume, transformation logic or a third system exceeds what the native connector can express, an iPaaS layer carries the load instead of custom code.
Usage, subscription and payment events joined to the account record, so expansion and churn signals reach the same funnel view as marketing engagement.
Dedupe, normalisation and validation running against both systems, since the connector's email-only matching cannot resolve records on its own.
Both platforms landed in one warehouse where funnel velocity and attribution can be modelled without either system arbitrating the other.
One engagement, documented end to end: a North America B2B SaaS company whose Salesforce and HubSpot had been diverging silently for months behind a home-built sync.
The diagnostic surfaced three problems we did not even know we had. By the time we saw the field mapping spec, it was obvious why the previous sync had been silently corrupting data for months. What impressed us most was that every decision was documented — we were not handed a black box. We owned the system at handover.
Replacing a silently failing sync with a 47-field mapping specification, Apex error handling and closed-loop attribution.
Anyone can authorise the managed package. The work that determines whether your reporting is trustworthy in eighteen months happens in the decisions around it.
Source of truth, conflict rules and deduplication are designed before the first record syncs — not retrofitted after the first bad report.
Every engagement opens with a reconciliation of both systems. We have never once found the data flowing the way the team believed it was.
Sandbox validation covers what happens when a validation rule rejects an update or the API allocation runs out — because that is when integrations actually break.
The field mapping specification, ownership matrix and escalation path are yours at handover. No undocumented configuration, no black box.
Salesforce architecture, HubSpot administration, marketing operations and sales operations sit in the same team. Integration problems live in the gap between those roles.
Yes. The native integration is bidirectional, and direction is configurable per object and then refined per field — two-way, always use Salesforce, or always use HubSpot. In most builds we set marketing engagement fields to flow from HubSpot, pipeline and account fields to flow from Salesforce, and only a small number of genuinely shared fields to two-way. Setting everything two-way is the most common configuration mistake we are asked to fix.
No, and this is the single highest-value decision in the whole build. HubSpot's inclusion list is an active list that controls which contacts are allowed to sync from HubSpot into Salesforce; contacts not on it stay in HubSpot. Without one, subscribers and unqualified traffic land in the CRM and reps stop trusting the record queue. Note the exception: records created first in Salesforce can still sync to HubSpot regardless of the inclusion list.
It matches leads and contacts on email address, and email address is the only field it uses. That means the same person with a work address in Salesforce and a personal address in HubSpot will not be recognised as one record. Deduplication therefore has to be designed deliberately — usually by surfacing create date and the Salesforce Contact and Lead IDs, then merging in the correct system first so the sync resolves the pair rather than recreating it.
The integration requires an edition with API access — Professional, Enterprise, Unlimited and Government Cloud are supported; Group Edition is not. Installation needs a Salesforce system administrator, and the integration user needs API access plus edit permission on each object being synced. HubSpot's own documentation is the authority here and should be checked at the time you install, since edition and permission requirements do change.
Almost always one of three causes: lifecycle stage and lead status mapped to each other without translation, so the funnel means different things in each system; campaign attribution that is not carried through lead-to-opportunity conversion; or records sitting in the sync error queue that one system has and the other does not. All three are architecture problems, not reporting problems, and they are fixed in the mapping layer.
Most commonly, exhausting the Salesforce API call allocation. Bulk imports, re-scoring a large list, mass property updates and big email sends all generate call volume, and when the allocation is consumed records queue rather than sync. Setting the API call allocation in HubSpot deliberately, and monitoring it, prevents the surprise. Permission and validation errors on the integration user are the other common cause.
A clean bidirectional contact and deal sync can be live in two to three weeks. Adding campaign attribution, custom field mapping, deduplication and an enrichment layer typically takes six to eight weeks. On the documented B2B SaaS engagement referenced on this page, the full five-phase delivery ran in under eight weeks from diagnostic to governance handover. The diagnostic phase is the one nobody should compress — skipping it is what produces the silent failures we are later hired to repair.
Yes, and it is more than half our work on this stack. We audit the current configuration, quantify how far the two systems have diverged, identify the root causes rather than the symptoms, and rebuild the mapping and governance layer. Cleanup is sequenced so that merging and remapping do not generate a second wave of duplicates.
Most teams are surprised by their own audit. If you want to know how far Salesforce and HubSpot have drifted apart — and what it would take to close the gap — that is the conversation to have.
Salesforce Partner · HubSpot Partner · Serving US, Canada, UK, UAE, Australia & New Zealand
