Skip to main content

How to connect Salesforce and HubSpot without duplicate contacts

Clean up duplicates on both sides before you connect anything. Then pick one matching key, give one system the job of creating records, and decide how leads and contacts map. For a typical setup this takes two to four weeks, and at our rates it costs $1,500–$6,000.

Why duplicates appear when you connect the two systems

HubSpot and Salesforce decide whether two records are the same person in different ways. HubSpot treats email address as the unique identifier for a contact. Salesforce does not enforce unique emails, and it keeps leads and contacts as separate objects, so one person can exist as a lead, a contact, or both.

HubSpot’s native connector links each HubSpot contact to a single Salesforce record. If Salesforce already holds two records with the same email, only one of them stays in sync and the other drifts. If a record has no email at all, the connector has nothing to match on. Most "sync duplicates" already existed before the sync.

The common causes:

  • Existing duplicates in Salesforce: a lead and a contact for the same person, or two contacts entered by different reps.
  • Both systems creating records. A form fill creates a HubSpot contact while a rep enters the same person in Salesforce by hand, before the sync has linked them.
  • Email variations, such as Jane.Doe@acme.com and jane.doe@acme.com , or a personal and a work address for one buyer.
  • Records without an email (phone-only leads, event lists, imports), which cannot be matched on email.
  • A Zapier or Make recipe running alongside the native connector, so two pipes create the same record.

The setup that prevents duplicates, step by step

  1. Audit both databases. Export Salesforce leads and contacts and HubSpot contacts. Normalize emails (lowercase, trim spaces) and count how many addresses appear more than once. This tells you whether you face a small cleanup or a project.
  2. Merge in Salesforce first. Salesforce is usually the sales system of record. Decide which record survives: the converted contact over the open lead, and the record with activity history over the empty one.
  3. Turn on Salesforce matching and duplicate rules for leads and contacts, so new duplicates get flagged or blocked when they are entered. Test them against the integration user; a blocking rule also blocks the sync’s insert.
  4. Choose who creates records. A common rule: HubSpot creates people (forms, marketing), Salesforce creates accounts and opportunities, and reps search before they add anyone. Use HubSpot’s inclusion list so only qualified contacts reach Salesforce.
  5. Decide the lead-versus-contact rule. Choose whether new HubSpot contacts arrive in Salesforce as leads or as contacts, and stick to it. Mixing the two is the largest single source of duplicates we see.
  6. Store the Salesforce ID in HubSpot. Once a record is linked, the Salesforce record ID is a more reliable key than email. Match on it first, email second.
  7. Run a test batch of 50–100 records, including edge cases, then reconcile counts before you sync everything.

Native connector, no-code tool or custom integration

For most companies, HubSpot’s native Salesforce connector plus a proper cleanup is the right answer. Custom code is only worth it when the matching logic is more than "same email".

Option Upfront cost Monthly cost Who maintains it What breaks first
HubSpot native connector Setup and cleanup time Included with eligible HubSpot plans Your admin Records without email; lead and contact duplicates in Salesforce
Zapier or Make Low, a few hours Subscription, scales with task volume Whoever built it No real matching logic, so it creates a new record whenever a search step misses
Third-party sync tool Low to moderate Subscription, usually priced by record volume Vendor, plus your admin Field mappings it doesn’t support; conflict rules you can’t change
Custom integration (our figures) $1,500–$6,000 for two systems at $85/hour Hosting, usually small Us or your engineer, with a runbook Upstream field changes, which it logs and alerts on rather than failing silently

Never run a no-code recipe alongside the native connector on the same object; two pipes writing the same contacts create duplicates.

A worked example

Take a hypothetical 60-person company with 40,000 Salesforce leads and contacts and 30,000 HubSpot contacts. The audit finds that 7% of Salesforce emails appear on more than one record, mostly open leads that were never converted, plus about 2,000 phone-only leads from trade shows.

