View as Markdown

TL;DR

  • Every CRM merges differently: what survives, what moves and what can't be edited change by platform.
  • Before you merge, learn five things: objects, merge behavior, read-only fields, integrations and permissions.
  • Test a merge on a few records the client agrees you can use, and check the result in the CRM itself.
  • Keep your process the same and only adjust the parts the platform changes.
  • Dedupely works the same way in every CRM it supports and in spreadsheets, so your process carries over.

Most consultants have a home CRM: the one they've set up a dozen times. Then a client arrives on a different one. The cleanup is the same job, but the details that make a merge safe are different, and you don't know them yet.

This post covers what to find out about an unfamiliar CRM before you merge anything in it.

What changes from one CRM to the next

Area Why it matters for a cleanup
Objects Some CRMs have leads and contacts, others only contacts. Companies may be called accounts or organizations
Merge behavior Some keep the surviving record's ID, others create a new one. Some limit how many records merge at once
Read-only fields System and calculated fields can't be changed by a merge
Linked records Deals, tickets and activities may or may not move to the surviving record
Integrations Other tools may sync back and recreate a record you just merged
Permissions You may need admin rights to connect a tool or merge records

Five things to find out first

  1. Which objects hold duplicates. List the objects the client uses and what each one is called.
  2. What happens in a native merge. Read the CRM's own help pages on merging: which record survives, what happens to IDs and what moves.
  3. Which fields are read-only. These keep whatever the surviving record has.
  4. What syncs in and out. Ask the client for a list of connected tools and which ones create records.
  5. What access you'll get. Confirm you'll have the rights you need before the project starts.

Test before you scale

Pick a few duplicate sets the client agrees you can use for a test, ideally test records or low-value ones. Merge them, then check in the CRM:

  • Did the right record survive?
  • Did the right values win in fields that disagree?
  • Did activities, deals and linked records move?
  • Did any integration recreate the record a day later?

Keep your process, adjust the details

Your cleanup process doesn't need to change: agree on what a duplicate is, find them, review a sample, merge in batches, check and hand over. What changes is the detail inside each step: which objects, which fields win and what to check afterwards.

Write those details down for each CRM. The next client on the same platform will take half the time.

How Dedupely helps on an unfamiliar CRM

In Dedupely, finding and merging duplicates works the same way across HubSpot, Salesforce, Pipedrive, Close, Nimble, Google Contacts and spreadsheets, so your searches, Merge Rules and review steps carry over from one client to the next. Syncing never changes the CRM, so you can explore a new client's duplicates before you merge anything. Without Merge Rules, Dedupely follows the CRM's own merge logic, and Merge Rules only work on fields that aren't read-only in the CRM. You can test your settings on a spreadsheet export first, and partners can book a call with the Dedupely team to set up searches for a tricky dataset.

Run your next client cleanup

Same job, new details

An unfamiliar CRM doesn't need a new process. Find out how it merges, what it can't change and what syncs into it, test on a few records, then run the cleanup the way you always do.

Frequently asked questions

How do I clean a client's CRM I don't know well?

Find out how the CRM merges, which fields are read-only and which tools sync into it. Test a few merges, then follow your usual process.

What's the biggest risk on an unfamiliar CRM?

Not knowing what a merge does: which record survives, what happens to IDs and what moves. Test before you merge in bulk.

Do I need admin rights in the client's CRM?

Usually, to connect a deduplication tool. Confirm access with the client before the project starts.

Should I use the CRM's own merge tool?

For a few records, it's fine. For a full cleanup, a tool with match rules, review and merge rules saves time and mistakes.

Can I test without changing the client's CRM?

Yes. Syncing in Dedupely never changes the CRM, and you can test your settings on a spreadsheet export first.