HubSpot Salesforce Integration: How to Set It Up and Make It Work
The HubSpot Salesforce integration is not plug-and-play. Platform ownership, sync error prevention, governance rules, and when to get expert help.
Table of contents
HubSpot Salesforce Integration: How to Set It Up and Make It Work
The native HubSpot-Salesforce connector takes minutes to switch on, which is exactly why most integrations fail. The setup that decides whether it works isn't technical, it's this: define which platform owns what before you sync a single record. Give HubSpot lead capture, attribution, and marketing automation; give Salesforce pipeline, reporting, and the system of record. Then map only the fields you need, name a winner for every field conflict, run selective sync so you don't burn contact limits on dead data, and check the error logs on a schedule rather than waiting for a rep to report a missing lead.
Skip the ownership decision and the two systems will fight, quietly, over every record. RevBlack has audited dozens of instances where the connector was live and green while sync errors dropped high-intent leads and nobody could say which platform was right.
How does the native HubSpot Salesforce integration work?
The native HubSpot-Salesforce integration syncs standard objects between the two platforms automatically - but the default mapping is a starting point, not a final architecture.
Out of the box, standard objects line up like this:
- Accounts sync to Companies
- Opportunities sync to Deals
- Activities sync to Events
On HubSpot Enterprise, up to ten custom objects can be synced. A new contact in HubSpot becomes a lead in Salesforce. When a deal closes in Salesforce, HubSpot moves that contact to Customer.
RevBlack recommends having a solid data hygiene protocol in place before activating the sync - bad data that enters the integration corrupts both systems simultaneously. For the full deduplication and data quality setup before go-live, see the CRM deduplication playbook.
HubSpot and Salesforce are complementary, not competitors
HubSpot and Salesforce are not interchangeable - they are complementary, and most high-growth B2B teams run both for that reason.
Salesforce is the gold standard for enterprise CRM: highly customizable, scalable, and deeply integrated with ERP, CPQ, and billing systems. HubSpot wins on usability and marketing tools: lead capture, automation, attribution, campaign management, and sales engagement that marketing and SDR teams actually adopt.
A common setup is using HubSpot for marketing automation and engagement while Salesforce remains the core CRM and pipeline system. For most RevBlack clients, replacing Salesforce is not realistic - it is too embedded in daily operations. But missing out on HubSpot's marketing capabilities is also a real cost. Integration is the answer, as long as it is done with a clear plan.
HubSpot's marketing strengths in a dual-stack setup
HubSpot's Marketing Hub is often the reason teams bring it alongside Salesforce - and understanding its specific strengths clarifies which platform should own which functions.
Email marketing: Automation workflows, performance tracking, A/B testing, GDPR compliance, and subscription management.
Campaign marketing: Drag-and-drop landing pages, form builders, campaign-level reporting, and Google Search Console integration.
Sales enablement: Native lead scoring, company scoring, calculated properties, and activity reporting.
Inbound and channel marketing: Omni-channel automation, ABM tools, ad management, video hosting, blog creation, and live chat.
These marketer-first features make HubSpot the strongest complement to Salesforce's enterprise backbone - but they only deliver value if the integration is configured to let HubSpot own these functions without Salesforce overwriting them.
The most common integration challenges
Sync errors are the most damaging failure mode in a HubSpot-Salesforce integration - and they often happen silently, with no alert to sales or RevOps until a lead has already gone cold.
One of the most common scenarios: a prospect submits a form through HubSpot, fits the ICP, and is ready to engage - but due to a sync error, their information never makes it into Salesforce. The sales team is never alerted, and a high-quality lead slips through the cracks.
Common causes of sync errors include:
- Duplicate records
- Mismatched field types
- Conflicts with third-party integrations
- Misconfigured automations inside HubSpot or Salesforce
Add Salesforce Flows, Process Builders, or Apex triggers and the chances of something breaking increase significantly. RevBlack maps processes, keeps data clean, and monitors sync continuously. For a full breakdown of every error type and how to fix them, see the HubSpot Salesforce sync errors playbook.
The single most important configuration decision
Deciding what each platform owns is the single most consequential configuration decision - and most teams skip it entirely.
If ownership is not defined explicitly, automations will collide. This is most common with lead routing and assignment. If HubSpot handles lead capture and attribution, let it run the full process before sending data into Salesforce. If Salesforce owns pipeline reporting and automation, keep it there and push results back to HubSpot.
Split ownership is a recipe for duplicates, sync errors, and incompatible workflows. The decision has to be made before building anything - not after the first sync conflict.
Campaigns and leads mean different things in each system
Two concepts cause more confusion in HubSpot-Salesforce integrations than any others: campaigns and leads. They share names but do not share functions.
Campaigns: A HubSpot campaign tracks assets and how they perform: email clicks, landing page views, ad clicks. A Salesforce campaign tracks people and companies: deal status, lead stage, new business. They are not the same object and were never meant to produce matching numbers. Build reports that make the distinction obvious and train the team on when to look at HubSpot versus when to look at Salesforce.
Leads: In HubSpot, leads are a sub-object of a contact, used to represent qualification and intent. In Salesforce, leads are a distinct record type that converts into a contact, account, and opportunity. They share a name but not a function - and they do not sync natively. For B2B organizations with a defined TAM and ICP, RevBlack often recommends bypassing lead objects entirely and working directly with contacts, accounts, and opportunities to eliminate duplication. For the full architectural decision on leads vs. contacts in Salesforce, see the guide on why to replace lead objects with contacts in Salesforce.
Five governance rules that keep the integration clean
Beyond the basic sync setup, five governance guardrails prevent the integration from drifting into a mess of conflicting data and broken automations.
1. Custom mapping Do not sync every field across both systems. Decide which platform wins when there is a conflict. Without a clear winner per field, hours get wasted untangling fields that keep overwriting each other.
2. Selective sync Be selective about what enters HubSpot. Dumping every Salesforce record into HubSpot burns through contact limits and clutters reports with dead data. Use inclusion lists or a dedicated integration user so only the right contacts flow through.
3. Governance rules Agree on the rules before things break. What counts as a duplicate? Which fields can never change, and which should always update? If these are not set upfront, the system makes the decision - and it will not match what the team expects.
4. Third-party integrations Pick a home base - the tool everything else connects to. For most RevBlack clients, that is Salesforce. Connect everything there and let HubSpot pull what it needs. Wiring tools into both platforms builds a spaghetti architecture that nobody can maintain.
5. Performance monitoring Do not wait until reps complain about missing leads. Check the error logs proactively. Look for records stuck in processing. A five-minute daily review prevents a nasty surprise at the end of the quarter.
When should you get expert help?
The native integration handles straightforward setups - but several scenarios require a partner with hands-on experience in both platforms.
Consider getting expert help when:
- The Salesforce org is loaded with custom objects and workflows
- Sensitive data is involved where mistakes are not an option
- Flows, Apex, or other heavy automations are already running
- There is no dedicated admin watching either platform
RevBlack is one of the few consultancies that is a certified partner with both HubSpot and Salesforce. The result is an unbiased opinion on which platform should own what, a proven integration playbook, and an approach that aligns technology to revenue rather than to features.
