July 11, 2026
A HubSpot Salesforce integration connects the two platforms so contacts, companies, deals, and activity history stay aligned in both systems without manual export-import work. Most teams run both because marketing lives in HubSpot and sales runs the pipeline in Salesforce. This HubSpot and Salesforce integration guide covers the native connector, real costs, setup, and best practices - the native connector handles the standard sync for free on qualifying plans, syncing every 15 minutes.
Here's what this guide covers:
By the end, an admin or RevOps lead will know exactly what to configure, what it costs, and where teams usually go wrong.
A HubSpot Salesforce integration is the connection that keeps customer data consistent across both CRMs. When a record changes in one system, the change shows up in the other, so sales and marketing work from the same facts instead of re-keying data by hand.
The reason so many companies need it is simple: they didn't plan to run two CRMs, but they ended up there. Marketing standardized on HubSpot for campaigns, forms, and lead scoring. Sales runs the pipeline, forecasting, and heavy customization in Salesforce. Over time, both systems hold the same contacts and deals, and the records start to drift apart.
That drift is where the pain shows up. A rep updates a phone number in Salesforce, marketing changes a lifecycle stage in HubSpot, and within a week the two systems disagree on who the customer is. You'll know you need the integration if leads created in HubSpot never reach Salesforce, sales has no idea what a lead did before the handoff, or your team exports spreadsheets just to make reports match.
Done right, the integration removes double data entry, kills conflicting records, and gives both teams a shared view of every account. The hard part isn't the first connection - it's keeping thousands of records accurate in both directions, every day, as your processes change. That's the same discipline our team brings to enterprise Salesforce engineering: clean data first, then automation on top.
HubSpot owns and maintains the native connector, and it's available on HubSpot's Professional and Enterprise tiers. The install process starts and ends in HubSpot, with a few steps completed in Salesforce along the way. When you install it, the connector creates the following inside Salesforce:
Two things drive how the connector behaves. First, an integration user - a dedicated Salesforce user account that HubSpot logs in as. Anything you want HubSpot to see or change in Salesforce, this user needs access to. Second, the sync frequency: the native connector checks for changes on a periodic cycle, historically around every 10–15 minutes, not the instant a record changes.
That timing matters. If your sales team acts on lead data the moment it lands, a 15-minute window can mean calling a prospect on stale information. For most marketing-to-sales handoffs it's fine. For real-time routing or high-volume orgs, it's a known limit - and one reason some teams add a third-party sync layer later.
The connector is bidirectional for the core objects out of the box, includes built-in sync health and error views, and needs no extra subscription on qualifying plans. Where it stops: complex field transformations, non-standard field types, deep custom-object relationships, and consolidating multiple HubSpot portals into one Salesforce org.
Yes - the HubSpot Salesforce integration installs a managed package listed on the Salesforce AppExchange, but you start the install from HubSpot's App Marketplace, not from AppExchange directly. When you connect the two, HubSpot walks you into Salesforce to install its AppExchange package (the managed package, permission set, and Visualforce pages). So while the package lives on the AppExchange, the setup flow is HubSpot-first. You don't search the AppExchange and install it standalone - you trigger it from the HubSpot side and approve the package in Salesforce.
The most common worry about this integration is how sales will act on the data marketing collects in HubSpot. That's what the Visualforce pages are for. When you install the managed package, HubSpot adds a panel to the Lead, Contact, Account, and Opportunity records so reps see marketing context without leaving Salesforce.
The panel surfaces the record's HubSpot activity right on the Salesforce page. As of 2026, reps can view the object's HubSpot timeline and associated records, see property values and property history, enroll the record in a HubSpot workflow, book a meeting, and enroll a contact in a sequence. HubSpot updates these embed features regularly, so the exact list grows over time - but the point stays the same: sales sees what marketing did before the handoff.
It's a quick Setup task, repeated per object:
This is the piece that turns a back-end data sync into something reps actually use every day.
Object mapping is the process of matching HubSpot objects to their Salesforce equivalents - Contacts to Leads or Contacts, Companies to Accounts, and Deals to Opportunities - so records sync to the right place.
Before you sync anything, you need object mapping, because the two CRMs store records as "objects" but don't always name or model them the same way. The biggest difference: Salesforce uses two objects for people (Leads and Contacts), while HubSpot uses one (Contacts). In HubSpot, progression is tracked with a Lifecycle Stage property instead of a separate Lead object.
Here's how the standard objects line up:
Two rules keep field mapping clean. Match data types, not just names - a text field can't drop into a numeric or picklist field without a transformation, and mismatches throw sync errors. And decide which system owns each field before you turn sync on. A HubSpot dropdown property will sync with a Salesforce picklist, but HubSpot has no "inactive" picklist value, so retire old values by deleting and replacing them rather than deactivating.
Add the Salesforce Lead ID and Salesforce Contact ID properties to your field mapping, then read the ID prefix: 00Q means it's a Lead, 003 means it's a Contact. Because HubSpot uses one Contact object for both, this prefix is the fastest way to know which Salesforce record a HubSpot contact is tied to.
Nothing breaks. When a Lead converts to a Contact in Salesforce, the resulting Contact keeps syncing to the same HubSpot contact the Lead was already linked to. The history stays intact - you don't get a duplicate.
No. HubSpot allows only one record per email address. If Salesforce has several Leads or Contacts sharing an email, the most recently updated one syncs to HubSpot. This is exactly why standardizing on email as your unique identifier matters so much.
Getting this data model right is the foundation of any migration or integration project, which is why data migration and harmonization is one of the first things we scope on a Salesforce build.
Every field you sync needs a rule that decides what happens when both systems have a value. Set these wrong and you'll overwrite owners, break lifecycle stages, or lose data silently. The native connector gives you four options:
After install, walk through every mapped field and confirm both the sync direction and the rule. The default mapping is a starting point, not a finished configuration. A field that's mandatory on only one side needs a default value, or the write will fail.
The native HubSpot Salesforce integration costs nothing extra - it's included with qualifying HubSpot Professional and Enterprise plans. The real cost sits in the plans and edition requirements around it, plus any third-party tools or setup help you bring in. Here's the honest breakdown.
The line most teams miss is the Salesforce edition requirement. The integration relies on API access, so you'll need at least Salesforce Professional with the API add-on, or Enterprise edition and above. If your Salesforce contract doesn't include API access, that's a real budget item.
The second hidden cost is cleanup and setup. If you install the connector on top of messy data, you now have dirty data in two systems instead of one, and untangling it later costs far more than cleaning it up front. Third-party sync tools only enter the picture when you need real-time updates, heavy custom-object mapping, or multiple HubSpot portals feeding one Salesforce org - cases the native connector can't handle. For most teams, right-sizing licenses and avoiding tools you don't need is where the savings are, and it's exactly the kind of cost optimization and ROI work we focus on.
Integrating HubSpot with Salesforce follows the same shape whether you use the native connector or a third-party platform. Rushing straight to "install" is how most integrations break. Work through these steps in order.
Before connecting anything, assess data quality in both systems. Run duplicate reports in Salesforce and check for incomplete or stale records. If you've built up years of technical debt, pause and clean it up - syncing dirty data just spreads the mess.
List every object and field you'll sync, and decide which system is the source of truth for each field. A simple spreadsheet with property name, field type, and sync direction saves hours of rework. Don't plan to sync everything - start with Contacts, Companies, Deals, ownership, and core activities.
The HubSpot Salesforce integration user is the dedicated Salesforce account HubSpot logs in as to read and write data. In Salesforce, clone the System Administrator profile and pare it down to what HubSpot actually needs, then create this dedicated integration user. Don't reuse a personal admin login. Every change HubSpot makes shows up as this user, so a dedicated account keeps your audit trail clean and survives staff turnover.
Can you use an existing admin as the integration user? You can, but don't. If HubSpot logs in as a real admin, every sync-driven edit blends with that person's own work, and you lose the ability to tell who changed what. The same goes for reusing one integration user across several tools - you won't know which integration made a change. One dedicated user per integration keeps the audit trail readable.
Install the app from the HubSpot marketplace, sign in with the integration user's Salesforce credentials, and install the managed package in Salesforce. Grant access to the users who'll need it so the HubSpot Visualforce panel appears on their page layouts.
In the integration panel, match HubSpot properties to Salesforce fields one at a time, choosing a sync rule for each. Match picklist values exactly, and confirm field types are compatible. Turn off HubSpot's company auto-enrichment if you don't want it overwriting Salesforce account data.
Create an active list in HubSpot - for example, Lifecycle Stage = Marketing Qualified Lead or greater - and set it as your inclusion list. Only records on that list sync to Salesforce, which keeps junk and half-baked leads out of the sales system.
Know the difference between the two gates. An inclusion list controls which records flow from HubSpot to Salesforce. Selective Sync controls what HubSpot can pull from Salesforce, by limiting the integration user's profile and permissions. Reach for Selective Sync only when you must hide specific data from HubSpot - regulated fields like HIPAA-protected data, for instance. Used without a clear reason, it tends to create more sync problems than it solves.
Create clearly named test records ("UAT Test Contact 001") in both systems and watch them sync. Check property values, owners, associations, and sync direction. Confirm nothing overwrites the wrong side before real data moves.
Switch on full sync, swap the test inclusion list for your real one, and check the error log daily for the first two weeks. Treat launch as a soft launch — catch issues before they spread across thousands of records.
The core HubSpot Salesforce integration best practices are: sync only the fields you need, set a strict rule per field, gate records with inclusion lists, standardize picklists, communicate the change to your teams, and review sync errors weekly.
The teams that keep their integration healthy for years tend to follow the same habits. These are the ones that matter most.
This kind of ongoing discipline is why many enterprises hand it to a partner. Our managed services and platform readiness practice covers exactly this: release governance, org health dashboards, and error monitoring so the sync keeps working as your GTM process evolves.
Even a well-built integration hits recurring issues. Five problems account for most HubSpot-Salesforce sync tickets, and each has a concrete fix.
The pattern behind most of these is the same: the native connector was built for standard, lower-volume sync, so complex cases expose its edges. Fix the simple issues first - duplicates and one-way settings - before you reach for API limits and custom objects. After fixing each issue, return to the error list and resync the affected records. For guidance straight from the source, the Salesforce Admins resources and Apex Hours cover permission and validation-rule specifics in depth.
For a Salesforce integration with HubSpot, most teams should start with the native connector and only add a third-party tool when they hit a real wall. Use this quick test.
Stick with the native connector if: you sync standard objects (Contacts, Companies, Deals), your volumes are moderate, and a 10–15 minute sync window is acceptable. It's included, quick to stand up, and supported directly by HubSpot.
Add a third-party sync platform if: you need near-instant updates for live lead routing, you're mapping custom objects with complex relationships, you're consolidating multiple HubSpot portals into one Salesforce org, or your daily volume pushes against Salesforce or HubSpot API limits. iPaaS tools (Zapier, Workato) handle triggered automations well but often run one-directional recipes. Dedicated real-time sync platforms maintain true two-way state with conflict handling - at a subscription cost that usually starts around $1,000/month.
The decision isn't "which is better" - it's "what does your data model and speed requirement actually demand." Many orgs run the native connector for years without ever needing more. If you're not sure which side you're on, that's a good moment to bring in a Salesforce engineering partner to model it against your record volumes. You can read more perspectives on integration architecture at Salesforce Ben and the Salesforce Developer blog.
Yes. HubSpot includes a native Salesforce connector on its Professional and Enterprise plans that syncs contacts, companies, deals, and activities bidirectionally for standard objects, with no third-party tool required. For custom objects, high volumes, or real-time updates, teams often add a dedicated sync platform.
The connector installs a managed package, a permission set, and Visualforce pages in Salesforce, then logs in through a dedicated integration user. It maps HubSpot Contacts, Companies, and Deals to Salesforce Leads/Contacts, Accounts, and Opportunities, and checks for changes on a periodic cycle of roughly 10–15 minutes.
The native connector itself is free with qualifying HubSpot Professional and Enterprise plans. Your real costs are the required HubSpot plan, a Salesforce edition with API access, and -only if you need real-time or custom-object sync — a third-party tool that typically starts around $1,000 a month.
Yes, as long as your Salesforce Professional edition includes API access, which is usually a paid add-on. Without API access, the integration can't connect. Enterprise edition and above include API access by default.
The native HubSpot connector covers most needs. Beyond it, iPaaS tools like Zapier and Workato handle triggered automations, and dedicated real-time sync platforms handle custom objects and high-volume bidirectional sync. Duplicate-management and data-quality tools help keep both systems clean.
The native integration syncs on a periodic check, historically around every 10–15 minutes, rather than the instant a record changes. If a workflow depends on real-time data — like routing a hot lead to a rep immediately - a change-data-capture sync platform can propagate updates in seconds.
Only to a point natively. The connector handles standard objects well, but custom objects and their relationships have to be built and mapped by hand on both sides, and complex relationship structures often break down. Teams with tailored data models usually add a dedicated sync platform for full custom-object support.
Use an inclusion list to define which HubSpot records are allowed to sync - typically filtered by lifecycle stage, so only sales-ready leads flow through. To restrict the other direction and hide certain Salesforce data from HubSpot, use Selective Sync by tightening the integration user's permissions.
A basic native-connector configuration can be running in a few hours, plus time for mapping and testing. A clean production rollout - data cleanup, full field mapping, sandbox testing, and a staged go-live - usually takes days to a couple of weeks depending on how complex and messy the two orgs are.
A HubSpot Salesforce integration is only as good as the data model and sync rules underneath it. The native connector gets most teams a long way, but the difference between a clean sync and a two-system mess comes down to preparation: clean data, deliberate mapping, strict rules, and steady monitoring. That's where a Salesforce engineering partner earns its keep. At Minuscule Technologies, we handle Salesforce integrations, data migration, and managed services for Nasdaq-listed enterprises - connecting CRMs, ERPs, and data warehouses without the silos and without the surprise costs. If you're planning a HubSpot-Salesforce sync or untangling one that's drifted, talk to our team about scoping it the right way.
You've seen what's possible. Now, let's make it happen for your business. Whether you need an end-to-end Salesforce solution, a complex integration, or ongoing managed services, our team is ready to deliver.
Schedule a Free Strategic Call
