Review duplicate contacts by confirming that the records describe the same person or organisation before merging them. Names, shared phone numbers and company addresses are clues, not conclusive identity evidence. Preserve activity and relationship references, resolve conflicting fields and test permissions. A smaller contact list is not an improvement if it combines unrelated people or loses sales context.
- Verify identity before merging similar records.
- Preserve opportunities and activity relationships.
- Resolve conflicting values with an explicit survivor rule.
Define the contact identity rules
Decide whether the record represents a person, organisation or shared contact channel. A branch office can share a company name while remaining a distinct operational relationship. A reception number may serve several people and should not automatically establish that they are duplicates.
Use candidate matching rules to create a review list rather than a final merge decision. Names, email addresses and phone numbers can change or be shared. Keep the reviewer’s confidence and evidence explicit when the identity remains uncertain.
Inspect relationship context first
Review associated organisations, opportunities, tickets and relevant activity. A person may legitimately participate in several buying situations or move to another organisation. Those relationships should not be lost because the cleanup expects a single current company field.
Distinguish historical context from incorrect data. An older employer may explain a previous opportunity, while a current employer supports a new one. Decide how your record model preserves that history before overwriting fields to create a visually neat contact.
Choose a field conflict policy
Conflicting email, title or address values need a review rule. The newest value is not automatically the most reliable; it may be an import error or unverified form submission. Identify the evidence and owner for the accepted value.
Preserve useful alternate channels according to your data policy and purpose. Avoid retaining every historical detail simply because storage is available. The accepted merged record should be understandable and proportionate, with sensitive information limited to authorised roles.
Test the merge’s practical consequences
Before applying a broad cleanup, test linked activities, ownership, access and exports with representative records. Confirm that notes retain appropriate attribution and that current staff can still find the original references where needed. A merge changes more than the visible contact fields.
Provide a route to investigate mistaken merges. Depending on the system, reversal may be limited, so preserve appropriate review evidence and backups under the agreed process. Do not assume a candidate tool can undo every relationship change without demonstration.
Improve intake after cleanup
Review which channels created duplicates and where identity checks should occur. A salesperson adding a contact from an email and a website form creating another record may need a consistent review step. Avoid rigid rules that prevent legitimate new people from being recorded.
Review the pilot merge with a seller who uses the affected opportunities and with the person responsible for data access. Confirm that the accepted identity, activity and permissions remain intact. Matching and recovery behaviour require an actual demonstration; a duplicate count alone cannot establish that a cleanup was correct.
Your working checklist
- Define person and organisation identities.
- Review matches as candidates, not conclusions.
- Inspect linked opportunities and activity.
- Write conflict and survivor rules.
- Test permission and export consequences.
- Fix duplicate-producing intake paths.
Common questions
Is an identical phone number enough to merge contacts?+
No. A reception number, family number or shared business channel can legitimately appear on several records. Use it as a clue and check identity and relationship context. A merge should follow the accepted evidence rule rather than assuming that one matching field proves the records describe the same person.
Which record should survive a duplicate merge?+
Choose a survivor rule based on reliable identity, useful relationships and your record model, then resolve conflicting fields explicitly. The newest or most complete record is not always correct. Preserve review evidence and verify linked activities so the result remains understandable rather than merely reducing the number of rows.
Can duplicate cleanup damage reporting?+
Yes, if merges change ownership, organisation relationships or counted populations without preserving context. Test the effect on representative reports and exports before applying bulk changes. Explain the cleanup boundary so a later change in contact counts is not misread as a change in genuine customer interest or sales activity.
Sources and further reading
These primary references explain relevant concepts. Our scenarios and working checklists are original, illustrative guidance.
- ERPNext documentation: Lead
Further reading on CRM contact context and opportunity relationships.
- ERPNext documentation: Data Import
Further reading on record keys and validation during data preparation.
Published by EasyManageX as practical, AI-assisted guidance. Examples are illustrative. Confirm software capabilities, licence terms and project-specific requirements before committing. Read our editorial policy.
