Duplicates rarely announce themselves. You find out because a donor got two acknowledgment letters, or a rep called a lead who has been a customer for a year. Then you go looking for a tool, and every buyer’s guide you find was written by a company selling one of the options.
We built one of these tools. Dedupe & Match is a module in the Apsona suite, so we would rather say that here than have you find it halfway down. The rest comes from an interview with Justin Barss, who works with Salesforce admins on duplicate problems, plus published documentation for every product named.
By the end you will know where native Salesforce stops, what to compare, and how five options differ.
Why duplicate records happen in Salesforce
Most Salesforce orgs are fed by other systems. Forms, websites, event platforms, and integrations all create new records, and none of them was built to your data standards. They are optimized to capture the record, not to perfect it.
Blocking duplicates at the point of entry helps, but it has a cost: it slows the process down and can leave data stuck mid-transit instead of in Salesforce where someone can act on it. So the practical approach is usually to let data land, then clean it in one place. You cannot control how four upstream systems behave. You can control what happens in your system of record.
How does Salesforce handles duplicate records
Salesforce comes out-of-the-box with matching rules, which define what counts as a match, and duplicate rules, which decide what happens when one is found: warn, block, or log for review.
For plenty of orgs that is enough. It costs nothing and it stops a real share of duplicates at the door. Any honest evaluation starts by asking whether you have pushed it to its limit yet. Here is where it stops:
- Three records per merge, selected manually, on the same object (Salesforce Help). A group of 15 duplicate contacts takes seven separate merges.
- No automation. Every merge is a human action.
- Limited object coverage. The Potential Duplicates component cannot be added to custom objects (Salesforce Help).
- Five active matching rules per object (Salesforce Help).
- Duplicate jobs, which scan records you already have, require Performance or Unlimited edition (Salesforce Ben, May 2026).
That does not make the native tools bad. It makes them a starter set. Once duplicates arrive faster than one person can merge them three at a time, you are choosing between buying something and living with the mess.
Audit your org before you shop
Four questions, answered with real numbers, will get you a better tool and a better price than any vendor conversation will.
- Where are duplicates hurting? Usually a missed follow-up or a customer getting the wrong communication. That is the cost an executive approver cares about.
- How many, how often? “Roughly 200 duplicate contacts a month, mostly from event imports” is a different negotiation than “a lot.”
- Which objects? Transactions, opportunities, and custom objects are where tools differ most.
- Where does your team lose time? If two people spend a morning a week reviewing records, that is budget you already spend.
Our Time Savings Calculator works through that last one with no form to fill in.
Six things to compare
- Volume in one pass. Every tool has a ceiling. Ask for it in records and fields.
- Object coverage. Standard objects are table stakes. Ask specifically about custom objects and whichever object holds your transactions or gifts.
- Matching control. Fuzzy matching, meaning detection that catches Bob Smith and Robert Smith rather than only exact matches, is the baseline. Beyond that, can you target a slice of records and build separate setups for different source systems?
- Automation or review. If duplicates arrive through one or two predictable paths, automation lets you set it and check in. If you are merging transaction data, you want eyes on every merge. Know which you are buying.
- Where your data goes. A native tool, built on the platform so records never travel to another server, removes a whole category of compliance question. Ask every vendor plainly whether data leaves Salesforce.
- Maturity and support. The AgentExchange is full of apps built for one customer’s problem and left there. A team that has seen 50 orgs has not seen yours, and a small vendor may not have capacity when something breaks at volume.
One more thing: trials show you the interface. A paid initial cycle against your real data, or two tools running side by side for a month, shows you whether it solves your problem.
How five options compare
Native Salesforce comes first because every org already has it. The rest are alphabetical, which happens to place Apsona near the top. We did not put it there, and our entry carries its own limitations like every other.
| Tool | Best for | Where it runs | Starting price |
| Native Salesforce | Occasional duplicates and time to merge by hand | Inside Salesforce | Included |
| Apsona Dedupe & Match | Review-before-merge control across any object | Inside Salesforce | $125 per builder license per month, billed annually, 3 minimum (apsona.com, effective May 1, 2026) |
| Cloudingo | Scheduled, automated dedupe with undo | External app connected to Salesforce | $2,500 per year per org (cloudingo.com, August 14, 2026) |
| DemandTools | Enterprise volumes and complex matching logic | Installed on your computer | $11 per Salesforce license per month (validity.com, August 14, 2026) |
| Plauti Deduplicate | Native automation at large record volumes | Inside Salesforce | Not published, quoted per org (plauti.com, August 14, 2026) |
Native Salesforce duplicate management
Matching rules, duplicate rules, and a manual merge screen, included with your license. Best for orgs with occasional duplicates, and any org that has not configured its rules properly yet. Do this first regardless of what else you buy. Strength: free, and prevention at the point of entry that no cleanup tool replicates. Limitation: three records per merge, no automation, and limited custom object support (Salesforce Help).
Apsona Dedupe & Match
A deduplication and matching module in the Apsona suite, which also covers cross-object reporting, document and email merge, and bulk data work. Best for admins who want to review before merging, across any object including custom ones and managed packages. Strength: complex filtering to target a specific slice of records, CSV matching to check a file before you import it, and everything running inside Salesforce. Limitation: no cross-object matching, so you cannot match leads against contacts in one operation. It is browser-based, with a practical ceiling around one million cells per action, meaning columns times rows. apsona.com/dedupe-and-match
Cloudingo
A dedicated deduplication product runs through a Cloudingo account with an agent installed from the AppExchange. Best for teams wanting automation and a low-touch cleanup rhythm. Strength: scheduled automation and undo, which not every tool offers. Cloudingo states it stores only an index of matching fields, not your data (cloudingo.com, August 14, 2026). Limitation: it runs outside Salesforce and connects in, so confirm the architecture in detail if data residency matters. Feature access is tiered. cloudingo.com
DemandTools
Validity’s data quality platform, covering deduplication, standardization, and mass updates. The full product installs on your computer rather than running in a browser (Salesforce Ben, November 2024). Best for organizations processing millions of records regularly with complex logic. Strength: local hardware handles session volumes browser-based tools cannot. Limitation: each user installs it locally, and longtime users have criticized the move from DemandTools Classic to V for missing features (Validity Community, December 2024). validity.com/demandtools
Plauti Deduplicate
Formerly Duplicate Check. Installs from the AppExchange and runs entirely inside Salesforce (plauti.com, August 14, 2026). Best for teams wanting automation and prevention at volume without data leaving the platform. Strength: fully native, with automated merging, real-time warnings at entry, and an audit log. Limitation: processing speed is tied to Salesforce, which is why Plauti offers local and cloud processing for large jobs (plauti.com). Pricing is not public, which makes budgeting harder.
Which one should you choose?
By scenario, not by winner.
- Rules not configured yet. Start with native Salesforce. Spend the afternoon before you spend the budget.
- Predictable duplicates you want to stop thinking about. Automation-first. Cloudingo and Plauti Deduplicate both aim here.
- Review before merge, across objects Salesforce will not touch. Control-first, especially for transaction and opportunity data. Apsona Dedupe & Match is built for this.
- Millions of records per session. A browser will not hold that. DemandTools, or Plauti’s local processing.
- Data cannot leave Salesforce. Salesforce itself, Apsona, and Plauti Deduplicate. Ask everyone else to describe their architecture in writing.
Frequently asked questions
How many records can Salesforce merge at once? Three, on the same object, selected manually (Salesforce Help).
Do I need a third-party tool at all? Not necessarily. If your matching rules are well configured and volume is low, native Salesforce may be enough. The tipping point is when duplicates arrive faster than someone can merge them three at a time.
Which tools keep data inside Salesforce? Among these, Salesforce’s own tools, Apsona, and Plauti Deduplicate run natively. Cloudingo connects from outside and DemandTools runs on your computer.
What is the cheapest option? Native Salesforce, included with your license. Among paid tools, published starting prices run from $11 per Salesforce license per month to $2,500 a year per org. The cheapest tool is rarely the cheapest outcome, since a product built for one use case may not handle yours.
Can any of these match leads against contacts? Some can, some cannot, and it is worth asking explicitly. Apsona does not do cross-object matching today.
Where this leaves you
Start with the free move. Fix your matching rules, then count duplicates for 30 days so you know the volume, the objects, and the sources you are actually shopping for. After that the decision is short: predictable duplicates point to an automation-first tool, transaction data points to one that asks before it merges, millions of records per session point to something running on local hardware, and a hard data residency requirement narrows you to the native options. Shortlist two, buy one for a single cycle against real data, and decide who owns the cleanup before the tool arrives.
If you want a second opinion on that shortlist, tell us about your duplicate problem and we will tell you which category of tool fits, including when it is not ours. On the form, choose the sales option rather than support, and ignore the severity field, which is there for existing customers reporting issues. Apsona is a data management suite that runs inside Salesforce, and Dedupe & Match is one module in it, alongside reporting, document and email merge, and bulk data tools.
