Dedupely Intelligence
TL;DR
- Change freezes and audits often ban changes to customer records, and a merge is a change.
- Pause automatic merging and bulk merges before the window starts, and say so in writing.
- You can keep finding and reviewing duplicates, because that doesn't change the CRM.
- Merge urgent cases only with sign-off, and keep a record of each one.
- In Dedupely, matching and review continue while merging is paused, and the Audit Log records every merge.
Many companies have periods when nobody is supposed to change important data: a year-end close, a financial or security audit, a system migration, a peak sales week. IT calls it a change freeze.
Duplicates don't stop during a freeze. Merging them does change data, so it usually falls under the freeze. This post covers what to pause, what you can keep doing and how to restart afterwards without a backlog surprise.
Why merges count as changes
A merge rewrites the surviving record, moves activities and associations, and removes the other records. During an audit, that can:
- Change numbers an auditor already sampled, like customer counts or open deal totals.
- Move records an auditor is tracing, like an invoice linked to a company that's merged away.
- Change IDs that a report or a finance system relies on.
So treat merging like any other data change during the window.
What to pause before the window
- Automatic merging. Turn off any scheduled or automatic merges.
- Bulk merges. Hold planned batches until the window ends.
- Imports that might be merged later. Note which ones arrive during the freeze, so you can review them afterwards.
- Tell the team. A short message: merging is paused from this date to this date, flag duplicates instead of merging them.
What you can keep doing
A freeze doesn't have to stop the cleanup:
| Activity | Changes the CRM? | During a freeze |
|---|---|---|
| Finding duplicates | No | Keep going |
| Reviewing matches and deciding | No | Keep going |
| Writing or adjusting merge rules | No | Keep going, test on a sample after the window |
| Rejecting false matches | No, in most tools | Keep going |
| Merging | Yes | Pause, or only with sign-off |
When the window ends, the review work is done and the merges can run straight away.
When a merge can't wait
Sometimes a duplicate causes a real problem during the freeze: a customer getting two invoices, or a rep calling an existing account as a prospect. In that case:
- Get sign-off from whoever owns the freeze.
- Merge that set only, not the whole search.
- Record it: who merged, when, which records and why.
How Dedupely fits a freeze
Syncing and scanning in Dedupely never change your CRM; only merges do. So searches, Manual Review and rejecting false matches can continue while you pause Auto Merge on each Duplicate Search. Auto Merge can also run between hours you choose, which helps with short daily windows. For audits, Merge History shows who merged each set, its CSV export keeps the original values and record IDs, and the Audit Log records merges, scans and setting changes, with entries kept indefinitely.
Pause the merges, not the work
A change freeze or audit is a reason to stop merging, not to stop cleaning. Pause automatic and bulk merges, keep finding and reviewing duplicates, merge only urgent cases with sign-off, and run the reviewed merges when the window ends.
Frequently asked questions
Can I merge CRM duplicates during a change freeze?
Usually not, because a merge changes records. Pause automatic and bulk merges, and merge urgent cases only with sign-off.
What can I keep doing while merging is paused?
Find duplicates, review matches, write merge rules and reject false matches. None of these change the CRM in most tools.
Why do auditors care about merges?
Merges change counts, move linked records and can change record IDs, which can affect what the auditor is checking.
How do I restart after the freeze?
Merge the sets you reviewed during the window first, then switch automatic merging back on and check the first runs.
What should I record for a merge made during a freeze?
Who merged, when, which records, why it couldn't wait and who approved it.
Or sign up with Google
Pipedrive Marketplace