Blog

For the B2B, B2C and nonprofit teams we work with at Revunami, the HubSpot-Salesforce integration has been a low-grade tax on RevOps for years. Duplicate contacts. Owner fields that won’t sync. Company merges that silently break. The kinds of issues that don’t bring the business down but quietly eat hours every week.

That’s why we are excited to see that HubSpot is rebuilding the integration from the ground up. The architecture between the two most-used CRMs in the world was last refactored in 2014, and HubSpot has spent the last year quietly migrating it onto a new platform they call v2.

Getting onto v2, however, is its own project. Done in the wrong order, it creates more sync errors than it fixes. We’ve been waiting for this update for years, and we’ve built the migration playbook for it. 

What v2 actually fixes

Most of the long-standing complaints go away with v2:

• Deduplication on any field, not just email. Job-changers, role-based addresses, and Salesforce’s separate Lead and Contact objects stop creating duplicate records.
• Native owner field sync, so territory changes and reorgs stop quietly drifting between systems.
• Unique ID matching, which is what messy real-world data has always needed: duplicate emails, shared inboxes, household records on the nonprofit side.
• Inclusion lists on every object, not just contacts.
• Company merges that actually sync. Merge a company in Salesforce, and the merge now reflects in HubSpot. This alone justifies the upgrade for most of the portals we audit.

Timeline

Custom objects, tickets, and activities are already on v2. Companies launched last month. Deals ship in the coming weeks. Contacts hit beta in Q4 2026, and the legacy engine will be fully deprecated by mid-2027.

Where it goes wrong

A one-click upgrade button exists in your integration settings. That button is also how teams break their CRM.

Every customer who has been running this integration for more than a year has built workarounds: custom dedupe scripts, owner-sync middleware, iPaaS connections compensating for picklist mismatches, workflows wired around Lead-to-Contact conversion edge cases. v2 makes a lot of that infrastructure unnecessary, but it doesn’t tell you which pieces to retire and which to keep. Flip the switch in the wrong order and you get duplicate records flowing in two directions, owners reverting overnight, and a support queue that takes weeks to clear.

Contact sync is the one to be especially careful with. Contacts are the highest-volume, most-interdependent object in your CRM, with the deepest ties to lifecycle stage logic, marketing email status, and subscription management. Being an early adopter on the contact rewrite is not where you want to be.

How we handle it

Our work usually starts with an audit of your current sync and an inventory of every workaround in your stack so we know what v2 retires. From there, we sequence the object upgrades, validate each one in a sandbox before production touches it, and monitor the cutovers. We also handle the duplicate-record cleanup that’s been waiting on company merges to work.

For B2B SaaS clients with complex lead-to-account routing, we make sure territory hierarchies survive the sync rewrite. For B2C brands, we keep commerce, loyalty, and service data flowing cleanly into the sales motion. For nonprofits, we protect donor and constituent histories that can’t be rebuilt if a sync goes sideways.

Your team doesn’t need to become experts. We already are.

If you’re running this integration and you don’t want to spend 2026 and 2027 putting out fires, let’s talk.