Sluice, by GTM Cloud · Clean · Early access

Merge duplicates in Salesforce, and take the merge back if you need to

Sluice builds on the duplicate rules your org already has, lists every duplicate group for review, and takes a backup before each merge or sync, so you can undo from History.

You know this one

A rep calls a contact who was told last week, by a different rep, that the renewal was handled. Two accounts, same company. One holds the opportunity history. The other has the contacts and the open case.

You know the fix: pick one, merge, done. Your cursor goes to the button and stays there, because a merge is a one-way door. Whose phone number wins? Where do the related records end up? Nobody can tell you, and nobody can take it back.

So the ticket stays open, and the duplicates stay where they are.

How to merge duplicates in Salesforce and keep an undo

A sluice is a channel that separates what you want from the gravel. Sluice does the same for your records.

It builds on your org’s own duplicate rules and adds scored Match Rules for any object, with a preview before they go live. Every duplicate group lands in one list. You open one, compare the records side by side, pick the survivor, and read the Result After Merge column before you commit.

Before each merge or sync, Sluice takes a backup. If it was the wrong call, you undo it from History.

See it first. Take it back. Keep the receipt.

PreviewUndoProve
Side-by-side review with a Result After Merge column before you commit.Merges and syncs are backed up first and can be undone from History.A history of who merged, synced, converted or dismissed what.

What you get

Merges you can look at before you press the button

Review each group side by side, pick the record to keep, and see the result before you commit. Related records are counted per candidate.

A backup before every merge and sync

Each one is backed up first and can be undone from History.

The matching you already trust

Rules listen to your org’s duplicate rules, so nothing is replaced. Match Rules add scoring on any object, with a preview.

Warnings when a record is saved

Choose how firm each warning is: stop the save, ask once, or save and flag the record for review.

Leads converted into the Contact they match

When a Lead matches an existing Contact, convert it into that Contact from the review screen. That can’t be undone, so it has its own permission.

How it works

  1. Enable objects. In Settings, choose the objects Sluice covers.
  2. Create a rule. Pick the duplicate rules to listen to, the scope, the survivor and the schedule.
  3. Review groups. Scans find groups. Open each one and review it side by side.
  4. Resolve. Merge, sync or convert. Merges and syncs are backed up, so you can undo them.

Two readers, two reasons

If you’re the admin

Keep the matching you already trust and add scored Match Rules on any object. Eight custom permissions decide who may merge, sync, convert, dismiss, scan and undo.

If you’re the one signing off

Duplicates distort pipeline, split account history and embarrass reps. Most teams leave them alone because a wrong merge can’t be taken back. Sluice removes that fear.

Today, and with Sluice

TodayWith Sluice
Duplicates flagged, then left in place because merging is riskyA review screen with the result after merge
No clear view of what a merge does to related recordsRelated records counted per candidate
A wrong merge can’t be reversedBackup first, with Undo from History
Duplicates keep arriving because saves aren’t checkedWarnings as the record is saved

Where it’s strong, and what to know first

We’d rather you find the limits here than after you install.

Where Sluice is strong

  • A backup before every merge and sync, with Undo from History
  • The surviving record shown before the merge, with related records counted per candidate
  • Works with your org’s own duplicate rules, and replaces nothing
  • Warnings at save: stop it, ask once, or save and flag
  • A Lead that matches a Contact is converted into that Contact from the review screen

Good to know before you install

  • The match index is stored in a Big Object, so your org needs to be able to hold Big Objects.
  • Converting a Lead can’t be undone, which is why it has its own permission.
  • Scans run in the background on an hourly schedule. A record-page component covers the check-now case.
  • Sluice finds and resolves duplicates inside Salesforce. It doesn’t enrich records or match against outside data.

Questions people ask

We already have duplicate rules. What does this add?

Duplicate rules flag, and Sluice resolves. You get one list of every duplicate group, a side-by-side review, merge or sync with a backup taken first, and a history of what happened. Your existing rules keep working and feed it, so nothing you built is thrown away.

Can you undo a merge in Salesforce?

With Sluice, yes. A backup is taken before each merge, and you undo it from History. You also see the surviving record and the related records counted per candidate before you commit, so wrong calls get caught earlier. Undo is the net underneath.

What exactly can be undone?

Merges and syncs, from the backup taken before each one. Converting a Lead into a Contact can’t be undone, and the app says so before you do it. That’s why convert has its own custom permission, separate from merge, so you can limit who holds it.

Can we stop new duplicates as well as clean old ones?

Yes. Warning rules act when a record is saved, and you choose how firm they are: stop the save, ask once, or save and flag the record for review. Scans and the review list handle the duplicates that are already in your org.

Who is allowed to merge?

Whoever you say. By default, people can act only on records they could already edit and delete. Each action has its own custom permission: merge, sync, convert, dismiss, run scan, undo and manage rights. Grant them to the people you trust with each one.

How do you merge duplicate accounts in Salesforce safely?

Open the group, compare the records side by side, choose the one to keep, and read the Result After Merge column. Sluice backs up the merge first, so a mistake can be undone from History. Groups that aren’t duplicates can be dismissed instead of merged.

Works well with

Sluice is part of the Clean stage of the lead-to-renewal map. Not sure where your duplicates come from? Book a Data Health Check. Every app installs by itself. None needs another.

Built on the platform

  • Native to Salesforce. It works with the platform’s own duplicate and matching rules.
  • A backup before every merge or sync, so either can be undone from History.
  • Four permission sets and eight custom permissions for fine-grained control.
  • In-app guides for admins and users, in English, German, Spanish, French (Canada) and Portuguese (Brazil).

Start with the object you are afraid to merge

Ask for early access and a walk-through on one object, with a rule built from your own duplicate rules. Merge a group, then undo it.