For the first time since 2014, HubSpot is rebuilding the engine that syncs data between HubSpot and Salesforce. The company has confirmed a near-complete refactor of the integration's backend — internally called v2 — and it is already rolling out object by object.
If your business runs both CRMs, this is one of the most consequential integration changes in years. The native HubSpot–Salesforce connector is used by roughly 11,000 customers, and many of its most painful limitations — duplicate records, missing owner sync, shared API limits — trace back to architecture that is now more than a decade old.
This guide explains what the v2 sync engine is, what it fixes, the rollout timeline you should plan around, and the practical steps RevOps and admin teams should take now to avoid surprises during the transition.
The HubSpot–Salesforce v2 sync engine is a ground-up rebuild of the backend that moves data between the two CRMs — the first major overhaul since 2014. It matters to any organization that runs HubSpot and Salesforce together, because v2 addresses long-standing problems like email-only deduplication, no native owner-field sync, and shared Salesforce API limits. The rollout is phased: company sync is already live, deal sync is shipping next, and contact sync is targeted for a Q4 2026 beta, with the legacy engine planned for deprecation by mid-2027. The action it supports is a readiness review of your sync configuration, deduplication rules, and field mappings before each object migrates. Vantage Point helps teams audit and re-architect their HubSpot–Salesforce sync so the move to v2 is clean rather than disruptive.
The v2 sync engine is a near-complete rebuild of the backend that powers the native HubSpot–Salesforce integration — the workers, sync pipelines, and logic that decide how records move between the two systems. HubSpot has confirmed it is the first major overhaul of this integration since 2014.
The legacy engine wasn't rebuilt for over a decade for an understandable reason: it sits between two of the most-used CRMs in B2B, and breaking it would disrupt thousands of businesses at once. So HubSpot is migrating objects onto the new platform gradually, validating each one before moving on.
In practice, "v2" doesn't change how you click through the integration settings overnight. It changes what the integration is capable of — and removes constraints that RevOps teams have worked around with third-party tools and custom scripts for years.
If you run a dual-CRM stack, the sync layer is where data quality is won or lost. When it drifts, marketing and sales work from different versions of the truth, reporting breaks, and AI features sit on top of dirty data. The v2 rebuild matters because it targets the structural causes of that drift, not just the symptoms.
It also matters because the change is happening on HubSpot's timeline, not yours. Objects are migrating now, and the legacy engine is slated for retirement. Teams that review their configuration ahead of each migration will have a clean transition; teams that ignore it risk discovering misconfigurations only after sync behavior changes.
Most of the native connector's reputation comes from a handful of well-known limitations. Here's how the legacy engine compares with what v2 is built to deliver.
| Pain point | Legacy engine (pre-2014 architecture) | v2 sync engine |
|---|---|---|
| Deduplication | Matched contacts on email address only — broke with job changes, role-based emails, and Salesforce's separate Lead/Contact objects | De-duplicate on any field, plus unique ID support for more reliable matching |
| Owner field | No native owner sync; territory and reorg changes caused silent drift | Native owner-field sync |
| Sync scope | Limited controls over which records flow | Inclusion-list support to control what syncs |
| Reliability | Bulk operations could exhaust shared Salesforce API limits and suspend the integration | More resilient pipelines with fewer errors |
| Troubleshooting | Hard to debug, even for HubSpot; "known limitation" was a common answer | Better visibility and a more debuggable platform |
The takeaway: the workarounds many teams built — external dedupe tools, owner-sync middleware, custom error monitoring — exist because of real gaps. v2 is designed to close several of them natively, which is a reason to revisit those workarounds rather than carry them forward unchanged.
HubSpot is moving objects onto v2 in phases. Treat these as directional dates from HubSpot's announcement — they can shift, so confirm current status in your portal.
| Object | v2 status (as announced) | What it means for you |
|---|---|---|
| Custom objects, tickets, activities | Already migrated | Early objects validated on the new platform |
| Companies | Live on v2 | Company sync behavior now runs on the new engine |
| Deals | Shipping next | Review deal field mappings and sync rules soon |
| Contacts | Targeted Q4 2026 beta | The highest-impact object — plan dedupe and Lead/Contact logic now |
| Legacy engine | Planned deprecation by mid-2027 | The transition window is finite; don't defer the review |
Contact sync is the one to watch. Contacts carry the heaviest deduplication and Lead-versus-Contact reconciliation logic, so a configuration that "worked" under email-only matching may behave differently once field-based dedupe is available.
You don't need to wait for contact sync to prepare. A short readiness pass now prevents most transition surprises.
If your team is evaluating how the v2 transition affects your Salesforce and HubSpot setup, Vantage Point can help assess the right next steps and build a practical migration plan.
Vantage Point works across both Salesforce and HubSpot, so we look at your sync as one connected system rather than two products bolted together. A typical engagement audits your current configuration, cleans and de-duplicates data, redesigns field mappings and sync rules for v2, and retires the brittle workarounds you no longer need.
That work runs through our HubSpot and Salesforce integration and system integration and data migration services, and we keep the integration healthy over time with managed services and ongoing support. Because our practice is dual-platform and vendor-neutral, we build to hand over with documentation and a named internal owner — not to create dependency. For deeper background, see our guides on connecting HubSpot and Salesforce the right way, how deduplication works across the two systems, and sync rules, directions, and field mappings.
It is a ground-up rebuild of the backend that syncs data between HubSpot and Salesforce — the first major overhaul of the native integration since 2014. v2 replaces the old workers, sync pipelines, and matching logic with a faster, more resilient platform that supports field-based deduplication, owner-field sync, and better error handling.
You don't trigger the migration yourself — HubSpot moves objects onto v2 in phases. What you should do is prepare: review your sync rules, deduplication logic, and field mappings, and clean up duplicates and picklist mismatches before each object migrates. That readiness work is where teams avoid surprises.
HubSpot has targeted a Q4 2026 beta for contact sync, with the legacy engine planned for deprecation by mid-2027. These dates come from HubSpot's announcement and can change, so confirm the current status in your own portal before making configuration changes.
v2 targets the connector's best-known limitations: deduplication that previously matched on email address only, the lack of native owner-field sync, picklist mismatches, and bulk operations that could exhaust shared Salesforce API limits and suspend the integration. It also aims to be more debuggable when issues arise.
It shouldn't break a well-configured integration, because HubSpot validates each object before migrating it. The bigger risk is configuration that quietly depended on old behavior — for example, email-only dedupe. Reviewing and testing your setup before each object moves is the safest approach.
Maybe, but revisit them. Many teams added external dedupe tools or owner-sync middleware specifically because the legacy engine couldn't do field-based matching or owner sync. With v2 offering both natively, some of those workarounds can be simplified or retired — but only after you confirm v2 covers your specific rules.
Yes. Any organization that runs HubSpot and Salesforce together — across any industry — relies on this sync layer for clean, shared data. The v2 improvements to deduplication, owner sync, and reliability are relevant wherever marketing and sales depend on the two systems agreeing.