Marketing swears the lead was sent on Tuesday. Sales swears it never arrived.
A clean HubSpot Salesforce integration ends that argument for good, because both teams finally look at the same record. Marketing keeps the tool it loves for campaigns and forms, sales keeps Salesforce for pipeline and forecasting, and the record in the middle stays the same on both sides.
Here is how to set it up in an afternoon, and the five mistakes that quietly fill both systems with duplicates. If you would rather have it built and tested for you, that is exactly what our Salesforce integration services cover.
What is a HubSpot Salesforce integration
A HubSpot Salesforce integration is the native connector that keeps contacts, leads, companies, deals and activities in sync between both systems based on rules you define. You decide which records travel, which fields map to which, and which system wins when the same field is edited in both places. Sync runs on a regular cycle of roughly every 15 minutes, and many events such as form submissions and property changes trigger a faster update.
This is different from a migration. If you are moving off HubSpot entirely, our HubSpot to Salesforce migration checklist is the better starting point. This guide is for teams that want to keep both systems and run them as one.
What you need before you connect
- A Salesforce edition with API access, such as Enterprise or Unlimited, or Professional Edition, which the connector also supports. Group Edition is not supported
- A HubSpot Professional or Enterprise subscription on at least one hub, since the connector is not available on Starter plans
- A dedicated integration user in Salesforce with system administrator access and the permissions HubSpot asks for
- A written rule for field ownership, one line per important field saying which team and which system owns it
That last point takes ten minutes and saves weeks. Most sync problems we fix are not technical. They come from two teams quietly assuming they each own the same field.
Step 1. Create a dedicated integration user in Salesforce
Create a new Salesforce user just for the connector, for example [email protected]. HubSpot requires the connecting user to be a system administrator, with API Enabled, View Setup and Configuration, Modify All on the objects you plan to sync, and a few metadata permissions for embedding HubSpot in Salesforce.
Never connect with a real person's login. When that person leaves or changes role, the sync breaks, and every record HubSpot creates looks like it was created by them. A dedicated user keeps the audit trail honest and survives team changes. 👍
Step 2. Install the connector and choose what syncs
In HubSpot, open the App Marketplace, find the Salesforce integration and start the install. You will log in to Salesforce as the integration user, install the HubSpot package, and then walk through the setup wizard for contacts, companies, deals and activities.
The most important choice on this screen is the inclusion list. It tells HubSpot which contacts are allowed to sync to Salesforce. Without one, every newsletter signup and every student downloading an ebook lands in Salesforce as a lead. With one, only contacts that meet your qualification rule, for example marketing qualified leads with a valid company email, cross over to sales.
Step 3. Map fields and decide who wins on conflicts
HubSpot gives every mapped field a sync rule. You can always use Salesforce, prefer Salesforce unless it is blank, keep the field two way, or not sync it at all. The goal is not to sync everything. It is to sync the fields each team actually needs and to make every conflict predictable.
A simple pattern works for most teams. Marketing data such as source and lifecycle stage flows from HubSpot to Salesforce, and sales data such as owner and status flows back. Contact details stay two way, with Salesforce as the tie breaker.
Step 4. Set up lead handoff rules
This is where the lead fights actually end. Agree on one moment when a contact becomes sales' responsibility, usually when the lifecycle stage reaches marketing qualified lead, and make that moment visible in both systems.
- Lifecycle stage in HubSpot decides when a contact joins the inclusion list and syncs to Salesforce
- Lead status in Salesforce shows what sales did with it, and syncs back so marketing can see the outcome
- Owner assignment happens in Salesforce, through assignment rules or a flow, so routing lives in one place
When a rep marks a lead as unqualified, that status returns to HubSpot, and marketing can move the contact into a nurture program instead of sending it again next week.
Step 5. Test with 20 records, then turn on the full sync
Before you switch on the full sync, pick 20 test contacts that cover your real cases. Include a brand new lead, a contact that already exists in Salesforce, a contact with a personal email, one with a missing company, and one whose owner should change. Run them through, then check each record on both sides, field by field.
Only when all 20 behave as expected do you open the inclusion list to the full audience. Watch the sync error log in HubSpot daily for the first week, and keep an eye on Salesforce API usage, since a single contact sync can use several API calls.
Five mistakes that create duplicates
- No inclusion list. Every contact syncs and Salesforce fills with leads nobody will call. Fix it by syncing only qualified contacts
- Two way sync on every field. Both teams overwrite each other and nobody trusts the data. Fix it by giving each field one clear owner
- No matching rule on email in Salesforce. Leads and contacts get created twice for the same person. Fix it with Salesforce duplicate and matching rules on email before you connect
- A personal user as the integration user. The sync breaks the day that person leaves. Fix it with a dedicated integration user
- Ignoring deleted records. HubSpot and Salesforce do not treat deletions the same way, so records reappear or vanish on one side. Fix it by agreeing a deletion policy and testing it in Step 5
We used the same discipline in a recent move for a 25 person B2B analytics SaaS team. The project took 4 weeks, lost zero records across more than 5,000 contacts, companies and deals, and improved pipeline visibility by 40%. 📈
Common questions
Is the HubSpot Salesforce integration free?
The connector itself has no separate fee, but it needs a HubSpot Professional or Enterprise subscription and a Salesforce edition with API access. The real cost is the setup time and the care it takes to get mapping and handoff rules right.
How often does the HubSpot Salesforce integration sync?
The regular sync cycle runs roughly every 15 minutes. Many events, such as form submissions, property updates and new records, trigger a faster sync, so in practice most changes appear within minutes.
Can I sync custom objects?
Yes, custom object sync is available with HubSpot Enterprise. It is worth planning carefully, since every extra object adds API usage and mapping work.
See how we approached a full move in our HubSpot to Salesforce migration case study, or explore our Salesforce integration services for help with any other system.
When marketing and sales look at the same record, the conversation moves from whose fault it is to which deal to close next.
