What This Integration Does
This integration keeps contact records, deal data, and pipeline information synchronised between HubSpot and Salesforce so that teams working in either CRM have the same view of every customer relationship. Marketing works in HubSpot. Sales works in Salesforce. The integration ensures that a lead captured through a HubSpot form appears in Salesforce within minutes, and that a deal closed in Salesforce is reflected in HubSpot for attribution and reporting.
The challenge with syncing two CRMs is not moving data — it is deciding which system wins when both contain different information about the same record. This integration includes a conflict resolution layer that applies rules based on field type, update recency, and data source. A phone number updated by a sales rep in Salesforce overrides the older value in HubSpot. A marketing attribution field in HubSpot is never overwritten by Salesforce. These rules are defined during setup and enforced on every sync cycle.
The Workflow
The synchronisation runs bidirectionally on a near-real-time schedule.
When a new contact is created in HubSpot — through a form submission, an import, or manual entry — the integration checks Salesforce for an existing match by email address. If no match exists, a new lead or contact is created in Salesforce with the mapped field values. If a match exists, the integration updates the existing Salesforce record with any new information from HubSpot, subject to the conflict resolution rules.
When a deal progresses in Salesforce — stage changes, value updates, close dates — the integration updates the corresponding deal in HubSpot. Marketing uses this data for closed-loop reporting: which campaigns generated the leads that became revenue. Without the sync, marketing attribution is either manual or missing entirely.
Custom field mapping handles the structural differences between the two platforms. HubSpot properties and Salesforce fields rarely align perfectly. A multi-select field in HubSpot might map to a picklist in Salesforce with different option values. The integration translates between formats so data appears correctly in both systems without manual reformatting.
Lifecycle and lead status fields synchronise with logic, not just value copying. A contact that moves to “Marketing Qualified” in HubSpot triggers a lead status change in Salesforce that routes the record to the correct sales team. A contact that is disqualified in Salesforce is updated in HubSpot so marketing stops sending nurture emails.
Before and After
Before: Marketing and sales operate in separate data silos. A lead captured through a HubSpot campaign is manually entered into Salesforce by an SDR. When a deal closes in Salesforce, someone remembers to update HubSpot — or does not. Marketing cannot prove which campaigns generate revenue because the data lives in a different system. Duplicate records accumulate because nobody is sure which system has the correct information.
After: Every contact and deal exists in both systems with consistent data. Marketing attribution flows automatically from first touch in HubSpot through closed deal in Salesforce and back. Lead handoff from marketing to sales is instantaneous and tracked. The sales team never asks “did we already talk to this person?” because the full interaction history is visible in their CRM.
Who Needs This
This integration is for businesses where marketing and sales use different CRMs — typically because marketing adopted HubSpot for its content and automation tools while sales adopted Salesforce for its pipeline management and enterprise features. It is common in mid-market companies with ten to fifty person sales teams, in organisations that have grown through acquisition and inherited different CRM platforms, and in businesses where the cost of migrating entirely to one platform exceeds the cost of integrating both.
How We Build This
This is a custom API integration using the HubSpot and Salesforce REST APIs, not the native HubSpot-Salesforce connector. The native connector handles basic scenarios but breaks down with complex field mappings, custom objects, non-standard lifecycle stages, and the conflict resolution rules that most real implementations require.
We build a middleware layer that manages the sync logic, handles API rate limits on both platforms, logs every change for audit and debugging, and provides a monitoring dashboard that shows sync status, error rates, and data quality metrics. The integration runs as a managed service with alerting when sync failures occur, so problems are caught before they impact the teams relying on the data.
Get Your CRMs Talking
If your marketing and sales teams are working from different data because HubSpot and Salesforce are not connected, get in touch to discuss the sync rules and field mapping for your specific setup.
Related pages:
Alex
I’m a software developer and CEO of Digital Royalty, helping growing teams scale their SaaS platforms without losing quality, visibility, or control. I focus on building structured, maintainable systems with clear processes, reporting, and accountability. With over a decade of experience across agency and in-house roles, I specialise in delivering long-term, scalable solutions that support complex, evolving products.