Before merging duplicate CRM records, verify that they represent the same person or organisation. Similar names, a shared number or the same company do not always establish identity. Merging also affects history, open work and relationships.
Distinguish people, companies and branches
One person can relate to several companies, while a company can have separate branches and contacts. A shared switchboard number may belong to multiple legitimate records. Confirm the data model before deciding that a match is a duplicate.
- Identify the record type.
- Review verified contact details.
- List linked quotes, orders and service work.
- Check open tasks and owners.
- Review communication preferences and access.
Choose the master record deliberately
The newest record is not necessarily the most accurate. Decide which verified values should survive and investigate conflicting fields. Do not silently replace one person's information with another's. Contact preferences also need an authorised handling rule.
Preserve linked work
- List both records and their relationships.
- Confirm they represent the same entity.
- Select the master and retained fields.
- Test the supported merge method appropriately.
- Compare conversations, files and open tasks.
- Check for duplicate automated messages or tasks.
If a merge is irreversible, use the appropriate approval and backup process. If the product lacks a merge feature, plan a controlled migration with the technical team instead of improvising database changes.
Check the business relationship, not just the match
In a fictional example, a company's headquarters and branch share one switchboard. Merging them without review could change order addresses or ownership. Matching is a review signal, not a final decision.
Reduce future duplicates
Search-before-create, consistent field formats and possible-match warnings can help. Keep a legitimate path for creating a different entity and review repeated form submissions. Explore related guides, the BE Soft CRM service and discuss your record rules.
Frequently asked questions
Does the same phone number prove a duplicate?
No. Shared switchboards, families and branches require review.
Can the older record simply be deleted?
Not without checking history and linked work. Deletion and merging are different operations.
