What This Update Actually Is
Right now, merging two duplicate records in HubSpot unenrolls both records from any active workflows. That includes the record you chose to keep. It doesn't matter that it's your primary. It still gets dropped.
After August 18, 2026, that behavior changes. The primary record stays exactly where it was in every active workflow. Its position is preserved: delays, branches, and queued actions all continue as if the merge never happened. The duplicate being merged away gets unenrolled. That part stays the same.
This applies across all CRM object types that support merging: contacts, companies, deals, tickets, and custom objects. HubSpot is rolling it out automatically. You don't flip a switch.
Why HubSpot Shipped This
Duplicate records are one of the most common friction points we see in live portals. Humans run imports, fill out forms twice, or get entered by two different reps. The data mess is normal. What shouldn't be normal is punishing your team for cleaning it up.
The old behavior created a real trade-off. Merge now and interrupt active nurturing sequences, onboarding flows, or deal-stage workflows. Or leave the duplicate alone and accept dirty data. Neither option was good.
The internal frustration was real too. Operations and RevOps humans knew the merge would break something downstream. So they'd delay the cleanup, build workarounds, or re-enroll records manually after the fact. That's wasted time and an avoidable source of automation gaps.
How to Use It Step by Step
There's no configuration needed. But here's the full picture of what the experience looks like after August 18:
- Find your duplicate records the same way you do today, either through HubSpot's duplicate management tool or manually.
- Select which record to keep as the primary and which to merge away. The primary is the record whose workflow enrollments will be preserved.
- Confirm the merge. HubSpot unenrolls the duplicate from its workflows and leaves the primary exactly where it was.
- Check the primary record's workflow history if you want to confirm continuity. You'll see no interruption in enrollment or timing.
- Resume your normal data hygiene cadence without building manual re-enrollment workarounds.
One caveat worth naming: the duplicate's workflow position is lost. If the record being merged away was further along in a nurture sequence than the primary, that progress doesn't carry over. HubSpot keeps the primary's position, not the most advanced position between the two. Choose your primary carefully.
What It Touches in Your HubSpot Strategy
This update is deceptively small. The ripple effects are real.
Key Takeaway
Any workflow that touches contacts, companies, deals, tickets, or custom objects is now safe to run alongside a deduplication effort. That means onboarding sequences, lead nurturing, deal-stage automation, and renewal flows no longer need to pause while your ops team cleans data.
Marketing Hub: Nurture Sequences Stay Intact
Lead nurturing workflows are the most common casualty of the old behavior. A contact mid-sequence gets merged, drops out, never receives the follow-up email, and falls cold. With this fix, your nurture logic runs clean even on a cleanup day.
Sales Hub: Deal-Stage Workflows Don't Stall
Duplicate deals are common when reps create records manually and an integration also creates one. Merging those used to stall deal-stage automations. Now the primary deal keeps moving. Task creation, internal notifications, and pipeline triggers stay on schedule.
Service Hub: Onboarding and Ticket Flows Hold Their Place
Customer onboarding workflows tied to contacts or tickets are sensitive to interruption. A merge during the first 30 days of onboarding could break a carefully timed sequence. That risk is now gone for the primary record.
RevOps: Deduplication Cadences Can Scale Up
If your team has been holding back on bulk deduplication because of automation risk, that constraint is lifting. You can now build or run deduplication workflows more aggressively without auditing every active enrollment first.
This pairs naturally with HubSpot's recent data integrity work. If you've already been using the single property revert feature to fix data mistakes fast, you're building a cleaner CRM foundation overall.
If you're also syncing records from Salesforce, this update becomes even more important. Merge conflicts between synced and native records are common, and keeping workflows intact on the HubSpot side reduces downstream sync confusion. See how selective sync for Salesforce objects fits into that cleanup strategy.
Key Takeaway
The biggest strategic shift here is that data hygiene and automation reliability are no longer in tension. Clean data and running workflows can coexist. That's a meaningful unlock for any RevOps or marketing ops team managing a high-volume portal.
Who Should Care Most
This update matters most to the following humans and scenarios:
- RevOps and marketing ops professionals who manage deduplication across large contact or deal databases and have been throttling cleanup to protect active automations.
- Marketing teams running time-sensitive nurture sequences where a dropped enrollment means a missed touchpoint and a colder lead.
- Sales ops teams managing deal-stage workflows where automation drives task creation, notifications, and stage progression.
- Growing companies where duplicate records accumulate fast due to multiple lead sources, integrations, or manual data entry, and the CRM cleanup backlog keeps growing because the automation risk feels too high.
- Service teams running customer onboarding workflows tied to contacts or tickets, where a mid-flow interruption damages the customer experience.
If your portal has fewer than 5,000 contacts and a simple workflow structure, this update is still a quality-of-life improvement. If your portal has 50,000+ records and a dozen active workflows, this is genuinely significant.
George's Take
I've audited portals where the deduplication backlog was in the thousands, and every time I ask why it hasn't been addressed, the answer is some version of "we don't want to break our automations." That's not laziness. That's a rational response to a broken system behavior. HubSpot just fixed the behavior. So now the question for every team sitting on a cleanup backlog is simple: what are you waiting for? Schedule the deduplication sprint, protect your primary records carefully, and let your workflows run.
“Clean data and healthy automations shouldn't be a trade-off. When your CRM tools force you to choose between the two, the tools are wrong. This update fixes that.”
If you're thinking about how your CRM data quality affects the full buyer experience, the deeper context lives in our guide to building a B2B customer journey that actually guides buyers. Automation integrity is a foundation piece, not a detail.
If your portal has a deduplication backlog you've been afraid to touch, or if your workflows have gaps you can't fully explain, let's look at it together. A Sidekick portal audit surfaces exactly these kinds of automation and data health issues before they compound. Book a strategy call and we'll show you what's actually happening in your HubSpot.
Frequently Asked Questions
Will HubSpot automatically keep my contact enrolled in workflows after a merge?
Yes, starting August 18, 2026, the primary record you choose to keep will stay enrolled in any active workflows. Its position, including pending delays and branches, continues without interruption. Only the record being merged away is unenrolled. No settings change is needed. This applies to all Pro and Enterprise tiers.
What happens to the workflow enrollment of the record being merged away?
The duplicate record being merged away is unenrolled from all its active workflows as part of the merge. That enrollment is not transferred to the primary record. Only the primary record's existing workflow position is preserved. If the duplicate was further along in a sequence, that progress is lost.
Does this update apply to deal and company workflows, or only contacts?
It applies to all CRM object types that support merging in HubSpot: contacts, companies, deals, tickets, and custom objects. Any active workflows tied to those object types will preserve enrollment on the primary record after a merge, across Marketing, Sales, Service, Data Hub, and Smart CRM Pro and Enterprise.
Do I need to re-enroll records that were dropped from workflows during past merges?
This update only affects merges performed after August 18, 2026. Records already unenrolled due to past merges won't be automatically re-enrolled. You'll need to manually re-enroll those contacts or use a workflow with re-enrollment criteria if you want them back in specific sequences.
How do I choose which record to make the primary when merging?
Choose the primary based on which record has the most accurate data and which is currently enrolled in the workflows you want to continue. Since only the primary's workflow position is preserved after August 18, picking the right primary is more important than ever. Review active workflow enrollments on both records before merging.
Will this change affect bulk deduplication or only manual merges?
HubSpot's announcement covers the standard merge behavior across the CRM. Whether you merge manually record by record or through HubSpot's duplicate management tool, the primary record's workflow enrollments are preserved. If you use third-party deduplication tools via API, check with your vendor on how they handle the primary record designation.
