TL;DR
- In calls with 106 teams, cleanups rarely stalled on finding the duplicates.
- They stalled waiting on someone else: a manager, IT or another team.
- Security and legal reviews held some teams back before they could even start a trial.
- Others held back merges for fear of losing data or merging the wrong records.
- Dedupely lets you measure duplicates without changing the CRM, so approvals start from real numbers.
Ask a team why their CRM still has duplicates after months of planning a cleanup, and the answer is rarely "we couldn't find them". We went back through calls with 106 teams evaluating or using Dedupely, from June to November 2026, and looked at what held cleanups back. Three reasons came up again and again.
1. Waiting on someone else
The most common delay was another person's decision. Teams had to wait for a manager's approval, an admin who could grant access, a board that met monthly, or a colleague who knew which records to keep. Some teams found the tool they wanted and still waited weeks for a decision about the budget or the rules.
What helps:
- Name the decision maker before the evaluation starts.
- Bring numbers to the conversation: how many duplicates, which objects, what they cost the team.
- Agree on the merge rules with the people who own the data, not just the admin.
2. Security and legal review
Several teams couldn't connect their CRM, even for a trial, until security or legal approved the tool. Teams in healthcare and financial services mentioned it most, with questions about certifications, data storage and agreements.
What helps:
- Ask for the security questionnaire on day one, not after the trial.
- Send the vendor's documents with the request: certifications, data processing agreement, sub-processors.
- Test with a sandbox or dummy data while the review runs, if your policy allows.
3. Fear of merging the wrong records
A few teams had the tool, the access and the approval, and still held back. They worried that a merge would combine two different people, lose a contract or activity history, or break a report someone else relies on.
What helps:
- Start with the obvious duplicates, like exact email matches.
- Preview the merge result before you merge.
- Merge a small batch and check it in the CRM.
- Keep a record of the original values, so any merge can be traced and corrected.
What didn't stall cleanups
Finding duplicates was rarely the blocker. Most teams already knew they had them, from their CRM's own duplicate tool, a report that looked wrong, or reps complaining. The hard part was getting from "we know" to "we merged".
How we reviewed the calls
We looked for reasons a team gave, in their own words, for not moving ahead. We didn't count reasons Dedupely staff described on a team's behalf, or issues with Dedupely itself. Most of these reasons came up in a minority of calls, so this post describes patterns rather than shares.
How Dedupely helps cleanups move
In Dedupely, connecting and syncing never change your CRM, so you can measure duplicates before anyone approves a merge. Dedupely's Trust Center has its security documents and sub-processor list, and Dedupely is ISO 27001:2022 certified. Merge Rules and the merge preview show the result before you merge, Safety Settings keep risky matches out of bulk merges, and Merge History records every merge with the original values. Most merges can be undone for 30 days.
The duplicates aren't the hard part
On our calls, cleanups stalled on people, reviews and confidence, not on finding duplicates. Name the decision maker, start the security review early and build confidence with a small, checked first batch.
Frequently asked questions
Why do CRM cleanup projects stall?
In our calls, mostly waiting on another person's decision, a security or legal review, or fear of merging the wrong records.
How do I get a cleanup approved faster?
Bring numbers: how many duplicates, which objects and what they cost the team. Name the decision maker early.
How do I speed up a security review?
Request the questionnaire at the start and send the vendor's documents with the request.
How do I get over the fear of merging the wrong records?
Start with obvious duplicates, preview the result and merge a small batch first.
How was this research done?
We reviewed calls with 106 teams evaluating or using Dedupely between June and November 2026.




Salesforce AppExchange