A sales rep messages you on Monday morning: the account history for one of their biggest customers has disappeared. You open the record and find it isn't gone. It's sitting inside another company, merged over the weekend by a duplicate rule that matched on a shared domain. Then you check the workflow history and realise it didn't happen once. It happened 400 times.
Your next search is probably "how do I undo a merge in HubSpot?" The honest answer is short: natively, you can't.
This post covers what HubSpot does and doesn't let you recover, why bad merges happen even in well-run portals, and how to reverse them (one at a time or in bulk) when the merge was done with Koalify.
Quick answer: HubSpot has no native unmerge feature. Once two records are merged, HubSpot can't separate them again. If the merge was done through Koalify, you can reverse it: a single record from its timeline event, or hundreds at once by enrolling the affected merges in an unmerge workflow.
HubSpot's own knowledge base is clear on this: once you've merged two records, it isn't possible to unmerge them. There's no undo button, no recycle bin for the record that was merged away, and HubSpot support can't reverse it for you.
Here's what a merge does in HubSpot:
Unmerging has been one of the most requested features in the HubSpot Community for years. HubSpot has said it's on the roadmap, but without a timeline.
Until then, the native workaround is entirely manual: create a new record, copy the old values back in from property history, and re-associate the right contacts, deals and activities one by one. That's manageable for one bad merge. It isn't manageable for 400.
Our customers merge thousands of duplicates, often through workflows that run in the background without anyone watching. At that volume, a small error rate still adds up. If 0.5% of 10,000 merges are wrong, that's 50 records someone has to untangle.
The usual causes are rarely dramatic:
One HubSpot partner we work with found merge chains 250, 198 and 136 records deep in a client portal, all caused by loose domain-based rules running unchecked. A salesperson only noticed when historical data appeared to have vanished.
Bad merges are a normal cost of automating deduplication. What matters is whether you can reverse them. For a lot of teams, the fear of a merge they can't undo is the main reason they keep merging by hand, long after the backlog has outgrown manual work.
HubSpot can't unmerge because it doesn't keep a clean snapshot of each record as it was before the merge. Koalify does.
Every merge Koalify makes is logged in two places inside HubSpot:
That snapshot is what lets Koalify rebuild the record that was merged away.
A few honest limits before you rely on it:
Use this when you spot one wrong merge, for example after a hurried click on a duplicate card.
When a workflow or rule has merged the wrong records in bulk, you reverse them in bulk too. Every Koalify Merge record can be enrolled in a workflow, so you filter down to the bad merges and undo them in one go.
The whole process stays inside HubSpot. There's no export, no spreadsheet and no separate tool to log into.
Unmerging fixes the records. These checks stop the problem coming back:
Being able to undo a merge doesn't mean you should skip the careful steps. Test new rules on a small segment, review the first batch of merges by hand, and keep a backup before large bulk runs.
What unmerge changes is the risk of switching automation on. One customer told us he'd been "scared to just start merging". After seeing an unmerge in action, he moved straight to bulk merging his backlog. That's the point: deduplication that runs in the background, with rules you control and a way back if a rule gets it wrong.
Not natively. HubSpot doesn't offer an unmerge feature, and merged records can't be separated again through HubSpot itself. The only native option is rebuilding the record by hand from property history. If the merge was done with Koalify, you can unmerge it from the record's timeline or in bulk with a workflow.
No. Koalify can only unmerge merges it made itself, because unmerging relies on the snapshot of both records that Koalify logs at the moment of the merge. Merges done in HubSpot's own tool, or before Koalify was installed, have no snapshot to restore from.
No. The record that was merged away is recreated with a new HubSpot record ID. Koalify stores that new ID as the Restored Record ID on the Koalify Merge record, so you can trace it.
Contacts and companies.
Go to CRM > Koalify Merges and filter by merge source, workflow ID, merge date or duplicate rule. Every merge Koalify makes is listed there, along with the property values of both records before the merge.
Only if the rule or workflow that merged them is still active. Turn it off or fix the rule before you unmerge. For single unmerges, you can also mark the pair as non-duplicates so Koalify won't flag them again.
Clearing a 50,000-record backlog is far easier when you know a bad rule isn't permanent. Install Koalify free and run your first bulk cleanup with unmerge as your safety net.