A sales consultant creates a record for “Northstar Services”. Two weeks later, accounts adds “Northstar Services (Pty) Ltd” from an invoice. A colleague then creates “North Star” after receiving a new enquiry.
The same customer now has three records. The opportunity is attached to one, the quote to another and the decision-maker’s latest telephone number to the third. Each record looks incomplete, so every team member makes a different decision about what is happening next.
Duplicate data is not merely untidy. It separates the history, ownership and work that should give the business a shared view of the customer.
Agree what one customer record represents
Before cleaning anything, define the unit your CRM should treat as the customer. For many businesses, this is the legal or trading organisation, with individual people recorded as contacts. A group with several branches or subsidiaries may need separate records linked by a clear parent relationship.
The rule should answer practical questions:
- Is each branch managed and billed separately?
- Can several trading names belong to one legal entity?
- When should a contact move rather than be copied?
- Which identifier best distinguishes similar organisations?
- Who may create a new customer record?
Without a shared definition, one person’s duplicate can look like another person’s legitimate account.
Check before creating
The safest duplicate is the one that never enters the CRM.
Before creating a customer, search more than the exact name supplied. Check common abbreviations, trading names, website domains, telephone numbers, registration details and physical locations where appropriate. A small spelling difference should not be enough to create a second account.
Do the same for contacts. A new email enquiry may come from somebody already recorded under another employer or with an older address. Confirm whether the existing record should be updated, related to a new customer or retained for a valid historical reason.
Make this check part of the normal capture process. If users only search when they suspect a duplicate, the business will find most problems after the records have already divided.
Choose the surviving record deliberately
When duplicates exist, do not automatically keep the oldest or newest record. Select the record that provides the strongest operational foundation.
Review its customer identifier, ownership, active opportunities, quotes, invoices, contacts, tasks and communication history. The surviving record should be the one the team can use confidently after the clean-up.
Then decide which values are authoritative. A recently updated telephone number may be more useful than an older one, while the legal name on an approved account record may be more reliable than the wording copied from an email signature.
Record how conflicts were resolved. Quietly replacing information can make it difficult to understand why a value changed later.
Reconnect the work before closing duplicates
A duplicate cannot be resolved safely by renaming it “Do not use”. First account for every relationship and open item attached to it.
Check for:
- Open leads and sales opportunities.
- Quotes, invoices or orders.
- Customer contacts and decision-makers.
- Tasks, appointments and promised follow-ups.
- Documents, notes and communication history.
- Account ownership and internal responsibilities.
Move or reconnect each item according to the organisation’s approved process. Preserve information that explains what happened; a clean customer page should not come at the cost of losing the sales trail or financial context.
Make ownership visible
Duplicates often survive because different teams believe they own different versions of the same customer.
Give the surviving record a clear account owner and make the responsibilities for open work explicit. The account owner may coordinate the relationship, while individual opportunities, tasks or invoices remain assigned to the colleagues responsible for completing them.
This distinction matters. “Owned by sales” is not a next action. “Lerato will confirm the revised requirement by Thursday” is.
Use a practical example to test the process
Return to Northstar. The team identifies the approved legal account as the surviving customer record. They add “North Star” as a recognised trading-name variation, confirm the correct website domain and relate the current contacts to that account.
The active opportunity and quote are reconnected, the upcoming follow-up remains assigned to its owner and the accounts team verifies the billing details. The duplicate records are then closed according to the organisation’s retention process, with a note pointing colleagues to the surviving customer.
The result is not simply fewer records. Sales, operations and accounts can now see the same relationship and act from the same information.
Prevent the duplicate from returning
Clean-up is temporary if the capture process remains unchanged.
Review a small sample of newly created customers regularly. Look for repeated domains, similar names, matching telephone numbers and accounts created without an owner. When a duplicate appears, identify how it entered rather than correcting only the final record.
Useful prevention controls include a clear naming standard, required identifying information, a pre-creation search, restricted merge or closure permissions and a simple route for users to flag possible matches.
At MyTalent Software, Business CRM is positioned around leads, sales, customer relationships and business operations, with a shared view of customers, opportunities and the work ahead. Explore Business CRM or talk to our team about the customer-data and sales workflows available for your organisation.
One reliable customer record gives every team a clearer starting point—and every next action a better chance of reaching the right place.