HubSpot Salesforce Integration, Take 2: 12 Years Later, the Engine Is Finally Getting Rebuilt

The HubSpot-Salesforce integration has a reputation. And it's not a kind one.

It's the integration humans warn each other about. The one that comes up in every migration conversation, every source-of-truth debate, every late-night Slack message that starts with some version of "Why isn't this syncing?" I've fielded those Slack messages for twelve years. So have you, probably. So have most RevOps leaders running both platforms today.

That reputation didn't show up because HubSpot didn't care. It showed up because almost nobody wanted to touch an integration that 11,000+ customers and a whole lot of stressed-out humans depend on every single day. The backend that powers the whole thing was last refactored in 2014. That's not a typo. The architecture sitting between the two most-used CRMs in B2B is twelve years old.

Finally, finally, HubSpot's rebuilding it. Quietly. Without a Spring Spotlight, without a Breeze-credit headline, without the AI-agent confetti. Just a community post that landed in early May 2026 and barely made a sound.

Here's why it matters, what's actually shipping, and what HubSpot admins and RevOps leads should be doing this year.

Where We've Been: The 2014 Engine That Powered 11,000+ Customers

This story doesn't start in 2026. It starts in 2007, when HubSpot first released a Salesforce integration. It got serious in 2014, when HubSpot shipped its first fully bidirectional object sync. That same year is the one HubSpot now says was the last time the backend got a real refactor.

Here's a quick timeline so the rebuild lands in context:

• 2007. First HubSpot-Salesforce integration ships.
• 2014. First fully bidirectional object sync. Also the last major backend refactor before the current rebuild.
• August 2018. New connector package: faster, more secure, more flexible. HubSpot sunsets the HubSpot Intelligence object inside Salesforce and shifts to a more secure embed.
• September 2018. General availability for bidirectional sync between Salesforce accounts and HubSpot companies.
• April 2021. Salesforce one-way custom object sync goes from public beta to delivered for Enterprise customers.
• February 2024. Bidirectional custom object sync surfaces in a HubSpot product update.
• August 2025. Association sync extended to Salesforce tickets, tasks, and custom objects.
• February 2026. Updated company object sync surfaces in HubSpot community solutions, including deduplication and company-merge support.
• April 2026. Company objects move onto the new v2 engine.
• May 5, 2026. HubSpot publicly describes the v2 rebuild, confirms current object coverage, names deals as next, estimates a contact beta for Q4 2026, and targets full legacy deprecation for mid-2027.

The point of the timeline isn't trivia. It's that the integration has been getting incremental patches for almost twenty years. The plumbing underneath those patches is what's finally getting replaced.

Why It Earned Its Reputation: Six Long-Running Pains

Before we celebrate the rebuild, let's be honest about why the rebuild was overdue. Most of you reading this have lived at least three of these. Some of you have lived all six.

1. Duplicate Data

The legacy sync engine deduplicated contacts on email address. That falls apart the moment you have job changes, role-based emails (think info@ and sales@), shared inboxes, or Salesforce's separate Lead and Contact objects. Most RevOps teams either bought a third-party dedupe tool, wrote custom scripts, or quietly accepted that a meaningful chunk of their CRM was duplicates. None of those options are cheap.

2. The Owner Sync Gap

There wasn't a clean native sync for the owner field. Every territory change, every reorg, every rep transition could create silent drift between HubSpot and Salesforce. Every RevOps team that scaled past 50 reps built some custom middleware to keep deal owner aligned. That middleware tended to break the moment leadership reshuffled the org chart.

3. Shared Salesforce API Limits

HubSpot shares Salesforce's daily API-call allocation with every other tool connected to your instance. Bulk operations and large segment resyncs can blow through that allocation and suspend the integration. HubSpot's own docs say a single contact sync can take up to four API calls, and batch segment resyncs may need at least segment-size times three API calls available. When the budget gets blown, sync stops, and you usually don't notice until a rep complains that a deal isn't showing up.

4. Picklist Mismatches

HubSpot stores most dropdown values as open text on the backend. That means you can end up with values outside the options listed in settings. Every time you evolve your data model (refined lead sources, updated lifecycle stages, new deal types) you create a fresh batch of silent sync errors that nobody catches until reporting goes sideways.

5. The Salesforce Leads Object

HubSpot has Contacts. Salesforce has Leads and Contacts. Reconciling those at sync time is genuinely hard. HubSpot's own engineering team has now publicly acknowledged that the hardcoded logic handling Lead-to-Contact conversion was a frequent source of errors.

6. The Debugging Experience

When sync errors stacked up, the typical workflow looked like this: open a support ticket, wait, get asked for screenshots, wait, eventually get told "this is a known limitation." HubSpot now publicly says the legacy platform had "elaborate and hardcoded logic paths" that were difficult to investigate and sometimes generated errors themselves. That's the right kind of transparency from a vendor, and it means every RevOps team that fought this integration for the last decade had completely legitimate grievances.

Where We Are: What v2 Actually Is

