View as Markdown

TL;DR

  • Restoring deleted records can reintroduce duplicates you already resolved.
  • Records merged away or deleted as duplicates come back next to the record you kept.
  • Backups restored in bulk are the biggest risk, because nobody checks each record.
  • Restore only what you need, and check it against existing records first.
  • Dedupely's undo brings merged-away records back as new records, so you choose which merges to reverse.

A team deletes a few hundred records by mistake and restores them from the recycle bin. Problem solved, until someone notices that dozens of the restored records are duplicates of contacts the team merged last month. Restoring is a way back, but it doesn't know about your cleanup.

How restores bring duplicates back

Restore What comes back
A recycle bin restore Records deleted as duplicates, next to the record you kept
Restoring records merged away The other half of a merge, as a separate record again
A full backup restored into the CRM Every record as it was, including duplicates since merged
A re-import of an old export Old records, without the IDs that would update existing ones

What CRMs do about it

Some CRMs block the obvious case. HubSpot keeps deleted records for 90 days, but its help says a deleted contact can't be restored if an active contact has the same primary or secondary email. Salesforce keeps deleted and merged-away records in the Recycle Bin for 15 days, and restoring a merged-away record doesn't change the master record. A different email, a changed name or a re-import gets past most of these checks.

How to restore safely

  1. Restore only what you need, filtered by date, user or the process that deleted them.
  2. Check the list against existing records on email, name and company before restoring.
  3. Leave out records you deleted as duplicates, using your merge or deletion log.
  4. Run a duplicate search right after the restore, on the restored records.
  5. For full backups, restore into a sandbox first and compare.

Undoing a merge is a restore too

Undoing a merge brings the merged-away records back. Decide which merges to reverse one at a time, rather than restoring everything from a period, so correct merges stay merged.

How Dedupely handles undo and restores

In Dedupely, most merges can be undone for 30 days from Merge History, one merge at a time. The undo re-creates the merged-away records with new IDs and moves their links back, and the records go to Rejected Matches, so they don't show up as duplicates again in your searches. For older merges, the Merge History CSV keeps the original values, so you can restore exactly the records you need. After a recycle bin or backup restore, a Duplicate Search shows which restored records match existing ones.

Find the duplicates a restore brought back

Restore what you need, not what you cleaned

Restores and undo bring records back without knowing which ones you resolved as duplicates. Restore selectively, check against existing records, keep a log of deleted duplicates and run a duplicate search after any large restore.

Frequently asked questions

Why did restoring deleted records create duplicates?

The restore brought back records you had deleted or merged as duplicates, next to the records you kept.

Does HubSpot stop restored contacts from duplicating?

It won't restore a contact if an active contact has the same primary or secondary email. Other differences get through.

How long can deleted records be restored?

HubSpot keeps them for 90 days; Salesforce's Recycle Bin keeps them for 15 days.

Is undoing a merge the same as restoring?

It brings the merged-away records back too, so reverse merges one at a time.

What should I do after a large restore?

Run a duplicate search on the restored records and merge or delete the ones you had resolved before.