Run a big CRM cleanup without disrupting sales

Sales teams want a clean CRM, but they also need it to work every day while it's being cleaned. A large cleanup touches the records reps call, the accounts they own and the reports their managers check.

When a cleanup surprises sales, trust drops fast. Reps can't find an account, an owner changes overnight, or the pipeline report shifts before a forecast call.

In this post, you'll see what a cleanup can change for sales, what to decide first and how to tell reps what's coming. You'll also see how to merge in stages, and how to keep new duplicates from undoing the work.

What a cleanup can change for sales

A merge turns two or more records into one. For sales, that can show up in several places at once:

• Owners: when duplicates have different owners, only one owner survives.
• Record IDs and links: a bookmarked record or a link in an email can point to a record that no longer exists.
• Automations: merged records can leave sequences or workflows they were enrolled in.
• Reports: customer counts, pipeline totals and conversion rates change as duplicates disappear.

How much changes depends on your CRM and merge method. HubSpot creates a new record ID and unenrolls both records from active workflows by default. Its Primary ID Preservation public beta keeps the primary ID and the primary record's workflow enrollment; the secondary record is unenrolled. Check which behavior applies to your account.

As of October 2026, from HubSpot's knowledge base: Merge records.

Sales teams often worry about these changes, and they're easier to manage with a plan. Each change above is predictable, so you can decide how to handle it before the first merge.

Decide the rules with sales before you start

A cleanup goes smoothly when sales helped set the rules. It goes badly when reps learn the rules from the result.

Agree on what counts as a duplicate

What counts as a duplicate is case by case. What one team considers a duplicate, another may not. Two branches of one company may be one account for marketing and two territories for sales.

Ask sales leadership which records must stay apart, like branches, regions or a person with both a work and a personal email. Write the answers down per object.

Decide which values win in the fields sales uses

Owner, lifecycle or lead stage, and the next scheduled activity matter most to reps. Decide for each one which value survives a merge: the oldest record's, the newest one's or the most complete.

Owner is the field most likely to start a dispute. Agree on who keeps an account that two reps worked before you merge it. Our post on duplicates from a sales manager's point of view covers how those disputes start.

Pick the timing

Avoid the days when sales leans hardest on the CRM, like the end of a month or quarter, forecast calls and commission cutoffs. A quiet week gives reps time to check their accounts and ask questions.

Note any large import or campaign planned during the cleanup. You can clean while they run; you just need to know when new records will land.

Tell reps what will change

Reps don't need the details of your matching. They need to know what they'll see and what to do about it. Our post on why CRM deduplication breaks as sales teams scale explains why that conversation comes first.

A short message before each stage works well. It covers:

• Which records are being merged, such as contacts with the same email.
• When each stage runs, and when it's done.
• What reps may notice, like a changed owner or a record that moved.
• Who answers questions, and where to send them.

Before merging key accounts, ask their owners to look at the duplicate sets. They know things the data doesn't, like a subsidiary that must stay separate.

Merge in stages

A big cleanup done all at once leaves no room to learn. Stages let you check each round before the next one starts.

Start with the obvious duplicates

Begin with exact matches on the field that identifies each record, like email for contacts or domain for companies. These are the duplicates sales is least likely to question.

Looser matches, like similar names at the same company, come later, once the first stages have gone smoothly.

Preview and test on a small group

Before each stage, preview a sample of merges, including a few edge cases. Merge that small group first, then open the results and check the owner and stage on each one.

If you want a safety net, export the records in the stage first. Our guide on backing up your CRM before a large merge covers how much to keep.

Send unclear sets to the people who know them

Some sets need a person to decide. Send them to review, and ask the account owner or sales manager to confirm. Reject a match only when you're certain the records aren't duplicates, since a rejected match won't come back.

A staged cleanup at a glance

Keep new duplicates from undoing the work

Forms, imports and integrations keep adding records during and after the cleanup. If new duplicates appear, reps will notice them just as they start trusting the CRM again.

Once your rules are tested, you can merge new duplicates you're certain of, like exact email matches, automatically on a schedule. Check the rest regularly, as our post on how often to deduplicate your CRM describes.

After the last stage, share the before and after numbers with sales. Fewer records and one owner per customer show reps the disruption was worth it.

A cleanup sales can see coming

A large cleanup disrupts sales when it changes owners, records and reports without warning. Agreeing on the rules with sales, telling reps what will change and picking a quiet week remove most of the surprises.

Merging in stages does the rest. Start with exact matches, test on a small group and send unclear sets to the people who know them. The CRM gets cleaner while sales keeps working in it.

Frequently asked questions