The clearest official description of the rebuild is architectural, not cosmetic. HubSpot describes v2 as a near-complete refactor of workers, logic definitions, and sync pipelines. The legacy characteristic HubSpot calls out by name is "elaborate and hardcoded logic paths." The promised v2 benefits, in HubSpot's own words: faster, more resilient, more flexible sync, fewer errors, easier error resolution, and faster feature-enhancement velocity.

Here's the object-by-object state of v2 as of May 13, 2026:

• Custom objects, tickets, activities. Fully on v2 for all customers. Done.
• Companies. Just launched. Self-service upgrade available in integration settings.
• Deals. Launching in the coming weeks.
• Contacts. Through Q2 2026 development. Beta estimated for Q4 2026.
• Full legacy deprecation. Mid-2027 target.

A reasonable next question: what does "on v2" actually unlock today? Let's get specific.

What v2 Unlocks (And the Catch on Each One)

Every win on this list is real. Every win on this list also has fine print. Both halves matter.

Enhanced Deduplication on Any Mapped Field

If you've been running a third-party dedupe tool or a custom script because HubSpot would only dedupe contacts on email, that workflow is a candidate for retirement on v2 objects.

Catch: Values must match exactly. And the new dedup logic only applies to new records after upgrade, not retroactively. Existing matched records keep their existing matches. Old duplicate debt still needs a separate remediation plan.

Owner Field Sync

HubSpot highlights owner-field sync as a v2-platform enhancement. The custom middleware many teams built to keep deal owner aligned between systems is now a retirement candidate too.

Catch: Owner mappings are still exact-match, two-way only in the mapping rules. The improvement is on the underlying sync engine, not a wholesale rethink of how user mapping works.

Unique-ID Matching, Not Just Email

HubSpot says v2 supports matching records on a unique ID, not just an email address. That's the difference between sync that works for clean B2B data and sync that works for messy real-world data full of shared inboxes and role-based emails.

Catch: Detailed public implementation docs on the unique-ID matching pattern are still thin in the sources I can verify. Treat this as a directional improvement and test before you trust it in production.

Inclusion Lists for Any Object

HubSpot says v2 can support inclusion lists for any object on the v2 platform. If you've been writing field-mapping workarounds to control which records flow between systems, v2 is going to give you cleaner native controls.

Catch: Object-by-object public implementation detail is still light. Inclusion-segment behavior is well established for contacts. For the other objects, expect to validate behavior in a sandbox.

Fewer Sync Errors, Faster Resolution

Because the logic paths are simpler and less hardcoded, HubSpot says you'll get fewer errors in the first place and faster diagnosis when errors happen. This is the change you won't see on a release note but will feel in your support tickets.

The Headline Win: You Can Finally Merge Company Records

Here's the one most customers have been waiting on for years.

When you merge a company in Salesforce on the upgraded company sync, the merge now reflects in HubSpot. That single change retires one of the most-requested feature requests in the HubSpot-Salesforce ecosystem.

Catch: Salesforce records are not automatically merged when you merge a company in HubSpot. The two systems still treat that operation independently. And the company-sync upgrade itself is irreversible, so this is a one-way door. Test in a sandbox first. HubSpot itself says so.

Where We're Going: Why Contacts Last Is the Right Call

It's easy to look at the rollout order and ask, "HubSpot, why is the most important object the last to get rebuilt?" Fair question. Wrong instinct.

Contacts are the most complex object by a wide margin. The highest volume. The most field associations. The trickiest marketing-status, subscription, and lifecycle-stage behavior. The heaviest validation-rule dependency. The most edge cases tied to inclusion segments and Salesforce campaigns. If HubSpot rebuilds the contact sync wrong, the consequences aren't a workflow that breaks. The consequences are revenue operations going down across 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 asking you to be patient because HubSpot deserves patience. I'm asking you to be patient because a fast contact-sync rewrite would be genuinely terrifying for the entire B2B ecosystem.

What Won't Get Easier (Yet)

This is the cautiously half of cautiously optimistic. There's a list of native limitations the v2 rebuild does not appear to fix in any of the public documentation I can verify today. Going in with eyes open beats getting surprised six months from now.

• Only the primary company association syncs for contacts. A HubSpot Community Manager confirmed this in January 2026. If your go-to-market depends on many-to-many account relationships (multi-entity buying groups, channel structures, school district hierarchies, franchise models), the native connector still has a real boundary here.
• Deals are explicitly not deduplicated against Salesforce opportunities. HubSpot's own documentation says this out loud. If you want deal-level dedup, you're still pairing the native connector with another tool.
• Salesforce formula field updates don't trigger sync. This is the kind of "obvious once you know it" gotcha that has bitten plenty of teams who relied on formula-based segmentation.
• Custom object lookup fields can't be mapped directly. You sync those relationships through associations instead. Plan accordingly.
• A custom object can't sync to both Salesforce contacts and leads. Pick one. Architect accordingly.

None of these break the rebuild story. All of them shape what realistic native scope looks like in 2026 and 2027.

What HubSpot Admins and RevOps Leads Should Actually Do This Year

If you run a HubSpot-Salesforce integration today, here's the play. Staged, not big-bang. Honest about what's reversible and what isn't. Designed to retire workarounds, not stack new ones.

