TL;DR
- A single CRM admin can't review every duplicate, so certainty decides what gets merged first.
- Start with obvious duplicates, like exact email matches, which need the least review.
- Automate merging only for duplicates you would merge without looking.
- Written merge rules let someone else cover the work when the admin is away.
- Dedupely helps solo admins find, review and merge duplicates, with help from its Customer Success team.
When you're the only person who manages the CRM, duplicates compete with everything else. Sales wants a new field, marketing wants a list, and leadership wants a report by Friday.
Meanwhile, forms, imports and integrations keep adding records faster than one person can check them. A full cleanup sounds like a project for a team you don't have.
In this post, you'll see how to sort duplicates by how sure you are, what to automate and what to keep for review. You'll also see how to keep a short review routine, write your rules down and get decisions from other teams.
Why deduplication is harder when you're alone
A team can split the work and check each other's merges. A solo admin makes every decision alone, often between other requests.
There's no second opinion before a large merge, and interruptions break up the time a careful review needs. The knowledge of why something was merged also lives only in your head.
None of this means the cleanup has to wait. It means the plan has to fit one person's time, and it has to survive the days you're not there.
Sort duplicates by how sure you are
With limited time, start with the duplicates you can merge with the least checking. Sort them by certainty, and the plan follows.
| Certainty | Example | What to do |
|---|---|---|
| Obvious | Confirmed same person or company; shared inboxes and separate branches excluded | Test a reviewed sample, then bulk merge; automate only the verified rule |
| Likely | Same name and company, different email | Review in short sessions |
| Unclear | Same name only, or a shared inbox like info@ | Ask the team that uses those records |
| Not a duplicate | Branches of one company, or a parent and its subsidiary | Reject, but only when you're certain |
Rejecting a match takes it out of future results, so a wrong rejection hides a real duplicate. If you're unsure, leave it for review. Branches and subsidiaries are covered in how to handle related records that look like duplicates.
Automate only the duplicates you'd merge without looking
Automation can save a solo admin a lot of time, and it carries risk too. A wrong rule repeats its mistake on every record it touches.
Keep automation for the duplicates you'd merge without looking, like exact email matches on contacts. Test the rules on a sample first and preview the merged records. Once the rules hold, you can merge new duplicates you're certain of automatically on a schedule.
Leave the less certain patterns in review. How often to check depends on how much new data arrives, which we cover in how often to deduplicate your CRM.
Keep a short review routine
Review can take up much of a solo admin's time, because it has no natural end. A short session at a fixed time keeps it from growing.
- Book the time: a regular slot in your calendar, short enough that you keep it.
- Start with the objects sales uses daily: duplicate contacts and companies affect more people than old leads.
- Look at new duplicates by source: one form or integration creating most of them is worth fixing at the source.
- Stop when the slot ends: what's left waits for the next session.
For the full list of what to look at each month and quarter, see the CRM record maintenance checklist.
Write the rules down
When you're the only admin, the rules often live only in your memory. That works until you're on vacation, someone asks why two accounts were merged, or you hand the CRM to someone else.
One page is enough. Keep it where the rest of your CRM documentation lives, and update it when a decision changes.
| What to write down | Example |
|---|---|
| What counts as a duplicate, per object | Contacts: same email. Companies: same domain, except branches. |
| Which fields you match on | Email first, then name with company |
| Which value wins in a merge | Newest value, except the owner and lifecycle stage |
| What never merges | Partner accounts, records synced to billing |
| Who decides unclear cases | Sales ops for contacts, finance for billing companies |
| What runs automatically | Exact email matches on contacts |
Ask other teams for decisions
From other teams, what you need is their answer on what counts as a duplicate. That's case by case: what one team considers a duplicate, another may not.
Keep the ask small. Bring three or four real examples, each with one question, such as whether two records are one customer. A short answer from the right person saves you from undoing a merge later.
In larger companies, a RevOps team may own this process together. Our post on CRM deduplication for RevOps teams covers that setup.
How Dedupely helps a solo admin keep up with duplicates
Dedupely lets a solo admin build searches for supported objects, choose surviving values and preview merges. Keep uncertain identities in review and automate only rules checked against a representative sample. Customer Success offers help by call, chat and email when a case needs more attention.
A plan that fits one person's time
A solo admin can't check every duplicate, and doesn't need to. Sorting by certainty lets you merge the obvious ones quickly and automate them once the rules hold. Your review time then goes to the cases that need a person.
Writing the rules down turns what you know into something others can use. It makes your merges easier to explain, and it keeps the work going when you're away.
Frequently asked questions
How can a one-person CRM admin keep up with data cleanup?
Sort duplicates by how certain they are, then merge the obvious ones first, such as exact email matches. Automate only the patterns you'd merge without looking, and keep a short review session for the rest. Write your rules down so others can follow them and cover the work while you're away.
Which duplicates should a CRM admin merge first?
Merge the obvious duplicates first: contacts with the same email and companies with the same domain. They need the least review and remove a large part of the noise. Then move to likely matches, such as the same name at the same company with a different email, and review those before merging.
Is it safe to automate merging CRM duplicates?
It can be, for duplicates you're certain of, such as exact email matches. Test your rules on a sample, preview the results and check that blanks don't overwrite existing values. Keep less certain matches, like similar names, in review, since an automated rule repeats any mistake on every record.
How do you document CRM deduplication rules?
Keep a one-page document with what counts as a duplicate per object and the fields you match on. Include which value wins, what never merges, who decides unclear cases and what runs automatically. Update it whenever a decision changes, and keep it with your other CRM documentation.
Who decides what counts as a duplicate when there's one admin?
The admin runs the process, but the teams that use the records help decide. What counts as a duplicate is case by case, and sales, marketing and finance may see the same records differently. Bring them a few real examples, ask one question per example and write down the answer.
Or sign up with Google
Pipedrive user 
