View as Markdown

TL;DR

  • An admin who blocks merges is usually protecting something: an integration, a past bad merge or their own job.
  • Find out what they're afraid of before you argue for merging.
  • Start with work that doesn't change the CRM: finding duplicates, counting them and showing examples.
  • Merge a small, low-risk batch with the admin watching, then grow from there.
  • Dedupely's syncing and searches never change the CRM, so an admin can review everything before a single merge.

A client hires you to clean up their CRM. Then their CRM admin says no merging, at least not yet. Sometimes it's polite caution; sometimes it's a firm block.

The admin isn't the obstacle. They know which integrations break, which records finance relies on and what went wrong last time. Getting them on side is part of the job. This post covers how.

Find out what they're afraid of

Ask before you argue. The usual reasons:

What they say What's behind it What helps
"Last time a cleanup broke things" A past merge with no record or plan Show the plan, the rules and how each merge is recorded
"Our integration depends on these IDs" A sync or billing tool points to record IDs Decide which record survives for each integration
"I'm the one who gets the blame" Accountability without control Give them approval rights and a review step
"We can't undo it" Fear of a permanent mistake Explain what can and can't be undone, and how originals are kept
"Not now, we're busy" Timing Agree on a date outside their busy period

Start with work that doesn't merge

You can do a lot before the first merge:

  1. Find and count the duplicates, per object, and show the admin the numbers.
  2. Show examples from their own data, including the tricky ones.
  3. Write the rules together: what counts as a duplicate, which record survives, which values win.
  4. List the records that must never merge, with the admin's input.

By the end, the admin has seen exactly what would happen. Often that's enough to change the answer.

Merge in small steps

  • Start with the safest matches: exact email or exact external ID.
  • Merge a small batch with the admin watching or available.
  • Check a few merged records together the same day.
  • Grow the batch size only after the admin is comfortable.
  • Keep risky matches in manual review and let the admin decide them.

Make the safety net visible

Admins worry less when they can see the way back:

  • A record of every merge, with the original values.
  • A backup or export of the records before the first batch, if the client wants one.
  • What can be undone, for how long, and what can't.

How to back up your CRM before a large merge covers the backup.

How Dedupely helps win the admin over

Connecting a CRM to Dedupely and syncing it never changes anything in the CRM; only merges do. So you can run searches, count duplicates and show examples before a single merge. You can add the admin to their own company with a role that fits, like Read-only User, so they can review matches without merging. Safety Settings hold back large and risky matches from bulk merges, Manual Review keeps uncertain sets for a person to decide, and Merge History records every merge with its original values. Most merges can be undone for 30 days from Merge History; still, treat every merge as permanent.

Show the admin before you merge

Earn the yes

An admin who won't allow merging is usually protecting something real. Find out what, do the work that doesn't change the CRM first, write the rules together, and merge in small steps they can see.

Frequently asked questions

What do I do when a client's CRM admin won't let me merge?

Ask what they're worried about, then start with work that doesn't change the CRM: finding duplicates, showing examples and writing the rules together.

Can I do anything useful without merging?

Yes. Count duplicates, review examples, agree on rules and list the records that must never merge. Most of the cleanup decisions happen before the first merge.

How do I make the first merge feel safe?

Start with a small batch of exact matches, merge with the admin available, and check a few merged records together.

What if the admin is worried about integrations?

Find out which systems store record IDs and decide which record survives for each one before merging.

Should the admin have read access to the cleanup tool?

Yes, if they want it. A read-only role lets them review matches and rules without merging.