What This Update Actually Is
HubSpot shipped a new "Rules" tab inside Data Quality. From there, you can create a Duplicate Merge Rule that tells HubSpot exactly how to pick the winning record in any duplicate group.
The logic is sequential and waterfall-based. You stack up to five conditions. HubSpot evaluates the first condition. If one record wins, done. If it's still a tie, it moves to condition two, then three, and so on. At the end of all your conditions, you set a tiebreaker (like "most recent engagement") to resolve any remaining standoffs.
An upcoming addition will also let you set property overrides, so values from the secondary record can overwrite the winner's properties on specific fields. That piece isn't live yet, but it's baked into the same rule-building framework.
Why HubSpot Shipped This
Duplicate records are one of the most common sources of distrust in a CRM. We see it constantly across portals: two contacts for the same human, and nobody is sure which one to keep because neither is clearly "better" by HubSpot's old simple criteria.
The old options were limited. You could manually pick a winner, or lean on blunt rules like "created first" or "most recent engagement." That's fine for a handful of records. It breaks down when you're managing thousands of duplicates and you need the winner to reflect actual business logic, like preferring the contact with a specific lifecycle stage, a verified email domain, or a populated company association.
The internal frustration is real. RevOps humans have been forced to choose between bad options: accept bad merges, do it manually one by one, or build fragile workarounds outside of HubSpot. This update gives them a native, repeatable alternative.
HubSpot also flagged this as the foundation for future automated bulk merging. Right now, Merge Rules inform manual review. Down the road, they'll power automated deduplication at scale. Getting your rules defined now means you're ready when that capability arrives.
How to Use It Step by Step
- Navigate to Data Quality in your HubSpot portal. You'll see a new "Rules" tab in the top navigation.
- Click "Create rule" and select "Duplicate Merge Rule" from the options.
- Name your rule. Be specific. Something like "Contact Winner: Email + Lifecycle Stage" will save you confusion later when you have multiple rules.
- Select the object this rule applies to: contacts, companies, deals, or another supported object.
- Add your winning record conditions in order of priority. Each condition evaluates a property. The record that satisfies it best moves forward as the candidate winner.
- Stack up to five conditions in the waterfall. Order matters. Put your most important business criteria at the top.
- Set your tiebreaker. This is the final fallback if all conditions result in a draw. "Most recent engagement" is HubSpot's default option here.
- Save your rule. When you're reviewing duplicates, use the "Merged by" dropdown to invoke this rule and let it select the winner automatically.
What It Touches in Your HubSpot Strategy
This update lives inside Data Hub, but its ripple effect touches every hub you use. Here's where it actually matters.
CRM data integrity is the foundation everything else runs on. Bad merges corrupt lifecycle stage reporting, break workflow enrollment, and send sales reps chasing dead records. When Merge Rules ensure the right record survives, your contact and company data is more trustworthy from the start.
Key Takeaway
Merge Rules don't just clean up duplicates. They protect the data your automations, reports, and AI tools depend on. A bad merge today becomes a broken workflow or a skewed attribution report tomorrow.
Workflows and automations are directly affected. If a duplicate merge picks the wrong record as the winner, contacts can fall out of active sequences, lose their enrollment history, or get re-enrolled when they shouldn't. Consistent Merge Rules prevent that.
Reporting and attribution also take a hit from messy merges. When the wrong record wins, deal associations, form submissions, and engagement history can get split or lost. Correct merges keep your revenue attribution clean.
If you've been expanding your CRM property set, for example after the owner property limit increase to 250, your winning record logic may need to account for those new properties. More properties in your CRM means more opportunity to build smarter, more specific merge conditions.
For teams running a bi-directional sync with Salesforce, this matters even more. Duplicate contacts synced from an external system are a known headache. If you're planning ahead for HubSpot's Salesforce integration rebuild, getting your Merge Rules defined now means your deduplication logic is ready before records flow across systems at scale.
Key Takeaway
Build one Merge Rule per object type and name them clearly. When automated bulk merging becomes available, your rules will carry forward automatically. Don't wait until that feature ships to define your logic.
Who Should Care Most
This update is squarely for Data Hub Professional and Enterprise portals. Within that group, a few specific roles will feel the biggest impact.
- RevOps leaders who manage large contact or company databases and need to run bulk deduplication without manually reviewing every single match.
- HubSpot admins at companies with multiple data sources (forms, imports, integrations, third-party enrichment tools) where duplicates are an inevitable, ongoing problem rather than a one-time cleanup.
- Marketing operations humans who need lifecycle stage data to be accurate before running segmented campaigns or feeding contacts into automated nurture sequences.
- Sales leaders who've seen reps waste time on duplicate outreach or lose deal context because the wrong record was merged as the winner.
- Companies preparing for a CRM migration or data enrichment project where clean, consistent merge logic needs to be in place before records are touched in bulk.
George's Take
I've sat inside hundreds of HubSpot portals over the years, and duplicate records are almost always in the top three issues holding a company back from trusting their data. The old approach forced humans to either accept imprecise automated merges or drown in manual review. Merge Rules change that calculus completely. You define the business logic once, in a format that matches how you actually think about record quality, and then it applies consistently every single time. What excites me most isn't even the current feature. It's that this is clearly the foundation HubSpot is building toward automated bulk merging. Getting your rules defined now isn't just good hygiene. It's positioning.
“You define the business logic once, and it applies consistently every single time. That's how you get a CRM your whole team actually trusts.”
Data quality updates like this one often travel in groups. If you're auditing your portal right now, it's also worth checking how HubSpot's locale data upgrade from JRE to CLDR might affect how dates and values display on the records you're keeping after a merge.
If your portal is on Data Hub Professional or Enterprise and you want help building Merge Rules that reflect your actual business logic, not just HubSpot's defaults, let's talk. Book a strategy call with the Sidekick team and we'll map out your deduplication logic together.
Frequently Asked Questions
What are HubSpot Merge Rules?
HubSpot Merge Rules are configurable rules inside Data Quality that let you define which record wins when duplicates are merged. You stack up to five property-based conditions in waterfall order, plus a tiebreaker. They're available on Data Hub Professional and Enterprise and apply to contacts, companies, deals, and other supported objects.
How is a winning record chosen in HubSpot Merge Rules?
HubSpot evaluates your conditions in order. It checks the first condition and sees if one record clearly wins. If there's still a tie, it moves to the second condition, then the third, up to five total. After all conditions run, a tiebreaker (like most recent engagement) resolves any remaining ties.
Who can use HubSpot Merge Rules?
Merge Rules are available to HubSpot customers on Data Hub Professional and Data Hub Enterprise. They're not available on free, Starter, or non-Data Hub plans. If you're unsure which tier your portal is on, check Settings > Account > Account Details.
Can Merge Rules run automatically without manual review?
Not yet. As of August 2026, Merge Rules are invoked manually during duplicate review using the "Merged by" dropdown. HubSpot has confirmed that automated bulk merging is planned as a future capability that will use these same rules, so defining your logic now prepares you for that feature.
What's the difference between a winning record condition and a property override?
A winning record condition determines which duplicate becomes the primary record that survives the merge. A property override (coming soon) lets specific property values from the secondary record overwrite the winner's values on chosen fields. Both are set within the same Duplicate Merge Rule builder in Data Quality.
Where do I find Merge Rules in HubSpot?
Go to Data Quality in your HubSpot portal and look for the new Rules tab in the top navigation. Click Create Rule, then select Duplicate Merge Rule. From there you'll name the rule, choose the object it applies to, set your waterfall conditions, and define a tiebreaker.
