The HubSpot Salesforce integration is the most commonly requested setup I see in B2B companies running both platforms — marketing on HubSpot, sales on Salesforce. Done right, it eliminates the data silos that kill marketing attribution and waste 30–40% of a sales team’s time re-entering information between systems. Done wrong, it creates a sync loop that duplicates records, overwrites good data with bad, and makes both systems less reliable than either one alone.
This guide covers how the native HubSpot-Salesforce connector works, how to configure it correctly, and the field mapping decisions that most teams get wrong the first time.
How the HubSpot Salesforce Integration Works
HubSpot offers a native Salesforce connector that syncs data bidirectionally — no third-party tool required. The connector maps HubSpot Contacts to Salesforce Contacts and Leads, HubSpot Companies to Salesforce Accounts, and HubSpot Deals to Salesforce Opportunities.
The sync runs every few minutes by default. Key behaviors to understand:
- Sync direction is configurable per field — you can set HubSpot to Salesforce (one-way), Salesforce to HubSpot (one-way), or both platforms to update each other (two-way). Most fields should NOT be two-way unless both teams are maintaining the same data point.
- Conflict rules matter — when both systems have been updated since the last sync, HubSpot defaults to “most recently updated wins.” You can override this by setting specific fields to always sync in one direction.
- Not all Salesforce objects sync natively — Contacts, Leads, Accounts, Opportunities, and Tasks sync. Custom Salesforce objects require Operations Hub and custom-coded sync workflows.
Before You Connect: Decisions to Make First
Most integration problems are caused by rushing to connect the systems without defining the rules first. Answer these questions before clicking “Connect”:
Which system is the system of record for each data type?
This is the single most important decision. For most sales-led companies:
- Marketing data (lead source, form submissions, email engagement, UTM data) → HubSpot is the source of truth → sync HubSpot to Salesforce only
- Sales data (deal stages, close dates, opportunity value, account owner) → Salesforce is the source of truth → sync Salesforce to HubSpot only
- Contact data (name, email, phone, job title) → two-way sync is usually fine here since both teams update these fields
Do you want to sync all contacts or just MQLs?
By default, HubSpot can sync all contacts to Salesforce — which means every cold lead, every unsubscribed contact, and every test record ends up in Salesforce inflating your Salesforce contact limits. Best practice: use an Inclusion List to only sync contacts that meet a minimum quality threshold (Lifecycle Stage = MQL or above, or Lead Score above a threshold). This keeps Salesforce clean and focused on sales-ready contacts.
How will you handle leads vs. contacts in Salesforce?
Salesforce has both Leads and Contacts as separate object types. HubSpot maps to both but you need to decide your conversion logic: when does a Salesforce Lead get converted to a Contact + Account? If you’re not careful, you end up with the same person as both a Lead and a Contact in Salesforce — with HubSpot syncing to the Lead while sales works the Contact.
Step-by-Step: Setting Up the Integration
- Install the connector — In HubSpot, go to Settings → Integrations → Salesforce. You’ll need HubSpot Super Admin access and Salesforce System Admin access to complete the authorization.
- Run the initial sync audit — Before enabling full sync, run a test with a small batch of contacts. Verify that records map correctly and that there are no field conflicts or data overwrites.
- Configure your Inclusion List — Create an Active List in HubSpot of contacts eligible to sync to Salesforce. Set the integration to only sync contacts on this list rather than all contacts.
- Map your fields — In the Field Mappings section, review every default mapping. Add any custom HubSpot properties that need to appear in Salesforce, and vice versa. Set the sync direction and conflict rule for each field explicitly.
- Configure Activity Sync — Decide whether to sync HubSpot email sends and opens to Salesforce activity. This is useful for Salesforce reporting but can create significant activity log volume. Enable selectively.
- Test with real records — Before turning on for the full team, test the sync with 5–10 real contact records representing different scenarios: new lead, existing customer, contact with a deal in both systems.
Field Mapping Mistakes to Avoid
These are the most common field mapping errors I find when auditing HubSpot-Salesforce integrations:
- Two-way syncing Lead Owner / Contact Owner — if both systems can write to the Owner field, you get ownership conflicts every time a rep is reassigned in one system but not the other. Pick one system as the owner-of-record for each object type.
- Syncing HubSpot Lifecycle Stage to a Salesforce field without a clear mapping — Lifecycle Stage values in HubSpot (MQL, SQL, Opportunity) often don’t map cleanly to Salesforce Lead Status or Opportunity Stage. Define the mapping explicitly or you’ll have contacts in “MQL” in HubSpot and “New” in Salesforce indefinitely.
- Allowing Salesforce to overwrite HubSpot marketing data — UTM parameters, original source, first conversion event — these are HubSpot’s marketing attribution fields. They should always sync one way: HubSpot to Salesforce. Never let Salesforce overwrite them.
- Not mapping Deal/Opportunity close date — If Salesforce Opportunity close dates don’t sync to HubSpot Deals, your HubSpot forecasting and deal timeline reports will be inaccurate.
Maintaining the Integration Over Time
The integration needs ongoing maintenance. Every time a new custom property is created in either system, every time a workflow fires that updates a synced field, every time a Salesforce field is renamed or made required — the integration can break silently. Build these habits:
- Review the HubSpot-Salesforce sync error log monthly (Settings → Integrations → Salesforce → Sync Errors)
- When adding new custom properties to either system, immediately evaluate whether they need to sync
- Run a record audit quarterly: pull a sample of 20 contacts that exist in both systems and verify the key fields are consistent
- Define who owns the integration — one person in marketing/RevOps who gets alerted when sync errors spike
Companies that successfully integrate HubSpot and Salesforce report 30–40% productivity improvements and 25–35% higher lead conversion rates from the improved sales-marketing alignment — but only when the field mappings and sync rules are configured correctly from the start.
Frequently Asked Questions
Does the HubSpot Salesforce integration require a paid HubSpot plan?
The native Salesforce connector is available on HubSpot Professional and Enterprise tiers (Sales Hub, Marketing Hub, or CRM Suite). It is not available on Starter or Free plans. You also need to be on Salesforce Professional, Enterprise, or Unlimited editions — the connector does not support Salesforce Essentials. If you need to connect HubSpot Starter to Salesforce, you’ll need a third-party integration tool like Zapier or Make.
Will HubSpot overwrite data in Salesforce?
Only for fields configured with two-way sync where HubSpot has the more recently updated value. For fields set to “Salesforce to HubSpot only,” HubSpot will never overwrite Salesforce. For fields set to “HubSpot to Salesforce only,” HubSpot will write to Salesforce but Salesforce cannot overwrite back. The risk of accidental overwrites comes from fields left on default two-way sync without thinking through the conflict rules — which is why auditing every field mapping before going live is critical.
How do I handle the HubSpot Leads vs. Salesforce Leads/Contacts problem?
The cleanest approach is to sync HubSpot Contacts to Salesforce Leads until a Salesforce Lead is converted (has an associated Account and Opportunity), then sync to the Salesforce Contact record from that point forward. HubSpot’s native connector handles this automatically when configured correctly — once a Salesforce Lead is converted, subsequent syncs go to the Contact record. The failure mode is when Leads are converted in Salesforce without the connected Contact being surfaced back to HubSpot — always test your conversion workflow with a test record before deploying.
Can I sync HubSpot Deals to Salesforce Opportunities bidirectionally?
Yes, with caveats. You can sync HubSpot Deals to Salesforce Opportunities and vice versa, but the stage mapping requires explicit configuration. HubSpot Deal Stages and Salesforce Opportunity Stages are separate taxonomies — you need to create a field mapping that translates between them. Without this, deal stage changes in Salesforce won’t move the HubSpot Deal stage, breaking your HubSpot pipeline reporting.
What happens to existing records when I first connect the integration?
On initial connection, HubSpot and Salesforce perform a historical sync — they match existing records by email address and link them together. Records that match get linked; records without matches are left standalone. You can configure whether to create new records in each system for unmatched contacts. This initial sync can take hours for large databases. Always run the integration in a sandbox environment first if you have a Salesforce Developer or Partial Data sandbox available.
Connect the Systems — Then Manage the Connection
The HubSpot Salesforce integration is powerful when configured correctly and a constant headache when it’s not. The common thread in every broken integration I’ve fixed is the same: the field mappings were left on defaults, nobody defined the system-of-record rules, and the sync error log was never checked. The connection itself takes a few hours. The configuration decisions take a day. The ongoing maintenance takes 30 minutes a month. That’s the investment for eliminating the data friction that costs your team hours every week.
If your HubSpot-Salesforce integration is causing data problems or you’re setting one up from scratch, our HubSpot integration services cover the full configuration — field mapping, inclusion lists, sync rules, and testing. Book a call with Your HubSpot Expert and let’s get it right the first time.
Need expert help implementing HubSpot the right way? Work with Your HubSpot Expert — we handle setup, automation, and ongoing support so your team actually gets results.