Merge Rules | Winning Record Rules
Thursday, August 6, 2026
What it is
Lets admins set rules to automatically determine which record becomes the winning one when merging duplicates, with future support for property-override rules.
Why it matters
Gives teams more precise, rule-based control over duplicate merges instead of relying on manual choices, increasing confidence in bulk merges.
The Take
Casey Hawkins
A record is only winning until you need a value from the other one to override it.
Dedupe tools have done this for years. Insycle, Dedupely and Qualify all let you write a real rule: if the record is associated with a deal, that one survives. If it is the one with the Salesforce account tied to it, that one survives. HubSpot has not had that. The criteria it did offer, created first or most recent engagement, are not what anyone actually merges on.
The property override piece is the part worth waiting for. Choosing a winning record is only half the problem. The other half is keeping the one good field that lives on the record you are about to lose.
One caution on rollout, and this came out of a conversation with Trisha before we went live. Be careful how you train your teams on the word winning. A record is only winning until you need a value from the other one to override it, and then the label stops describing what is actually happening. If you are going to use the word, define it clearly everywhere you use it.
Watch Us Discuss This
The full segment from the show, us working through this update start to finish.
Produced by Value-First Media