HubSpot Duplicate Cleanup Gone Wrong: How to Recover From a Bad Bulk Merge

Bulk dedup tools are good tools, and most disasters trace back to a loose match rule, not the software. Move fast: stop the job, export your merge history while HubSpot's 90-day window is open, save the tool's own merge report, then run a free bulk scan to measure the damage before deciding how to recover.

Last updated: July 2, 2026

Whose fault is a bad bulk merge, the tool's or the configuration's?

Usually the configuration. HubSpot's native duplicate manager, Insycle, Dedupely, and Koalify are all capable, widely used tools. Trouble starts when match rules are looser than the data deserves, for example matching companies on name alone or contacts on shared office emails, so the tool faithfully merges pairs that were never duplicates.

For reference, HubSpot's own duplicate management tool identifies potential duplicates by comparing property values such as First Name, Last Name, and Email address for contacts, and Company Domain Name and Company Name for companies. Managing individual duplicates with it requires a Professional or Enterprise subscription. Third-party tools let you build much more aggressive rules, which is exactly why a misconfigured run can do more damage faster.

Can your dedup tool revert the merges it made?

Only partially, and only in some cases. HubSpot itself states it is not possible to unmerge records. Insycle documents a revert workaround in its support center, and its own article notes real limits, including that reverting is not compatible with contact records in its synthetic merge mode and merged activities cannot be removed.

The baseline is HubSpot's merge documentation: "It's not possible to unmerge records." Whatever a tool offers on top of that works within the same API limits.

To Insycle's credit, it documents its own limits openly. Its support article, "Revert Merge Operation on HubSpot Records", describes a workaround that requires the merge operation's CSV report, notes that its Synthetic merge revert method is "not compatible with contact records", states that activities merged into the master record "cannot be removed", and calls for manual cleanup of additional emails, domains, and associations afterward. That is honest vendor documentation of what HubSpot's platform allows, not a flaw unique to Insycle.

If you used a different tool, check its documentation for what its undo actually covers before assuming the merges are reversible. For a side-by-side look at what a revert restores versus a full reconstruction, see Insycle Revert vs Emergency Unmerge.

What should you do in the first hour?

Stop the merge job before anything else, then preserve evidence. Export HubSpot's merge history from the duplicate management tool, since it only reaches back 90 days, and download your dedup tool's own merge report. Then run the free bulk scan on up to 10,000 records to see exactly what was merged.

1

Stop the job

Pause the dedup run, scheduled automations, and any workflow or recipe that feeds it. Every additional merge stacks damage on records you will later need to reconstruct, and chain merges (records merged more than once) are the most expensive kind to recover.

2

Export HubSpot's merge history today

Go to Data Management > Data Quality > Manage Duplicates > Actions > Export merge history. Per the HubSpot documentation, the export reaches back up to 90 days and contains the records' property values prior to the merge plus the merge timestamps. That pre-merge snapshot is recovery gold, and the window is closing daily. One catch: the option only covers merges performed in the Data Quality tool, so merges run by a third-party tool will not appear there.

3

Save your tool's own merge report

If the cleanup ran through Insycle, Dedupely, Koalify, or another tool, download that tool's merge or operation report now. It is your record of which pairs were merged, and Insycle's documented revert workaround requires its merge CSV report, so losing it closes doors.

4

Roll back property damage where HubSpot can

If the cleanup also overwrote property values through imports, workflows, or manual edits, HubSpot's Restore CRM changes can roll records back to a previous point within the last 14 days. It is available on Starter and above and needs Super Admin permissions. It is not documented to reverse merges, so use it for the property side of the mess only.

5

Measure the damage with the Free Bulk Scan

Run a free merge audit on up to 10,000 contact or company records per job. Upload HubSpot's merge history export CSV, any CSV with a Record ID column, or pick a HubSpot list directly. For every record you get merge detected yes or no, complexity classification, and the estimated credit cost, in a downloadable CSV report. It is free and read-only, so it makes no changes to your CRM.

Should you fix it yourself or bring in help?

Scale decides. A handful of bad merges is comfortable self-serve territory: scan each record free, reconstruct, review the confidence scores, and execute, at about five minutes per record. Once the scan shows roughly 100 or more affected records, bulk recovery runs as a guided engagement so rebuild order and re-association stay safe.

Self-serve: Emergency Unmerge reconstructs HubSpot contacts, companies, and deals one record at a time, with per-field confidence scores you review before anything executes. Fine print worth knowing up front: unmerging creates new records with new Record IDs (a HubSpot API limitation) and results are probabilistic, with simple merges typically achieving 90%+ confidence. See How It Works, the setup guide, and pricing (no subscription, starting at $4.99).

Guided Bulk Recovery: the bulk unmerge itself is not a one-click button. The team works through the rebuild and re-association with you so the ordering is correct and every association is safely restored. Complete the Free Bulk Scan first and have the report ready, then request a free consultation. Response is typically within 24 hours.

Prevent the next cleanup from needing this page

Before the next bulk run, snapshot the records you are about to merge: Pre-Merge Backup captures every property and association on both records, in bulk via CSV or a HubSpot list, so a wrong merge restores for free with 100% accuracy. For ongoing protection, CRM Data Backup & Restore by Third Space backs up HubSpot contacts, companies, and deals with one-click restore. Free up to 2,000 records.

Frequently Asked Questions

Does HubSpot's merge history export cover merges made by third-party tools?

No. HubSpot's documentation says the option to export merge history only appears for merges that happened in the Data Quality tool, and the export reaches back up to 90 days. For merges run through an outside dedup tool, your evidence is that tool's own merge report, so download it immediately.

What does the Free Bulk Scan actually check?

It scans up to 10,000 contact or company records per job from a CSV upload or a HubSpot list. For each record it reports whether a merge was detected, how complex it is, and the estimated credit cost to unmerge, then gives you a downloadable CSV report. It is free and never modifies your CRM.

Can Emergency Unmerge undo thousands of bad merges automatically?

Not as a one-click button. Reconstruction is self-serve per record, and bulk jobs run as a guided recovery: after your free scan, the team works through the rebuild and re-association with you so the ordering is correct. Start by completing the scan, then request a free consultation through the support page.

Can HubSpot's Restore CRM changes undo a bad bulk merge?

It is not documented to reverse merges. Restore CRM changes rolls records back to a previous point within the last 14 days, undoing updates made by workflows, imports, or manual edits. Use it for property damage from the cleanup, and treat the merges themselves as a separate recovery problem.

Will the recovered records keep their original Record IDs?

No. Due to HubSpot API limitations, unmerging creates new records with new Record IDs rather than restoring the originals. Original values, including the pre-merge create date and Record ID, are preserved in a dedicated Emergency Unmerge property group, and every reconstruction is reviewed field by field before anything executes.

Related reading