The HubSpot-Salesforce integration has a reputation. And it's not a kind one.
It's the integration people warn each other about. The one that comes up in every migration conversation and every source-of-truth debate. It's the integration that has launched a thousand Slack messages to me that start with some version of "Why isn’t this syncing..."
It didn't get that reputation because HubSpot didn't care. It got it because everyone has been afraid to update (and potentially break) an integration that nearly 11,000 customers use every single day.
As a result, the backend that powers all of it was last refactored in 2014.
That's not a typo. The architecture that sits between the two most-used CRMs in B2B is twelve years old. And finally, FINALLY…HubSpot is rebuilding it.
What HubSpot (Quietly) Announced
Last week, HubSpot published a post in their community forum titled Rebuilding the Engine: What's Next for the HubSpot-Salesforce Integration. It got a fraction of the attention the Spring Spotlight features got, which is criminal because this affects far more customers than most of the AI features being rolled out.
Here's the TL;DR:
HubSpot has been internally developing v2 of the integration: a near-complete refactoring of the backend architecture that processes the data flowing between HubSpot and Salesforce, including workers, sync pipelines, logic definitions. They've been quietly moving objects onto the new platform for over a year, starting with custom objects, tickets, and activities.
As of last month, company sync is live on v2. Deal sync ships in the coming weeks. Contact sync is targeted for a Q4 2026 beta. And the goal is to fully deprecate the legacy sync engine by mid-2027.
The Problems with the Old Salesforce Integration
Before we get to what's new, let's talk about what's been broken. And a lot has been broken for a long time. So much so that my good friend Lauren Ryan basically built her career on helping companies fix the integration before HubSpot eventually hired her as a Solutions Engineer.
These are just a few of the major problems faced by users:
Duplicate Data - The legacy sync engine only deduplicated contacts on email address, which falls apart the moment you encounter job changes, role-based emails, or Salesforce's separate Lead and Contact objects. Most RevOps teams either bought a third-party dedupe tool, wrote custom scripts, or just accepted that a meaningful chunk of their CRM was duplicates.
The Owner Sync - There was no native sync for the owner field, which means every territory change, reorg, or rep transition creates a silent drift between the two systems. Every RevOps team that has scaled past 50 reps has built some custom middleware to handle this, but that often breaks the moment leadership reshuffles the org chart.
API Limits - HubSpot shares Salesforce's daily API call limit with every other tool integrated to your instance, and bulk operations can blow through the allocation and suspend the entire integration. When that happens, syncing stops and you often don't notice until a rep complains a deal isn't showing up.
Picklist Mismatches - HubSpot stores most dropdowns as open text on the backend, which means you can have values outside of the options in settings. Every time you evolve your data model (refined lead sources, updated lifecycle stages) you create a fresh batch of silent sync errors.
The Salesforce Leads Object - HubSpot has Contacts. Salesforce has Leads and Contacts. And reconciling those at sync time is genuinely hard. The hardcoded logic that handles Lead-to-Contact conversion is the same logic HubSpot's own engineering team admits triggers many errors.
The Debugging Experience - When sync errors stack up, the typical workflow is: open a support ticket, wait, get asked for screenshots, wait, eventually get told "this is a known limitation." HubSpot has now publicly confirmed the legacy platform was hard to debug even for the people who built it — which is the right kind of transparency from a vendor, and which means every RevOps team that has fought this integration for the last decade had completely legitimate grievances.
What v2 of the Salesforce Integration Unlocks
The new architecture brings a set of capabilities that customers have been begging for for years. Every object that runs on v2 gets these out of the box:
Enhanced de-duplication on any field. This is huge. If you've been running third-party tools or custom dedupe scripts just because HubSpot would only dedupe contacts on email, that's a workflow you can now collapse.
Owner field sync. Customers can now sync owner fields natively. If you've ever written a custom workflow with API calls to keep deal owner aligned between HubSpot and Salesforce, you know how much pain this removes.
Unique ID support. Records can be matched on a unique ID, not just email address. This is the difference between a sync that works for clean B2B data and one that works for messy real-world data with duplicate emails, role-based emails, and shared inboxes.
Inclusion lists for any object. You can now use inclusion lists for any object on v2, not just contacts. Control exactly what flows between the systems without writing field mapping workarounds.
Fewer sync errors, faster resolution. Because the logic is simpler and less hardcoded, errors are fewer in the first place, and easier for support to diagnose when they do happen.
And for the company object specifically, v2 unlocks one feature that has been one of the most-requested features for years:
You can finally merge company records.
When you merge a company in Salesforce, the merge will now reflect in HubSpot if you've upgraded to the new company sync.
This wasn't possible on the legacy platform. Now it is. That alone is worth upgrading the company sync.
The Rollout Timeline (and Why It's Reasonable)
Here's the release plan as HubSpot laid it out:
Custom objects, tickets, activities: Already on v2 for all customers. Done.
Companies: Just launched. Self-service upgrade available in the integration settings.
Deals: Launching in the coming weeks.
Contacts: Through Q2 development, estimated beta in Q4 2026.
Full legacy deprecation: Mid-2027.
Now, here's where I want to push back on the easy criticism. It would be very easy to look at that contact timeline and say "HubSpot, why is the most important object the last one to get rebuilt?"
The answer, if you've ever worked with the contact object at scale, is obvious: because it's the most complex object by far. Contacts have the highest volume, the most field associations, the most quirky behaviors around marketing email status, the most dependencies on lifecycle stage logic, the most subscription type considerations. If you rebuild the contact sync wrong, you don't just break a workflow, you take down revenue operations for thousands of companies overnight.
Doing custom objects, tickets, activities, companies, and deals first is the right order. It gives the engineering team a chance to stress-test the v2 platform on lower-stakes objects before they touch the one that, if it breaks, sends RevOps teams into incident response mode.
I'm not saying we should be patient because HubSpot deserves patience. I'm saying we should be patient because a fast contact sync rewrite would be terrifying.
So, What Should You Do?
If you're an admin or RevOps leader running a HubSpot-Salesforce integration, here's the play:
1. Audit your current sync errors and field mappings now.
Before you upgrade anything, get a clean baseline. Document what's working, what's broken, and what custom workarounds you've built that v2 might let you retire (dedupe scripts, owner sync workflows, custom unique ID matching, inclusion list hacks). This becomes your test plan.
2. Upgrade company sync in a sandbox first.
Don't move company sync straight to production. Spin up a sandbox, run the upgrade, and validate that company merges flow correctly between systems. Check your field mappings, especially anything custom. Watch for edge cases on companies with many associated records.
3. Plan your company merge cleanup.
This is the underrated opportunity. Most HubSpot portals I've seen have hundreds — sometimes thousands — of duplicate company records that exist because merging used to break the Salesforce sync. With v2, you can finally clean those up. Build the project plan now.
4. Wait on deal sync until it's been live for at least 30 days.
Deals are higher-stakes than companies. Let other customers be the early adopters, watch the HubSpot Community forums for issues, and upgrade when you have confidence the migration is stable.
5. Do not touch contact sync until you absolutely have to.
The migration period for contacts will run through 2027. There is no upside to being first on the contact migration. The risk-reward on the most important object in your CRM is firmly in favor of waiting until v2 contact sync has been battle-tested.
6. Start documenting your custom integration workarounds now.
Every script, every iPaaS connection, every workflow you've built to work around the legacy sync limitations is a candidate for retirement on v2. Document them all so you have a clear list to evaluate as each object moves over.
The Services Opportunity for HubSpot Partners
If you're a HubSpot Solutions Partner with customers running the Salesforce integration, this is a billable services opportunity you should be acting on this quarter, not next year.
Every customer on the legacy sync has a migration path ahead of them between now and mid-2027. That migration is not a one-click upgrade. It's a project (or, because of the long-term rollout plan, it could even be a retainer by itself):
audit the current sync configuration
document custom workarounds and middleware to retire
plan the upgrade order across objects
build a sandbox test plan
validate field mappings
plan a company-record dedupe cleanup
stand up monitoring for the cutover
Multiply that by a client base of even 20 accounts and you're looking at significant pipeline.
The reach-out is straightforward because the value is obvious: "HubSpot is rebuilding the Salesforce sync engine. Tickets and Companies are live now, Deals are next, Contacts come in Q4. Here's what your migration needs to look like, and here's how we'd scope it…"
Customers will appreciate the heads-up because most of them are not exploring the corners of the HubSpot community forum closely enough to have caught this.
Get the conversations started now. The customers who will need the most help are the ones who built the most custom workarounds.
Treat This Like the Bombshell It Isn’t
This wasn't a flashy announcement (probably because it doesn't come packaged with an AI agent that uses Breeze credits). But for the thousands of customers syncing hundreds of millions of records across HubSpot and Salesforce every day, this is the most consequential thing HubSpot has shipped this year.
The HubSpot-Salesforce integration has been the punchline of more RevOps conversations than I can count. It might finally be time to stop laughing at it.
It’s not too late to sign up for Attribution Unlocked!
We just completed Week 1 of the live bootcamp that will take you from zero to multi-touch in 4 weeks.
The recording of Week 1 is available, so now is the perfect time to catch up before Week 2!
To access the recording and attend weeks 2-4, join Hubsessed Academy as a paying member.
