Connect HubSpot to Salesforce

Marketing runs in HubSpot, sales runs in Salesforce, and the two need the same picture of a contact, a company, and a deal. HubSpot's own Salesforce sync covers the basics, but many teams outgrow it: they need field-level control over who wins, dedup logic that matches their data, custom object coverage, and a record of what the sync did.

• Each field has a defined source of truth, so a rep editing a title in Salesforce is not overwritten by a stale HubSpot value, and vice versa
• New contacts are matched, not duplicated: email first, then the stored cross-system IDs, then an optional name-and-company check
• Custom objects and custom fields on both sides are in scope, not just the standard object set
• Every record sync is a run you can inspect, so a contact that looks wrong can be traced to the sync that wrote it

The lead handoff flow most teams turn on first.

HubSpot SQL to a Salesforce Lead, and Salesforce status back to HubSpot

Started when a HubSpot contact reaches Sales Qualified Lead, with dedup against existing Salesforce records and a field-level merge on the way back.

1. 1
   Trigger: HubSpot New or updated contact, polled on the schedule you set, with a Filter that continues only when lifecyclestage is salesqualifiedlead.
2. 2
   Fetch: the trigger delivers the contact record; Get association and a batch read add its company.
3. 3
   Dedup: search Salesforce for a Contact by Email, then a Lead by Email, then a Lead matching LastName plus Company. Use the first match.
4. 4
   Resolve owner: a data table maps the HubSpot owner's email to a Salesforce User.Id. If the contact has no owner, assign by territory rules.
5. 5
   Write: upsert the Salesforce Lead, keyed on the stored Hubspot_Contact_Id__c, mapping the fields below. Company defaults to [Self-sourced] if the HubSpot company is blank, because Lead requires it.
6. 6
   Stamp both sides: write the Salesforce Lead.Id to the HubSpot property salesforce_lead_id, and the HubSpot hs_object_id to Lead.Hubspot_Contact_Id__c.
7. 7
   Reverse: a second flow polls Salesforce Lead and Contact changes and updates HubSpot, but only the fields where Salesforce is the source of truth (lead status, owner, opportunity stage).

The starting map for the HubSpot contact to Salesforce Lead step. The source-of-truth column is the rule the reverse flow reads.

• Qualified people and companies. Contacts at a chosen lifecycle stage become Leads or Contacts. Associated companies become Accounts, matched on domain. (HubSpot to Salesforce)
• Marketing context. Original source, first and last touch campaign, and email engagement land as fields or campaign members for attribution in Salesforce. (HubSpot to Salesforce)
• Pipeline and ownership. Lead status, opportunity stage and amount, owner changes, and closed-won flow back and set the HubSpot lifecycle stage and deal. (Salesforce to HubSpot)
• Consent and do-not-contact. An email opt-out or a do-not-contact flag set on either side reaches the other on the next poll, whichever system it originated in. (Either direction)

The same controls apply to this sync as to every other Neblex workload.

• Run history. Every record sync is a run with each step's input and output. A failed run can be replayed from the step that failed, and the stored cross-system IDs stop a second create.
• Approval steps. Add a Wait for form step wherever a person should check a change first, such as a bulk change or a merge that would collapse two Salesforce records into one.
• Scoped access. HubSpot uses a private app token with only the needed scopes. Salesforce uses a connected app and a permission set limited to the synced objects.
• Environments. Build against a HubSpot test account and a Salesforce sandbox, then promote the same flow and mapping to production.