Why does our new tool need a clean CRM before it syncs?

A new tool needs a clean CRM because it matches records one to one. If the same company exists three times, the tool can't tell which record is the real one. The sync waits until the duplicates are merged.

That's how a CRM cleanup suddenly lands on a launch plan. The tool is bought, the date is set, and the sync can't start.

In this post, you'll see why some tools need one record per company and how to find out what "clean" means for yours. You'll also see how to scope the cleanup, protect the record IDs the tool depends on and know when you're ready to connect.

What the block looks like

The block often comes from the vendor or the team setting up the tool. The setup asks for exactly one record per company or per person, and a check before the first sync finds duplicates.

Sometimes nobody stops the launch, and the problem shows up in the first sync instead. Orders or invoices land on the wrong company record, or the tool creates a new record because it found more than one match.

Why a tool needs one record per company

A sync links each CRM record to a record in the other system. To do that, it matches on a key field, like a domain or an account number. It often stores the CRM's record ID too.

A duplicate breaks that link. With two records for one company, the tool either picks one, creates a third, or refuses to continue. Any of these leaves the two systems telling different stories about the same customer.

Tools that write back to the CRM make it worse. A billing status or a support ticket can land on the record nobody uses. Our post on deduplicating your CRM before a new integration covers the wider picture.

Find out what "clean" means for this tool

"Clean the CRM first" can sound like a project with no end. For a launch, it means something narrower: clean enough for this tool. Ask the vendor or check the setup for these answers.

How to get the CRM ready for the sync

Clean the objects the tool syncs first

Leave the rest of the CRM for later. If the tool syncs companies and their billing contacts, those two objects are the launch scope. Everything else can follow on its own schedule.

Measure the gap on the key field

Search for duplicates on the field the tool matches on, and count the matches and the records in them. That number tells you how big the job is and lets you report progress to whoever owns the launch.

Start with the obvious duplicates

Merge records that share the exact key value first, like the same domain or the same account number. These are the sets nobody will argue about, and they're often most of the gap.

Then review the near matches, like name variants or country domains. Leave the judgment calls until last.

Agree on the judgment calls with the tool's owner

What counts as a duplicate is case by case, and what one team considers a duplicate, another may not. Two legal entities can be one account for sales and two customers for a billing system. The team that owns the new tool should decide those cases.

Protect the record IDs the tool depends on

If the tool stores CRM record IDs, decide which record survives each merge with that in mind. In some CRMs, a merge gives the merged record a new ID. Merging before the first sync means the tool stores the surviving IDs from the start.

If the tool or another system already stores IDs, keep a record of what each merge changed. A list of the original record IDs tells you which links in the other system need to point to the surviving record. Our post on what happens to workflows and record IDs when you merge covers how each case behaves.

Know when you're ready to connect

You're ready when a search on the tool's key field finds no obvious duplicates in the objects it syncs. The judgment calls should be decided, and the records with a blank key field should be fixed or excluded.

Run a test sync on a small set of records first, ideally in a sandbox. Check that the tool links to existing records instead of creating new ones.

New duplicates will keep arriving after launch, from forms, lists and the tool itself. Our post on managing recurring duplicates from CRM integrations covers keeping them out.

Clean enough for the tool, then keep going

A tool that needs one record per company needs a clear answer to one question: which record is this customer? That answer only has to hold in the objects it syncs.

Scoping the cleanup to those objects, starting with the obvious duplicates and protecting record IDs gets the launch moving. The rest of the CRM can follow once the sync is running.

Frequently asked questions