Website & Business Automation
Duplicate CRM Leads: Agree on Identity Before Merging Records
Choose sensible CRM duplicate rules for email, phone and repeat enquiries. Preserve customer history and avoid merging unrelated people.
In this guide
Two records with the same name are not necessarily the same customer. Two enquiries from one email address may also represent different projects. Duplicate cleanup needs business rules, not just a “merge everything” button.
Separate people, companies and enquiries
Decide which entity the system is identifying. A contact record can represent a person while several enquiry records represent their separate requests. Shared office addresses and family phone numbers make automatic matching less reliable.
Use stronger evidence first
A verified existing contact identifier is usually more useful than a similar name. Normalising phone formatting or email whitespace can help comparison, but it should not erase meaningful differences. Review the CRM's documented matching behaviour before adding a second integration with its own assumptions.
- Keep the original record identifiers.
- Preserve notes, consent history and open tasks.
- Decide which field wins when values conflict.
- Review ambiguous matches manually.
- Record who approved an irreversible merge.
A common edge case
Imagine two colleagues submitting requests through a shared accounts email. Merging them into one person could attach private notes to the wrong contact. Keeping one company record with two named contacts and separate enquiries may better reflect the relationship, if the selected CRM supports it.
Stop duplicates at the entry point
Check whether repeated form delivery or webhook retries create new records. A submission reference can prevent the same event from being processed twice; it does not prove two different submissions are the same project. Establish a backup/export and a review process before bulk cleanup. Measure whether staff can find the right history afterwards, not merely how many records disappeared.
Need help putting this into practice?
Tell Nithu what your website needs and which systems are involved. The next step is a review of the requirements and an agreed scope, with any paid tools or ongoing costs explained before work.