Duplicate customer merge review
Record candidate pairs and unresolved evidence. This tool changes no customer database.
No signup. Enter reference codes, add records and download a CSV. Entries stay in the browser tab. Filled fields do not establish completion, approval or compliance.
| First record reference | Second record reference | Identity evidence or conflict | Contact preference review | Review outcome | Review owner |
|---|---|---|---|---|---|
| Record-21 | Record-74 | Shared fleet office contact; driver identity unverified | Not reviewed | Unresolved | Advisor-A |
| Record-13 | Record-65 | Check vehicle associations and current contact | Conflict needs resolution | Unresolved |
- Use internal references. Do not enter full customer contact details.
- Review identity, history, preferences and your platform’s merge behavior before any change.
- The export is a review worksheet. It performs no merge or permission update.
The same driver appears twice in your reminder list. An old email address sits in one record. The current vehicle and a request to stop promotional messages sit in the other. Review both records before deleting the older-looking entry. The history you need might be in either one.
The worksheet above prepares a duplicate-record review. It does not connect to your CRM or merge anything. Use internal record references, document the evidence and choose a review outcome. Its fictional examples demonstrate the difference between a candidate match and permission to change a customer database.
Use with this guide
Build a declined-work follow-up queue
Check eligible records before allocating staff time.
Review customer and payment references
Keep the source records clear before changing operational systems.
Review customer loyalty requirements
See the paid product scope before preparing an audience.
Audit a repair-shop customer export before moving to a new CRM
A successful import message does not prove the right driver, vehicle and preferences survived the move. Review field meanings and actual record links.
How to measure whether a service reminder brought a customer back
A return visit after a reminder is an observation. Use a consistent comparison before crediting the message with the whole repair order.
Browse the complete auto repair guides and worksheets.
Treat a matching field as a review candidate
A shared email or phone number does not establish the same contact. Households share numbers, and a fleet office might receive messages for several drivers. Compare the person, company relationship, vehicles and service history between the suspected duplicates. Keep the review open when those details conflict or staff have not confirmed the identity.
HubSpot documents automatic deduplication by specific properties, including contact email and company domain, with behavior varying by record type and import method. Your repair software might use different rules. Check its documentation before importing a cleaned spreadsheet. A list looking tidy does not establish whether an import will update existing customers or create another set of records.
Sources for this section: HubSpot: Deduplicate records
Review history before choosing a surviving record
Open both records in the approved system. Note which holds the current contact information, vehicle associations, repair-order links and conversation history. Identify conflicting values instead of silently choosing the latest-looking row. A newly created record might contain less reliable information than an older verified record. Ask staff to resolve unclear identity before changing either customer.
In the fictional worksheet, Record-21 and Record-74 share an office contact but still need an identity check. The review outcome stays unresolved. A second pair includes an instruction to inspect contact preferences. Neither row recommends a merge. Use the worksheet to record the review questions, not to classify every matching field as a confirmed duplicate.
Preserve communication restrictions
Check unsubscribes, do-not-contact notes and other recorded preferences in both records. Verify how your actual platform handles those properties during a merge. Do not assume the preferred primary record automatically retains every restriction. If the records disagree, resolve the conflict in the authorized system before placing the customer in a promotional audience.
Keep campaign eligibility separate from identifying a customer. Removing a duplicate does not create permission to send marketing. After an approved cleanup, review the next audience export against the current restrictions. Inspect your messaging tools too. An old list in another system still exists even after the CRM records change. Assign someone to maintain the audience source and suppress stale exports.
Read the merge behavior before acting
HubSpot says merged records cannot be unmerged, and describes how activities, associations and properties combine. Other platforms need their own review. Record which account and objects you are changing, who has the required permissions, and what recovery options exist. Retain an approved export where your business allows one. An export is not proof every relationship will be restored.
For an uncertain match, leave the review open. For two distinct people, mark keep separate and document the reason. For a confirmed match, follow the platform’s documented process and verify the resulting record. This worksheet performs none of those operations. It checks required fields and exports your review notes so a responsible staff member has a clear decision to inspect.
Sources for this section: HubSpot: Merge records
Test the next reminder list
Generate a small audience from the approved source after cleanup. Check that the same appointment or declined recommendation does not appear twice under different customer references. Review recipients, current vehicle relationships and restrictions before sending. Count records separately from people and appointments. A smaller list is not automatically a better audience if the cleanup removed a legitimate fleet contact.
BlueFinch customer loyalty is an optional paid product with activation and messaging requirements. Its product page does not promise automatic cleanup of your shop CRM. Start with the customer system holding the service history. Bring a verified audience to any communication product, and keep a named owner responsible for correcting records rather than repeatedly editing downloaded lists.
Sources for this section: BlueFinch: Customer loyalty terms and availability
Primary sources
BlueFinch last reviewed these sources on October 3, 2026. Payment rules and state requirements can change.
- HubSpot: Deduplicate records
- HubSpot: Merge records
- BlueFinch: Customer loyalty terms and availability
Use this page for general business information. It is not legal, tax, or accounting advice.