Primary ID Preservation for Merged Records
Friday, August 21, 2026
What it is
When you merge two CRM records, HubSpot now preserves the primary record's ID as the surviving record ID. No new ID is generated. The secondary record's ID becomes a forward reference that resolves to the primary record ID.
Why it matters
Until now HubSpot minted a brand-new record ID on every merge. Integrations that cached or referenced record IDs broke silently, webhook consumers received an unexpected object-created event for what was conceptually the same record, and any team storing HubSpot IDs in an external system had to chase down the new canonical ID by hand.
The Take
Chris Carolan
It wasn't until just really like less than a month ago that I did a merge using Claude through the MCP and Claude actually was like, just a heads up. Now these records have different IDs. And I was like, I'm sorry, what?
Tagged a major update and it earns it. The striking thing on air was how many of us assumed this already worked. The record URL has always redirected to the survivor, so the new-ID behavior underneath stayed invisible until something depended on it.
Chris only found out recently, and found out from Claude: he ran a merge through the MCP and got told, as an aside, that these records now have different IDs. That is the whole problem in one sentence. Silent ID churn is the reason teams decided a HubSpot integration was too hard to maintain and never built one. Stable IDs across merges is table stakes in every other system, and it is good to see it land here.
Watch Us Discuss This
The full segment from the show, us working through this update start to finish.
Produced by Value-First Media