Integrating HubSpot with Salesforce is one of those projects that sounds simple on paper. Connect two platforms, sync some data, move on. But after helping 40+ companies wire these systems together, we can tell you - the devil's in the details.
Here's what a working integration actually gets you:
HubSpot's own data says companies that align sales and marketing on shared platforms see up to 36% higher customer retention. That tracks with what we've seen firsthand.
Below, we're covering the full picture - data architecture differences, the native connector setup, sync rules, common errors that trip people up, and how to keep things running long-term. Whether you're a Salesforce Admin bracing for a HubSpot rollout or a RevOps leader weighing your options, this guide has you covered.
Think of it as a bridge. HubSpot built and maintains a native connector that creates a two-way data sync between your HubSpot portal and your Salesforce org. Contacts, companies, deals, tasks - they all flow back and forth every 15 minutes without anyone touching a CSV file or writing API code.
One thing that surprises people: HubSpot owns the whole thing. You start the setup in HubSpot, install a managed package on the Salesforce side, and then manage everything - field mappings, sync rules, inclusion lists - from HubSpot's settings. Salesforce doesn't really "see" the connector in its own UI.
Supported platforms: You'll need Salesforce Enterprise, Unlimited, or Professional edition (with API access enabled). On the HubSpot side, any Professional or Enterprise subscription works - Marketing Hub, Sales Hub, Service Hub, Content Hub, or Smart CRM. Salesforce Government Cloud is supported too. Group Edition? Not supported.
Fair warning: flipping the integration on doesn't mean every record syncs instantly. Records move based on triggers - manual imports, list membership, or updates to mapped fields. That's actually a good thing (more on that in a second), because it gives you control over what crosses between systems.
Here's the thing. Most companies don't pick one or the other. They run HubSpot for marketing automation and lead nurturing, then hand everything to Salesforce for sales. Totally normal setup. But when those two platforms can't talk to each other? That's when things get messy.
Picture this: marketing's building leads in HubSpot, sales is grinding through opportunities in Salesforce, and neither team can see what the other is doing. Missed handoffs. Duplicate outreach. Blame games about lead quality. We watched a SaaS company in Austin lose three qualified deals in Q2 2025 because sales never saw the demo requests marketing captured.
When you connect both platforms through a Salesforce integration partner, every lead gets one unified timeline. Sales sees which emails a prospect opened, which pages they hit, and which forms they filled out - all without leaving Salesforce.
Nobody enjoys exporting CSVs from HubSpot and importing them into Salesforce. Nobody. We've worked with teams spending 5-10 hours a week just shuffling data between platforms. That's a part-time employee's worth of busywork.
With the native integration running, a phone number updated in Salesforce shows up in HubSpot within 15 minutes. Same thing the other way around. No spreadsheets, no fat-finger errors.
On average, marketing touches a prospect 8-12 times before they're sales-ready. Without integration, all those touchpoints- email opens, content downloads, webinar sign-ups - sit in HubSpot where your sales reps can't see them. That's a lot of context going to waste.
Once connected, that engagement data flows into Salesforce. Reps can spot patterns and personalize their outreach based on what a prospect actually cared about. Worth it.
Speed kills deals - or saves them. HubSpot can score leads based on engagement and behavior, then automatically push those leads into Salesforce and assign them to the right rep. No waiting. No manual routing.
A lesson we learned the hard way on Salesforce Sales Cloud implementations: cutting lead response time from hours to minutes can double conversion rates. We saw one client go from a 6-hour average response time to 22 minutes after setting up automated routing. Night and day difference.
Quick aside: if you skip this section, you'll probably regret it later. Misunderstanding how these two platforms structure data is the single biggest cause of integration headaches we see. Every. Single. Time.
Here's where things get interesting. Salesforce splits people into two buckets: Leads (unqualified prospects) and Contacts (qualified folks tied to an Account). HubSpot? It throws everyone into one Contact object and calls it a day.
So when the integration syncs, both Salesforce Leads and Contacts map to HubSpot Contacts. HubSpot tracks progression through a property called Lifecycle Stage instead of separate objects. A Salesforce Lead (ID prefix 00Q) and a Salesforce Contact (ID prefix 003) can both show up as Contacts in HubSpot - the Lifecycle Stage value is what tells them apart.
Why does this matter in practice? Two reasons. First, when you convert a Lead in Salesforce, the new Contact syncs to the same HubSpot record. No duplicate created. That's the good news. Second - and this catches people off guard - if you have multiple Salesforce Leads or Contacts sharing the same email address, only the most recently updated record syncs. HubSpot enforces one record per email. Period.
Different names, same idea. The mapping is pretty clean:
Only Contact sync is actually required. Companies, Deals, and Activities? All optional - turn them on based on what you need. Campaign sync is the oddball here. It's more limited and won't do bidirectional updates like the other objects.
Most field types transfer just fine. Text, number, date, checkbox - no drama. But a handful of field types will give you grief:
Getting your Salesforce field configuration right before connecting HubSpot saves hours of chasing down sync errors after the fact.
Not every team needs the same approach. Your team size, budget, and how wild your data model gets will point you in the right direction.
Most teams start here, and honestly, most teams stay here. HubSpot built it, it lives in the HubSpot App Marketplace, and it handles two-way sync for standard objects out of the box.
MuleSoft, Zapier, Workato, Skyvia - these tools pick up where the native connector leaves off. Custom object mapping, advanced sync logic, scheduling, multi-step workflows. More power, more complexity.
Both platforms have REST APIs. If you've got developers and specific requirements that no off-the-shelf tool covers, you can build exactly what you need from scratch.
We've walked clients through this process dozens of times. A standard setup takes 2-4 hours. Enterprise environments with messy field mappings and approval committees? Budget 1-2 weeks.
Real talk: don't use your personal admin account for this. Create a brand-new Salesforce user just for the HubSpot integration. Clone the System Administrator profile and give it a name like "HubSpot Integration User."
Why bother? Because every change HubSpot makes in Salesforce shows up as an edit by whoever authenticated the connection. Mix your personal edits with HubSpot's automated changes and you've got an audit trail that's useless. We've seen this bite teams during SOC 2 reviews.
The integration user needs: API Enabled, View Setup and Configuration, Modify All on the objects you're syncing (Contacts, Leads, Accounts, Opportunities), Modify Metadata, Download AppExchange Packages, and Customize Application.
Head to HubSpot, click the Marketplace icon in the top nav, and search for "Salesforce." Hit Install on the Salesforce integration page. Easy enough.
Planning to test in a sandbox first? Good call. Check the "Yes, this will connect to a sandbox" box before you proceed. Then log in with your dedicated integration user credentials.
HubSpot will ask you to install a managed package in Salesforce. That package sets up the HubSpot Embed component (the old Visualforce module is gone), a permission set, and the connection plumbing.
Pick "Install for All Users" and grant third-party website access when it asks. Installation takes a couple minutes. Once it's done, go back to HubSpot and click Next.
You've got two paths here:
Recommended Setup builds default field mappings between common HubSpot properties and Salesforce fields. If HubSpot can't find a matching property for a Salesforce field, it creates one on the fly.
Advanced Setup gives you manual control over every single mapping, sync direction, and inclusion list right from the start.
One thing we always tell clients: go with Recommended Setup first, then tweak. You'll configure contact sync (all contacts or a filtered segment via an inclusion list), activity and task sync, and object/property sync for Contacts, Companies, and Deals.
Your sales team is going to love this part (spoiler: it's not as hard as it sounds). The HubSpot Embed gives reps access to HubSpot data right inside Salesforce record pages. Contact timelines, sequence enrollment, meeting booking, marketing engagement - all visible without switching tabs.
Drop the HubSpot Embed component onto your Salesforce page layouts for Lead, Contact, Account, and Opportunity. Running Lightning Experience? Just drag and drop it onto your Lightning Record Pages.
Big mistake to sync everything at once. We always start with 50-100 test records. Check that field values move correctly in both directions. Look for type mismatches, blank fields that shouldn't be blank, and whether the 15-minute timing holds up. Confident everything looks right? Then open the floodgates.
Every field mapping gets a sync rule that controls which direction data flows. Pick the wrong one and you'll overwrite good data with bad data. We've cleaned up that mess more times than we'd like to admit.
Default rule for most fields. HubSpot only fills in a Salesforce field when it's empty. Once Salesforce has a value, HubSpot backs off.
When to use it: Fields where Salesforce is the source of truth, but you want HubSpot to fill gaps - company name, phone number, that kind of thing.
Watch out: Setting Lifecycle Stage or Lead Status to this rule is a trap. After the first sync, HubSpot can't update those values anymore. That breaks any marketing automation workflow that depends on stage progression. We see this mistake at least twice a month.
Salesforce wins. Always. HubSpot can read the data but never touch it.
When to use it: Fields only sales should manage - Account Owner, custom scoring fields, revenue data.
Both platforms can update the field. Whichever was updated most recently wins.
When to use it: Honestly, most fields should use this. Email addresses, phone numbers, job titles — anything either team might update on any given Tuesday.
The field sits in both systems but data stays put. No crossing the bridge.
When to use it: Sensitive fields you need to keep isolated (HIPAA data, internal notes) or fields where the data formats just don't play nice together.
We can't stress this enough. Every single team we've worked with that skipped this step spent twice as long fixing data problems after going live. Don't be that team.
Data quality audit:
Field mapping plan:
Access and permissions:
Team preparation:
Inclusion list strategy:
What we've seen is that orgs carrying years of technical debt in Salesforce really should work with a Salesforce administration partner to clean house before plugging in another system. Dirty data in one platform becomes dirty data in two. Fast.
Sync errors will happen. Not a question of if, but when. Here's what we see most often and how to fix each one.
Problem: Same person shows up as both a Lead and a Contact in Salesforce, or multiple HubSpot Contacts point to one Salesforce record.
Fix: HubSpot deduplicates by email address - one record per email, no exceptions. Before you flip the integration on, merge your duplicate Leads and Contacts in Salesforce. After go-live, combine Salesforce duplicate rules with HubSpot's built-in dedupe tool to catch new ones as they pop up. We had a healthcare client discover 3,400 duplicate Contacts during this step alone. Better to find them early.
Problem: A Salesforce field type doesn't match the HubSpot property type. Sync fails for that field.
Fix: Open the field mapping in HubSpot's integration settings and look for the red flag. Common fixes: convert a HubSpot text field to a dropdown so it matches a Salesforce picklist, or create a new HubSpot property with the right type. Trying to force incompatible types? Don't. Build a compatible intermediary property instead.
Problem: Salesforce has picklist values marked "inactive." HubSpot tries to sync those values back and Salesforce says no.
Fix: Go into Salesforce and replace inactive picklist values with active ones, or just delete them. Need to keep the historical data? Create a formula field or pull a report before you remove the inactive values. Ten minutes of prep saves hours of error-chasing.
Problem: Integration burns through Salesforce's daily API call limit. Syncs stop cold.
Fix: Here's what trips people up - a single contact sync can eat up to 4 API calls. Syncing 5,000 records a day means 20,000 API calls. That adds up fast. Check your Salesforce API usage in Setup → System Overview. From there, you can reduce the number of mapped fields, use an inclusion list to shrink sync volume, or upgrade your Salesforce edition for a higher API ceiling.
Problem: Changes aren't showing up in the other system, or they're taking way longer than the expected 15 minutes.
Fix: Pull up the sync status in HubSpot's integration settings and look for error messages. Common culprits: the integration user's credentials expired, someone changed permissions on the Salesforce side, or HubSpot's inclusion list is quietly excluding the record. Re-authenticate the integration user if needed. Then verify the record actually meets all your sync criteria. Nine times out of ten, that's the fix.
Getting the integration live is half the battle. Keeping it healthy? That's the other half. Here's what we recommend based on managing these integrations for clients since 2019.
Open HubSpot's Salesforce integration dashboard every week. Look at error counts. Check for failed syncs. Watch for records sitting in the queue longer than they should.
Catching problems early matters. A lot. One misconfigured field left unchecked for a month can snowball into hundreds of errors. We saw a fintech company rack up 1,200 sync errors in 6 weeks from a single picklist field that got changed during a Salesforce update. Nobody noticed until their sales team started complaining about missing lead data.
Salesforce ships three big releases a year — Spring, Summer, Winter. Each one can introduce new field types, change API behavior, or retire features. After every release, review your field mappings and run a few test syncs. Same rule applies whenever your team adds custom fields in either system.
That said, most teams forget this step. Put it on your calendar. Literally.
Not every record belongs in both systems. Use HubSpot's inclusion list to control which contacts flow into Salesforce — maybe only those with Lifecycle Stage = MQL or higher. Keeps Salesforce clean. Cuts API usage.
Selective Sync goes the other direction. It limits what Salesforce data HubSpot can access, based on the integration user's profile permissions. Handy for compliance (hiding HIPAA-protected fields, for example). But don't go overboard. Overly restrictive Selective Sync causes more headaches than it prevents.
Someone tweaks the integration user's Salesforce profile or role? The integration can break without anyone knowing. Not ideal. Add the integration user to your change management checklist so permission changes get flagged and tested before they cause silent failures.
"Is it free?" That's usually the first question we get. Short answer: the native connector comes included with HubSpot Professional and Enterprise plans. No extra fee. But the real cost? It goes beyond the subscription.
HubSpot plan requirements: Professional or Enterprise on any Hub. Marketing Hub Professional starts around $800/month as of early 2026. Already on one of these plans? Then the connector itself costs you nothing extra.
Salesforce edition requirements: You need API access. Enterprise, Unlimited, and Performance editions have it built in. Salesforce Professional can work, but you might need an API access add-on depending on your contract terms. Check before you assume.
Dedicated integration user license: Salesforce recommends a full platform license for the integration user - not an integration-only license. That means an extra Salesforce seat on your bill.
Third-party tool costs (if applicable): Going beyond the native connector? Zapier starts around $50/month for basic plans. MuleSoft and Workato enterprise tiers can run $500+/month.
It does. HubSpot has a native Salesforce integration that syncs contacts, companies, deals, and activities in both directions. You'll need a HubSpot Professional or Enterprise plan and a Salesforce edition with API access.
For a standard setup, 2-4 hours. Enterprise orgs with tangled field mappings, custom objects, data cleanup backlogs, and approval committees? More like 1-2 weeks. Either way, add a few days for testing and validation. Don't skip that part.
We get asked this a lot. HubSpot's grown into a full CRM platform, but for most enterprise use cases, it's not a swap-in replacement. Salesforce goes deeper on customization, reporting, app integrations, and complex sales process support. What most mid-to-large companies do is run both - HubSpot for marketing, Salesforce for sales - and connect them. That's the practical play.
Enterprise, Unlimited, Performance, and Developer editions all work natively. Professional edition works too, but you might need to buy API access separately. Government Cloud? Supported. Group Edition? Nope.
Every 15 minutes. You can't change that - it's a fixed interval baked into the native connector. Need real-time sync? You'll have to build a custom integration using the HubSpot or Salesforce APIs, or grab a third-party tool that supports webhook-based triggers.
Yes, but with limits. As of early 2026, HubSpot has expanded custom object sync, but it still doesn't match what third-party tools can do. If custom objects are central to your setup, look at MuleSoft or Workato. Or you could go the custom Salesforce integration route and have something built to your exact specs.
Need help connecting HubSpot with your Salesforce org? First-time setup or fixing one that's gone sideways - we've done both. Minuscule Technologies has delivered 75+ Salesforce integration projects across industries. Our team handles data mapping, field configuration, ongoing monitoring, and the troubleshooting that comes with it. Schedule a free strategic call and let's talk through what your integration actually needs.
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
