Skip to main content

Data Quality overview

The Dedupe Console finds duplicate records and merges them safely. Detection runs on your backup snapshots — never on your live org — so scanning millions of records costs you zero Salesforce API calls and can't disturb production. Only the final merge, if you choose to run one, writes to Salesforce.

[SCREENSHOT REQUIRED: Dedupe Console with duplicate groups on the canvas and the detection setup panel]

Why duplicates matter​

Duplicate accounts, contacts, and leads fragment your customer history: two reps call the same customer, reports double-count, automations fire twice. Fixing them by hand doesn't scale — you need reliable detection and a merge you can trust (and undo).

How bluefactory approaches it​

  1. Detect on a snapshot. Pick a backup snapshot, an object, and the fields that define "the same record" — with per-field comparison types (exact, ignore case, fuzzy, and more). See Finding duplicates.
  2. Review the groups. Matches appear as duplicate groups. You choose which groups to merge and which record wins in each. Rules can automate both choices. See Winner rules and field rules.
  3. Dry run first. A merge is a dry run by default — it simulates everything and reports what would change, writing nothing. Going live requires an explicit authorization naming the record count and the org.
  4. Merge — and undo if needed. Live merges run in the background with a full per-group audit, and can be undone: merged records are restored from the Salesforce Recycle Bin and re-linked. See Merging and undo.

Where to find it​

  • Dedupe Console — sidebar → Operations → Data Quality → Dedupe Console. This is where you configure and run everything.
  • Each detection you run is saved as a scan, with its merge history — dry runs and live merges — attached to it.

Safety, summarized​

  • Detection is read-only, on snapshot data. It never writes to your org.
  • Merges default to dry run.
  • A live merge requires ticking an authorization checkbox that spells out the maximum number of records and the target org.
  • Every live merge can be undone from its run page.
  • The snapshot you scanned remains your reference of how records looked before the merge.