Duplicate records are a headache for every nonprofit admin! Over the past three years, I’ve had the privilege of connecting, with over 100 nonprofit Salesforce administrators to chat about one of their biggest headaches: duplicate records. But not all conversations are the same.

Sometimes, it’s as simple as this: an admin shows me their duplicate queue, we tweak a matching rule, and voilà—problem solved in minutes. Other times, the duplicate challenge runs a little deeper. I find myself diving into a sandbox, testing alternative matching algorithms, and brainstorming solutions with our product team. And, yes, there are even days when a meeting turns into a heartfelt therapy session—an admin shares every data woe under the sun, unloading months (sometimes years!) of frustration. As always, but especially at these moments I realize that my job starts as a listener, before I can become the problem-solver. People need a fellow human who knows just how overwhelming resolving duplicates records can feel.

No matter the scenario, my goal is always the same: to listen, empathize, and offer solutions that really help. Seeing an admin breathe a sigh of relief when their data gets back in shape? That’s what keeps me going.

The stories I’ve heard all speak to one indisputable truth: unchecked duplicates don’t just clutter up Salesforce—they ripple across an entire organization. From skewed analytics to frustrated donors, the impact adds up quickly. That’s why I’ve pulled together the nine most common duplicate scenarios I encounter, along with practical tips to clean things up today using Plauti Deduplicate. I hope it helps at least some of you. Let’s dig in!

1. Twin Donor Profiles

Picture this: your team is in the middle of a major campaign when you suddenly realize “Jane Doe” and “J. Doe” are two separate donor profiles—each with their own giving histories. Sound familiar? Don’t panic! Use Plauti’s fuzzy-matching thresholds to bridge the gap. Loosen the thresholds to catch more variations or tighten them to minimize false positives. For additional confidence, require a match on the donor’s email address or birthdate before accepting a merge suggestion. Simple tweaks like these will bring harmony to your donor records.

Read more about fuzzy matching - here - Matching Methods - Plauti



2. Fragmented Family Households

When family members—spouses or siblings—end up in separate household accounts, it throws giving totals completely off. The fix? Creat Plauti’s Address + Relationship scenario to flag all the “Smiths” living at “123 Main St.” as potential duplicates. Then, schedule weekly batch jobs to merge low-risk cases automatically. Voilà—your households are whole again!

Read more about Scenarios: Scenarios - Plauti

3. Repeated Program Affiliations

It happens all too often: a dedicated volunteer ends up signed up twice for the same program, especially after a big event. Prevent this by creating a custom rule in Plauti to flag Affiliation records with matching Contact + Program + Date values. Always run a test job(better in your sandbox) to see what kind of results are pulled up.

4. Bulk-Import Boomerangs

We’ve all been there: nightly imports from mailing lists or fundraising platforms dump hundreds of duplicates into Salesforce. But there’s an easy way to stop this at the source: route all third-party feeds through Plauti’s API endpoint. Apply your API Single Insert or API Bulk Upload to your scenario before the data hits Salesforce, so duplicates are checked at the point of entry.

Read more about API Endpoint management - here -API Single Insert / Update - Plauti

5. Overlapping Data from Different Sources

Imagine this: your supporter fills out your web-to-lead form, later makes a donation via a fundraising platform integrated with an API, and then another team member manually enters their event attendance in Salesforce.You create a donor and a new lead, and suddenly you’ve got three “different” records for the same person across different objects. Sound familiar?

To solve this, use Plauti’s cross-object matching to identify duplicates across objects.

Read more about cross-object matching - here -Cross Object - Plauti

6. Risky Merge Conflicts

Merging records is great—until the right phone number disappears into the void. Nothing stings more than losing critical data during a merge. That’s why I always recommend setting up Plauti merge rules before performing any manual merges. This will prevent data loss, build your trust in the tool, and move you toward full automation. Please remember once a record is merged with Plauti Deduplicate it can't be unmerged.

Read more about side-by-side field comparison - here -Merge Rules - Plauti

7. Sluggish Performance & Storage Caps

Thousands of duplicates don’t just make your org messy—they’re also a hidden culprit behind sluggish load times and storage limits that creep even closer. Prevent this by scheduling quarterly bulk deduplication runs with Plauti. Delete old, unnecessary jobs to free up space.

Read more about scheduling automated bulk deduplication here.-Schedule a Duplicate Check Job - Plauti

Bonus: Family Members Mistaken for Duplicates

Another family related challenge that often is overlooked but is all too common: automated logic mistakenly lumps spouses or adult children together because they share a last name or phone number. If this happens, you can discard these records so they won’t be compared to each other anymore. They’ll still be compared to other records in your org, just not to one another.

But it also helps to ask your donors not to name all their children John Jr. 😉!

Read more about discards here -Discarded Items - Plauti

You’ve Got This!

Let me leave you with this: you already have Plauti Deduplicate in your Salesforce toolkit—and that’s half the battle won. Start small by targeting the scenario that costs you the most time and frustration. Apply the matching-rule tweaks or set up automated cleanup jobs mentioned in tip number 7. You’ll see your duplicate queue shrink in no time.

Remember, clean data is more than just tidy records—it restores confidence across your team and puts the focus back where it belongs: on your organization’s mission. You’re not alone in this fight, and with the right tools and a sprinkle of determination, you’ve got this!

Happy deduplicating!

Please feel free to share any frustrations with duplicate records—and any tips—in the comments section :)