The flow we would build: a HubSpot form fill creates or updates the contact by email. Once the contact reaches the inclusion list, the connector creates a Salesforce lead. When a rep converts the lead, HubSpot follows the converted contact, and the Salesforce contact ID is stored on the HubSpot record. For the phone-only leads, a small custom job matches on normalized phone number plus company name and sends uncertain matches to a review list instead of auto-merging.

Work Hours Cost at $85/hour
Audit, duplicate report, merge rules 12 $1,020
Supervised merge in Salesforce 8 $680
Connector settings, field mapping, inclusion list 8 $680
Phone-and-company matching job with review list 10 $850
Test batch, reconciliation, runbook 6 $510
Total 44 $3,740

Without the phone-only records, this falls to about 34 hours. If both systems have heavy custom fields with conflicting values, it moves toward the top of the $6,000 range.

Failure modes to plan for

  • Duplicate rules that block the sync. A Salesforce rule set to block, rather than alert, rejects the integration’s insert, and the HubSpot contact sits unsynced with an error few people check.
  • API limits. The connector uses Salesforce API calls from your org’s daily allowance. A bulk import or re-sync can use it up and stall other integrations.
  • Re-authentication. If the integration user’s password, permissions or license changes, syncing stops. Use a dedicated integration user rather than a rep’s login.
  • Conflicting field values. Decide per field which system wins. Otherwise a rep’s edit and a marketing update overwrite each other back and forth.
  • Data that arrives before its record. An activity or deal update can arrive for a contact that hasn’t been linked yet. A custom job should queue it and retry, not create a placeholder contact.

We built this kind of logic for Fundz: a HubSpot, Salesforce and Gmail connector framework with OAuth, incremental sync, deduplication and rate-limit handling across tenants.

When to hire someone, and when not to

Do it yourself if your Salesforce admin can merge duplicates, nearly every record has an email, and you create people in one system only. The native connector and a weekend of cleanup are enough.

Hire help when a meaningful share of records lack email, when leads and contacts are badly mixed, when other integrations already write to these objects, or when a past sync attempt left a mess you now have to reverse.

Wait if nobody has decided whether Salesforce or HubSpot owns the contact record. Settle that first; no tool fixes two systems creating people on equal terms.

Frequently asked questions

Does the HubSpot Salesforce integration deduplicate contacts automatically?
Partly. HubSpot deduplicates its own contacts by email address, and it links each contact to a single Salesforce record. It does not merge duplicates that already exist in Salesforce, and it cannot match records that have no email. Clean up Salesforce before you connect.

Should HubSpot create leads or contacts in Salesforce?
Most B2B teams push new HubSpot contacts in as Salesforce leads and let reps convert them, because that keeps the qualification step in Salesforce. What matters most is choosing one rule and applying it everywhere. Mixing leads and contacts for new people is the most common cause of duplicates.

How long does it take to connect Salesforce and HubSpot cleanly?
Plan on two to four weeks for a typical setup, including the audit, the merge, configuration and a test batch. Installing the connector itself takes an afternoon. The cleanup and the decisions about record ownership take the rest of the time.

Can I use Zapier to sync Salesforce and HubSpot instead of the native connector?
You can, but Zapier has no real matching logic. It relies on a search step, and when that search misses, it creates a new record. For an ongoing two-way contact sync, the native connector or a custom integration is safer. Never run both against the same object.

How much does it cost to fix Salesforce and HubSpot duplicates?
At Smplfy’s rate of $85 an hour, a two-system integration with cleanup typically costs $1,500–$6,000. The low end is mostly configuration and a supervised merge. The high end includes custom matching for records without email and conflict rules for heavily customized fields.

Related answers

Want a scoped estimate for your Salesforce and HubSpot setup?

We’ll send a short written scope or take a free 20-minute call. Have three things ready: roughly how many leads and contacts each system holds, which system creates people today, and what else writes to those records. Start a conversation.