Migration & data
Clean Up Duplicate Plumbing Customers Without Losing Job History
Treat a duplicate match as a review candidate, not an automatic merge instruction. Confirm identity, inspect linked properties and financial records, choose the retained record, and preserve a traceable mapping from the old references.
In this guide
Define a duplicate carefully
Two records with the same name may represent different people or organizations. Two records with different names may refer to the same customer after a spelling correction or business-name change.
A shared phone number or address can help the review, but it may also be used by a household, office, or property manager serving several locations. Use multiple pieces of evidence and the business context.
Do not merge live records unless the software's supported process and the effects on relationships are understood.
Build a candidate-review sheet
candidate_group,source_record_a,source_record_b,matching_evidence,conflicting_evidence,linked_jobs_checked,linked_invoices_checked,decision,retained_reference,reviewer
GROUP-EXAMPLE,CUST-A,CUST-B,similar_name,different_property,false,false,review_required,,office_owner
The example is fictional. Keep sensitive customer information in the appropriate protected source and use references in the review sheet when possible.
Check the relationships before the display name
Review service properties, jobs, estimates, invoices, payments, and communication history. The consequences of a merge extend beyond the name shown in the customer list.
For a fictional example, two records called “Oak Management” may correspond to different legal or billing entities. Combining them because their names look similar could put invoices under the wrong responsible party.
Conversely, “Sam Lee” and “Samuel Lee” might be the same customer, but the records still need a careful decision about which contact details are current and which properties belong to them.
Choose the retained information explicitly
| Decision | What to record |
|---|---|
| Primary identity | Why this record is retained |
| Contact details | Which value is current and how it was verified |
| Property links | Which locations belong to the customer |
| Historical references | How old IDs remain traceable |
| Conflicting notes | How discrepancies are preserved or resolved |
Do not overwrite a valid billing contact with a newer access contact simply because the latter record was created most recently.
Test the merge or remapping behavior
Use a safe test or supported review process before making a broad live change. Confirm what happens to linked jobs, open invoices, archived records, attachments, and external accounting references.
A system may support a true merge, a reassignment, an archive, or no direct merge at all. Do not assume those actions have the same effect.
If a correction affects posted financial records or accounting integrations, involve the relevant owner before proceeding.
Reconcile after cleanup
Check that all relevant jobs and properties remain accessible and that invoice balances and payment relationships have not changed unexpectedly. Preserve a log mapping old identifiers to the retained record.
Do not reuse an archived customer's identifier for an unrelated new customer. Historical references should continue to point to the correct meaning.
Prevent the next duplicate
Require a search before creating a new customer, using the relevant name, contact, and property context. Make the distinction between a new property and a new customer clear to staff.
Review import matching rules before rerunning files. A repeated import that creates new records instead of updating known IDs can undo a careful cleanup.
The best duplicate process is cautious and traceable. A smaller customer count is not a success if the cleanup has combined the wrong histories.
Sources and editorial notes
Product and documentation references checked September 29, 2026. GoPlumber publishes this guide about its own product category. Examples and templates are original illustrative material, not customer case studies or market benchmarks. Confirm current vendor terms before acting.