Key takeaway
Do not auto-merge customers on similar names. Matching IDs wait for confirmation; a person picks conflicting fields; orders, contacts, and files move to the record you keep. The other record is retired and its old values stay. Until confirmed, both records remain.

Suppose the following happens. Sales finds two customer cards. One is "Hangzhou Linjiang Machinery." The other is "Linjiang Machinery (Purchasing)." Someone deletes the second and types "merged" in a note. Next week two unshipped orders that lived on the purchasing card are gone. Similar names do not give the system permission to decide.
A duplicate merge should be one checkable action. Decide whether they are the same customer, let a named person resolve conflicting fields, move orders, contacts, and files onto the card you keep, retire the other card, and store the values from before the merge. Until someone confirms, leave both cards and their records alone.
Similarity is only enough to make a candidate
Separate three cases.
An identical stable number can be a strong candidate. If a customer number or a tax ID is supposed to mean one customer, two records should enter a queue for confirmation. They should not both keep accepting new work as if they were unrelated. A matching number still needs a person, because an old import may have filled the number in wrongly.
A similar name is a weak candidate. Two extra characters, a missing "Co., Ltd.," or a department in parentheses may be the same company, another company in the group, or a different ship-to under a familiar name. Weak candidates appear only on a confirmation list. A night job must not merge them.
Things that should stay separate are not duplicates. Two contacts at one company, two ship-to addresses, or two projects under one customer belong on one customer card. They are not a reason to fuse cards and erase the difference. You merge duplicate master records, not every detail under the name.
Say who may press merge. Often that is sales operations or a data owner, not everyone who can see customers. Seeing both cards is not the right to make them one.
Field conflicts need more than "keep the newest"
When both cards have a phone, an address, or an owner, no single rule fits every field.
If one side is empty, taking the filled side is usually safe. When both sides have a value, decide by field:
- Phone numbers and addresses can both be true. Do not drop the other one. Keep a primary and store the other as a secondary contact, unless a person says that value is wrong.
- Owner, default currency, and payment terms need one current value. A person picks it, and the value not picked is stored.
- The customer number that remains active can only be one. Store the retired number on the merge record so a search for the old number still opens the card you kept.
"Newest wins" will replace a correct address with an address someone just cleared by mistake. Do not make that the default for every field unless the field's meaning really is that the new value replaces the old.
Move related records; do not paste them into a note
What a merge usually loses is not the customer name. It is what hung under the customer: orders, quotes, contacts, files, and open tasks.
Those records should be reattached to the customer number you keep, and each one should remember which card it came from. Do not paste order numbers into a note and delete the old card. A note is not a relationship. Exports and queues cannot read that sentence.
Count before you move. The screen should say how many orders, contacts, files, and open items will move. If the count does not match, do not finish the merge. The count is a check on this action, not a published cleanup score.
Reattaching a file does not change who may download it. Download rules are separate. The person merging should not gain access to a contract they could not open before.
If the same number appears twice during an import, block it in the import receipt. Do not wait until both cards are in the system and hope a merge will tidy it up. That is a rule for the upload. This article is about two cards that are already stored.
A hypothetical walk-through
- Choose the retained record
- Resolve field conflicts
- Relink related records
- Retire the source and retain history
Everything below is demonstration data. An equipment trader has two customer rows, and someone is about to merge them.
Item | C-104, to keep | C-221, to retire | Merge decision |
|---|---|---|---|
Name | Hangzhou Linjiang Machinery | Linjiang Machinery (Purchasing) | Keep C-104's name; store C-221's name as a former name |
Tax ID | Empty | 9133-example-0000 | Take C-221, because the other side is empty |
Phone | 0571-00001111 | 0571-00002222 | Keep both. C-104 is primary; the other is stored as the purchasing desk |
Address | 18 Example Road, Hangzhou | 18 Example Road, Purchasing | Primary address is C-104; the department goes in an address note, not a new customer |
Owner | Salesperson A | Salesperson B | A person must choose. In this example, A; B is written into the merge note |
Unshipped orders | 1 | 2 | Move the 2 onto C-104 and record that they came from C-221 |
Quote file | None | 1 | Reattach to C-104; download rights stay as they were |
Before confirmation, the system only shows this comparison. It does not write. After confirmation, C-221 becomes merged and cannot take new orders. A search for the old number opens C-104 and says the number was merged.
If nobody has chosen an owner, the merge control stays disabled. That is safer than the system picking a salesperson.
If it was wrong, say what recovery can and cannot do
Each merge stores a merge record: who, when, the number kept, the number retired, both original values of each field, and the list of orders and files that moved.
Recovery puts those related records back and restores the kept card's fields to the pre-merge values. A field someone edited after the merge should not be overwritten quietly. Show it and let a person choose the current value or the pre-merge value.
Recovery does not promise that the merge never happened. Orders created after the merge belong to the card you kept. They should not be sent back to the retired card. Say that in the recovery note: only the listed relationships go back, not business created later.
How a general undo works is a separate design. If the merge never stored original values and the list of what moved, no later undo has anything to work from.
A merge checklist
[Customer merge checklist]
1. Candidates
- Which identical fields create a strong candidate:
- Which similarities only wait for confirmation and must not auto-merge:
- Are contacts and ship-to addresses explicitly not new customer cards:
2. Who confirms
- Who may run a merge:
- Does the screen list field comparisons and related counts before writing:
- Must a person choose when both sides have a value in a single-value field:
3. Related records
- Do orders, contacts, files, and open items move, rather than being pasted into a note:
- Does each moved record store the original customer number:
- Can the merge change who may download a file:
4. Recovery
- Are both original values, the actor, and the moved list stored:
- Does a search for the old number still find the customer you kept:
- Is it explicit that records created after the merge are not sent back:Take ten likely pairs from the current sheet and try the rules before building a one-click dedupe. Customer numbers and field meanings can go into the system preparation guide. If customers, orders, and files must be reattached inside one admin, put merge and recovery into the scope you discuss with business system development.
What CRM, SCRM, and AI CRM each solve is covered in that product comparison. How missing entry rules make a system unreliable is covered in five common traps in SMB digitization. Neither replaces the merge steps here.