Merging consolidates records. Establish that they represent the same person and decide which information should survive before confirming.

Before you beginConfirm the intended CentriCRM business, your permissions and feature availability. Use controlled records while learning; obtain authorization before live changes.

Step by step

  1. Search for the suspected duplicates using email, phone and name. Compare identities rather than relying on a shared surname.
  2. Open each record and note conflicting details and related work that your team needs to preserve.
  3. Use the available merge action only for confirmed duplicates. Choose the intended master record.
  4. Review the proposed field mapping. Resolve conflicting values with the record owner rather than accepting every default.
  5. Have an authorized user confirm the merge after reviewing its effects. Do not use merging to associate different household members.
  6. Reopen the surviving contact and verify details, findability and the business context. Check the associated work important to your team.

Expected result

One verified contact remains with reviewed identifying details.

Troubleshooting

  • If records represent different people, keep them separate and use an appropriate relationship instead.
  • If the merge control is absent, check permissions; do not delete records as a substitute.
  • Escalate unexpected missing history with the surviving record ID and redacted evidence.

Supporting documentation

These links open the provider’s documentation. Availability and permissions depend on your account.

More guides

Create and verify a contactKeep a single useful customer record, check the business context, and confirm your changes saved.
Review and respond to a conversationFind the right thread, review its history, and check the channel and recipient before responding.
Check a website lead form before launchFollow a controlled submission from the public form to the correct contact and follow-up process.
Prepare an authorized private integrationDefine the business, owner and permissions before an administrator grants a developer access.