TL;DR
- Decide what counts as a duplicate before anyone else starts merging records.
- Written merge rules let the person doing the cleanup decide the same way you would.
- Unclear matches should go to a review list for the cleanup owner to decide.
- Give only the permissions the cleanup needs, and remove them when the work ends.
- Dedupely lets an admin invite users to find, review and merge duplicates under the same rules.
A CRM cleanup takes time that a CRM owner rarely has. Handing it to someone else makes sense: a coworker in sales ops, a new hire, an assistant or a contractor.
The risk is that they decide differently than you would. Merges in many CRMs can't be undone, so a wrong guess about what counts as a duplicate stays in the data.
In this post, you'll see what to decide before you hand the work over and where to let them start. You'll also see which permissions to give, how to check the work while it runs and what to get back when they leave.
What to decide before you hand it over
The person you delegate to can do the work. What they can't know is how your team uses the records. These four decisions need to exist in writing before the first merge.
What counts as a duplicate
What counts as a duplicate is case by case, and what one team considers a duplicate, another may not. A contact with a work and a personal email may be one person to sales and two to marketing.
Write the definition per object, with a few real examples. Our post on what a duplicate is covers the common cases.
Which value wins in a merge
For each single-value field, decide which source wins. For supported multi-value fields, decide whether to combine values. Owner, lifecycle stage and email subscription status need particular care because a wrong result reaches sales and marketing.
What goes to review, and who decides
Some matches will be unclear, like the same name at the same company with a different email. Decide where those go and who answers them. Without that, the person either guesses or stops.
What's off limits
List what must never merge: partner accounts, records synced to billing, or customers in an open renewal. Also list which objects are out of scope for now.
| Decision | Example | Who makes it |
|---|---|---|
| What counts as a duplicate | Contacts with the same email are one person | The CRM owner, with the teams that use the records |
| Which value wins | The owner comes from the record with the latest activity | The CRM owner, with sales |
| What goes to review | Same name and company, different email | The CRM owner |
| What's off limits | Partner accounts and billing records | The CRM owner, with finance |
| Who may reject a match | Only the CRM owner | The CRM owner |
Start them on the obvious duplicates
Begin with exact matches on the field that identifies each record, like email or domain. They're the easiest to explain and the least likely to cause a dispute.
Ask the person to preview a sample before merging anything in bulk. Before the first large merge, back up the records involved, as described in how to back up your CRM before a large merge.
Rejections need the same care. A rejected match drops out of future results, so ask for rejections only when the person is certain.
Set permissions for the job
Give the person their own login. Shared credentials hide who merged what, and they're hard to take back.
In the CRM, give only the rights the cleanup needs, such as editing and merging the objects in scope. Connecting a cleanup tool to the CRM may need admin rights, which you can do yourself and keep.
Decide whether they may change rules or only follow them. If rules change during a cleanup, early and late merges no longer match.
Check the work while it runs
A short check-in keeps small mistakes from repeating across thousands of records. Look at three things.
- Counts: how many matches were found, merged, sent to review and rejected since the last check-in.
- Samples: a few merged records, picked at random, with their owners and associations.
- The review list: answer what's waiting, so the work doesn't stall on you.
A starting count helps you see progress. Our post on how to find out how many duplicates your CRM has shows how to get one.
What to get back when they leave
Delegation ends at some point, and the knowledge shouldn't leave with the person. Before their last day, ask for a handover that covers:
- The rules as they stand: any decision made along the way, added to the written rules.
- A record of the merges: what was merged, when and with which values.
- Open review items: what's still waiting, and why.
- Rejected matches: what was ruled out, so nobody wonders why those records never show up.
- Access: logins and permissions removed or reassigned.
From there, a routine keeps the CRM clean, such as the one in our CRM record maintenance checklist.
How Dedupely helps you delegate a cleanup safely
Check the actual role permissions before inviting someone. A regular user with merge access is not a read-only reviewer; use a separate review list when someone should assess matches without being able to change CRM data.
In Dedupely, admins invite users and change roles, and users can use every feature except Company Settings. You build the duplicate searches and set rules for which value wins, so merges follow the same rules whoever runs them. Unclear sets can go to review, and an audit log records each merge with the user who ran it.
Delegate the work, keep the decisions
Someone else can run a CRM cleanup well when the decisions are made first. The definition of a duplicate, the rules for which value wins and what goes to review all come from the CRM owner.
With those in writing, the right permissions and short check-ins, the person doing the work can move fast without guessing. When they leave, the rules and the record of merges stay behind.
Frequently asked questions
Can I delegate CRM data cleanup to an assistant or new hire?
Yes, once the key decisions are written down. Define what counts as a duplicate per object, which value wins in a merge, what goes to review and what must never merge. Start the person on exact matches, review the first merges together and check in regularly while the work runs.
What should I decide before someone else merges CRM duplicates?
Decide what counts as a duplicate, which value wins in each field, where unclear matches go and who answers them. Also list what's off limits, such as partner or billing records, and who may reject a match. Put it in writing so the person decides the same way you would.
What permissions does someone need to clean up CRM duplicates?
Only what the cleanup needs, such as editing and merging the objects in scope. Give the person their own login so you can see who merged what. Decide whether they may change rules or only follow them, and remove the access when the work ends.
How do I check someone else's duplicate merges?
Look at counts of matches found, merged, sent to review and rejected since your last check. Open a few merged records at random and check the owner, associations and fields your reports use. Answer the items waiting in review so the work keeps moving.
What should someone hand over after a CRM cleanup?
The rules as they stand, including decisions made along the way, and a record of what was merged. Add open review items, the list of rejected matches and a note on access to remove. That way the next person can pick up where the cleanup stopped.
Or sign up with Google
