Stratus Cloud Solutions Stratus Docs
Documentation / Data Cleanser User Guide / Reviewing & Merging Duplicates

Rollback Merges

Rollback lets you reverse a Data Cleanser merge — recreate merged-away records from field snapshots captured at merge time, move related records and file links back, and revert master field values to their pre-merge state. It is available on the Pro + Rollback license.

Rollback uses field snapshots stored when the merge ran — not the Salesforce Recycle Bin. Loser records are recreated with new Salesforce IDs. You can roll back while snapshots are still within the retention window (default 90 days, maximum 150 days).

Open the Rollback queue

In the Review tab, open the object-type menu in the duplicate queue and choose Rollback. The queue lists completed Data Cleanser merges that can still be rolled back, with a count badge on the menu item even while you are viewing Accounts, Contacts, or Leads.

  • Search merges by master record name.
  • Sort by newest, oldest, master record, object type, or status.
  • Select one or more merges for bulk rollback.
  • Dismiss finished rollbacks from the list when you are done reviewing them.

Preview before you rollback

Click a merge to open the Rollback preview. The preview shows what will happen when you roll back:

  • Records split back apart — loser records recreated from captured field snapshots.
  • Field values after rollback — a field-by-field comparison table: each column is one record after rollback, each row is a field. Compare master and restored values side by side before you commit.
  • Related records & files move back — reparented children and file links return to their pre-merge owners.

If related records or files were permanently deleted after the merge, the preview lists them and warns you before you proceed. Rollback can still run — but those related rows and files are not restored. The merge may finish as Partially rolled back if some reparent steps could not complete.

If the snapshot retention period has passed or field snapshots are missing, rollback is blocked and the preview is shown for reference only.

Roll back a merge

1

Select a merge

Open a row in the Rollback queue, or tick checkboxes for several merges.

2

Review the preview

Confirm records, field reversions, and related-record moves. Watch for warnings about missing snapshots or permanently deleted files.

3

Confirm rollback

Click Rollback (or Rollback selected merges for bulk). The job queues in the background — refresh the list to see processing, completed, partial, or failed status.

4

Retry if needed

A partial rollback leaves restored records in place. Review row-level errors in the preview or under Settings → Warnings, then use Retry rollback to finish reparenting any related rows and files that can still be moved back.

Mass merges are eligible too — each group merged in a mass run appears as its own rollback event. See Multi-Select & Mass Merge.

Rollback settings

Open Settings → Rollback (Pro + Rollback license required) to configure Snapshot retention & purge (days) — how long merge snapshots stay available for rollback and how long completed, failed, or expired rollback events remain before automatic purge. Default is 90 days; maximum is 150 days.

Each merge freezes field values at merge time. Successful rollbacks are removed from the queue immediately. Expired merges that can no longer be acted on are purged automatically. See Settings Reference for the full Rollback panel.

When rollback is blocked
  • License — Rollback requires Pro + Rollback. Pro-only orgs see an upgrade prompt in the queue.
  • Snapshot expired — the retention period for this merge has passed.
  • Missing snapshots — loser field snapshots were not captured or are unavailable.
  • Survivor deleted — the master record must exist before rollback can start. Restore the survivor, then try again.
  • Already rolled back — the event shows as done; dismiss it from the list when finished.
Missing related records and files (partial rollback)

Missing captured related records or files does not block rollback entirely. The preview calls out what cannot be restored — for example, "Deleted related records will NOT be restored" — and you can still confirm the rollback.

  • Related records deleted after the merge — rollback restores the merged records and reparents everything it can. Rows that were permanently deleted stay missing; the event may show Partially rolled back.
  • Files permanently deleted — file links move back only when the underlying files still exist. Deleted files are listed in the preview warning and are not recovered.
  • After a partial result — review the preview or Settings → Warnings, then use Retry rollback if remaining related rows can still be reparented.
Warnings and failed rollbacks

Failures, partial completions, and row-level errors also appear under Settings → Warnings. A failed rollback stops before finishing; a partial rollback completes what it can and flags what was skipped.

What rollback restores
Loser records
Recreated from field snapshots captured at merge time, each with a new Salesforce ID.
Master field values
Reverted to the pre-merge snapshot captured at merge time.
Related records
Reparented back to the record that owned them before the merge. Rows that were permanently deleted after the merge cannot be restored — rollback completes partially and warns you in the preview.
File links
Salesforce Files links moved back when the files still exist.