Can you undo a merge in a CRM?

In most CRMs, you can't undo a merge, and even where you can, it's best to treat every merge as permanent. Once two records become one, most CRMs have no button that splits them back into the originals.

That's why merging feels risky to so many admins. A wrong merge can join two different people, keep the wrong owner or overwrite a value someone needed. Some CRMs give you a little room afterward, and others give you none.

In this post, you'll see what HubSpot, Salesforce, Pipedrive, Close, Nimble and Google Contacts allow after a merge. You'll also see how to recover from a merge that went wrong and how to keep it from happening in the first place.

What each CRM allows after a merge

Here's what each vendor's help pages say, as of October 2026.

HubSpot

HubSpot's help page on merging records says it's not possible to unmerge records. You can trace a merge through the "Merged [record] IDs" property, which keeps the original IDs.

By default, the merged record also gets a new Record ID, and both records are removed from their active workflows. Accounts in HubSpot's Primary ID Preservation beta keep the primary record's ID instead.

Salesforce

When you merge accounts in Salesforce, the records that aren't kept are moved to the Recycle Bin, according to its merge considerations page. Its Recycle Bin page says deleted items stay there for 15 days and can be restored during that time.

Neither page describes an unmerge. Restoring a record brings it back, so check its values and related records before you rely on it.

Pipedrive

Pipedrive's merge duplicates article says merged items can't be un-merged. Its merge flow has a Preview step before you confirm, which is the moment to check.

Close and Nimble

Neither help page on merging describes a way to undo it. In Close, one lead is kept as the winner and the other is absorbed into it. In Nimble, you choose which data remains before the merge, which is the moment to check.

Google Contacts

Google Contacts gives more room. Its help page on merging says you can separate a contact you merged. Its page on editing and deleting contacts says you can undo all changes from the past 30 days at once. Deleted contacts stay in Trash for 30 days.

Undoing changes rolls back every contact to the time you choose, so contacts added after that point won't appear.

Why a merge is hard to reverse

A merge changes more than one record. When two records become one, a few things happen at once:

• Values are overwritten. Where two records disagree, one value wins and the other is gone from the record.
• Related records move. Activities, deals and associations from both records end up on the one that's kept.
• IDs can change. In some CRMs, the merged record gets a new ID, and other systems may still point to the old one.
• Automations react. Workflows, triggers and syncs can run on the merged record.

Splitting the record later means putting every one of those back by hand. That's why the original values matter so much: they're the only full picture of what each record looked like before.

Merges made by a deduplication tool happen in your CRM too. Some tools give you a way back, but undoing a merge still means bringing records back into your CRM. Those records then need the same checks as any other change, which is why it pays to plan each merge as if it's permanent.

How to recover from a wrong merge

When a merge goes wrong and there's no undo, recovery means rebuilding the original records from saved values. The order matters.

Stop any merges still running

If a bulk merge or an automatic merge is running, stop it first. Otherwise the same mistake keeps repeating while you look into it.

Find out what was merged

List the merges from the time of the problem. For each one, you need the original records and the values that won.

Decide how to fix each merge

The fix depends on what went wrong:

• The records were duplicates, but the wrong values won. Restore the right values on the kept record. There's no need to split anything.
• The records weren't duplicates. Re-create the record that shouldn't have been merged, with its original values, and move its activities and associations back where your CRM allows it.
• A whole batch used the wrong criteria. Restore record by record, starting with your most important accounts.

Restore from your saved values

For many records, import the corrected values with the record IDs, so the CRM updates existing records instead of creating new ones. Our playbook on what to do if you merged the wrong records goes through each step.

Keep the same merge from happening again

A re-created record can match the same record on the next search. Reject that match so it stays out of future merges, and tighten the criteria that paired them.

How to avoid merges you'd want to undo

Since it's best to treat every merge as permanent, the safest fix is the one you never need. A few habits cover most of the risk.

• Preview before you merge. Check the merged record's owner, email, stage and any field that matters to your team.
• Test on sets you know, then start small. A good search finds your known duplicates and leaves known non-duplicates alone. Merge a few sets and open them in the CRM before larger batches.
• Review the unclear sets. Send matches you aren't sure about to a person instead of merging them in bulk.
• Hold back risky matches. Large groups and placeholder values, like test@test.com, often pair records that aren't duplicates.
• Keep the original values. A record of every merge, or a backup before a large merge, gives you something to restore from.

Why a record of each merge matters well beyond recovery is covered in why you need a record of every merge.

Plan merges as if they're permanent

In most CRMs, a merge can't be taken back. Salesforce's Recycle Bin and Google Contacts' undo options give you some room, while HubSpot and Pipedrive treat merges as permanent.

Even where an undo exists, in a CRM or in a tool, it means bringing records back into your CRM and checking them again. So the safety comes before and after the merge. Preview and test before you merge, and keep the original values of every merge. If something still goes wrong, those values are what you rebuild from.

Frequently asked questions