1. Audit Your Current Sync Errors and Field Mappings

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. Every integration is, in effect, a security and data bridge between two systems. The longer it sits unaudited, the harder it is to clean up later. This baseline is your test plan.

This is also the moment to remind yourself: garbage in, garbage out. v2 makes sync better. It does not magically clean up data hygiene you've been deferring. If your portal needs a serious cleanup, start with our data hygiene ultimate guide and run a full portal audit before you touch the integration upgrade.

2. Upgrade Company Sync in a Sandbox First

HubSpot itself recommends testing the upgraded company sync in a developer test account or sandbox before enabling it in production. The reason: the company-sync upgrade cannot be reverted. Spin up a sandbox, run the upgrade, validate that company merges flow correctly between systems, and check your field mappings carefully. Watch the edge cases on companies with many associated records.

3. Plan the Company-Merge Dedup Cleanup

This is the underrated opportunity. Most HubSpot portals I've seen have hundreds, sometimes thousands, of duplicate company records that exist precisely because merging used to break the Salesforce sync. With v2, you can finally clean those up. Build the project plan now, because the cleanup is going to surface conversations you've been deferring: which record is the source of truth, which custom properties matter, what enrichment data overrides what.

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. Upgrade when you have confidence the migration is stable. Being first on deal sync is risk with no clear upside.

5. Don't Touch Contact Sync Until You Absolutely Have To

The contact migration runs through 2027. There is no upside to being early on the most important object in your CRM. The risk-to-reward math is firmly in favor of waiting until v2 contact sync has been battle-tested across a lot of portals. Plan around the deprecation date. Don't volunteer to be the test pilot.

6. Document Every Custom Workaround You've Built

Every script. Every iPaaS connection. Every workflow you stood up to compensate for legacy-sync limitations. Document all of them now, before the rebuild eats them. Each one becomes a candidate for retirement as the corresponding object moves onto v2. The teams that built the most workarounds are also the teams that will save the most operational overhead by retiring them.

For Sidekick's HubSpot Partner Friends

If you're a HubSpot Solutions Partner with customers running the Salesforce integration, this is a billable services conversation you should be having 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 isn't a one-click upgrade. It's a project: 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, and 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." Most of your customers aren't watching the HubSpot Community forum closely enough to have caught this. Give them the heads-up.

The Honest Close

This wasn't a flashy announcement. No AI agent, no Breeze credits, no Spring Spotlight stage time. The blog post that announced it got a fraction of the attention the new agents got.

But for the customers syncing hundreds of millions of records between HubSpot and Salesforce every day, this is the most consequential thing HubSpot has shipped in 2026. The HubSpot-Salesforce integration has been the punchline of more RevOps conversations than I can count over twelve years. With v2 finally landing, it might be time to stop laughing at it.

Cautiously optimistic. Because only time, and a lot of careful migrations, will tell.

Frequently Asked Questions

When Will the Contact Sync Rebuild Be Done?

HubSpot estimates a beta in Q4 2026 with a target of full legacy-engine deprecation by mid-2027. That means contact-sync migration starts after the contact-on-v2 release, and the legacy engine retires roughly a year after that. Plan your migration runway accordingly.

Is the Upgraded Company Sync Reversible?

No. HubSpot says the company-sync upgrade cannot be reverted after enablement. That's why HubSpot itself recommends testing the upgrade in a developer test account or sandbox before flipping it on in production.

Will Old Duplicates Be Cleaned Up by the New Dedup Logic?

No. HubSpot's enhanced deduplication on mapped fields applies only to new records after upgrade. Existing matched records are not reprocessed. If you want to fix the duplicate debt that built up under the legacy sync, you need a separate cleanup project.

Do We Still Need a Third-Party Sync Tool Like Workato, Stacksync, or Insycle?

It depends. The v2 rebuild narrows the gap with third-party tools on core native CRM sync, especially for company data quality. It does not eliminate the adjacent market. If you need real-time propagation, external databases in the sync loop, richer many-to-many association models, or aggressive duplicate remediation at scale, specialist tools still earn their seat at the table. If you've been using a third-party tool to work around limitations v2 is fixing natively, this is a great time to re-evaluate.

Who Is This Article Not For?

If you've never logged into HubSpot or Salesforce, this article isn't going to land. Start with our 7 HubSpot Onboarding Mistakes article instead. If you don't run both systems and have no plans to, the migration play here doesn't apply. This article is for HubSpot admins, RevOps leads, and Solutions Partners running the native HubSpot-Salesforce integration today and making decisions about what to do with it over the next 18 months.

Ready to Plan Your v2 Migration?

You don't have to figure this out alone. Book a free strategy call and we'll walk through your current sync setup, your custom workarounds, and a staged migration plan that fits your team and the humans inside it. Your trusty Sidekicks have been in the HubSpot ecosystem since 2014. Funny enough, so has the engine HubSpot is finally rebuilding.

Book your free strategy call.

For more weekly HubSpot breakdowns, browse the full HubSpot Updates feed.