Duplicate customer record merge: 8 checks

Key takeaways for how to merge duplicate customer records in field service software

Housecall Pro provides a new tool that automatically identifies possible duplicate customers and makes it simple to merge them, according to Housecall Pro. HubSpot specifies that records won't appear in the undo list if you make property value or other changes to the records during the 14-day period, according to HubSpot.

• Use the automatic identification tool in Housecall Pro to find potential duplicates before manual review.
• Note that HubSpot removes records from the undo list if you change property values during the 14-day window.
• Verify your specific platform's permissions and undo rules before initiating a merge action.
• Do not assume undo periods are identical across different field service software providers.

Direct answer for merging duplicate records

The eight checks below define the required permissions, identification steps, and constraints for merging duplicate customer records. Each check is tied to a specific platform rule. Before starting any merge action, verify your access level. According to HubSpot, "Merge records or Super Admin permissions are required to merge records." This permission check is the first gate. Without it, the merge function is inaccessible.

The table above lists the eight specific checks. Check 1 confirms the permission requirement. This establishes the baseline access needed. Checks 2 through 8 address the subsequent steps in the workflow. Each step relies on platform-specific behavior. The permission check ensures you can proceed to identification.

Identifying duplicates is the second check. You must locate the records that represent the same client. Selecting the correct record is the third check. You choose which profile remains active. Managing property overrides is the fourth check. This involves setting which data fields take precedence. Checking location constraints is the fifth check. Some platforms restrict merging locations across different customers. Reviewing status flags is the sixth check. Certain flags may persist or change during a merge. Executing the bulk action is the seventh check. This is the actual merge operation. Confirming the undo window is the eighth check. You verify if and when the action can be reversed.

Identifying and selecting the correct records

Before merging, you must correctly identify which record is the duplicate and which is the primary record. In ServiceTitan, the process begins by searching for the customer records you want to merge together and identifying the duplicate, which is the record you intend to remove, according to ServiceTitan. Once located, you must locate and mark the duplicate customer record to prepare it for the merge action, according to ServiceTitan. A recommended editorial step is to open the duplicate record and click Edit next to the customer name to add a clear identifier, such as the word DUPLICATE, before proceeding with the merge, according to ServiceTitan. This labeling helps distinguish the record you plan to remove from the one you will keep.

In HubSpot, the selection process involves a specific dialog box interaction. You must click the dropdown menu in the dialog box, then search for and select the record to merge into the primary record, according to HubSpot. This step ensures that the data from the duplicate is directed to the correct primary profile.

When using ServiceTitan, the final selection step requires precise input in the merge interface. In the Customer to Remove field, you must enter and select the name of the duplicate record, specifically the one you added the word DUPLICATE to, according to ServiceTitan. This confirms that the system will remove the correct profile and retain the primary record.

Managing property overrides and status flags

When merging customer records, the software determines which data fields remain based on specific rules. In HubSpot, the system handles default property selection by keeping the primary record's properties, as these are generally retained following a merge according to HubSpot. This default behavior means the primary record acts as the baseline for the new combined profile. If you need to change which fields are kept, HubSpot allows you to customize this process. You can set up to 20 property overrides on each merge rule according to HubSpot. This limit applies to each individual merge rule you configure, allowing you to specify which properties from the secondary record should overwrite the primary record's values.

Status flags also follow specific logic during a merge. In Housecall Pro, the "Do not service" flag has a particular behavior. If any customer marked as Do not service is merged, the merged customer will also be marked as Do not service according to Housecall Pro. This rule ensures that if one of the duplicate profiles has this restriction, the combined profile inherits it. You should review your customer list for this flag before initiating a merge. If a customer is incorrectly marked as Do not service, you may need to correct that status before merging to avoid carrying the flag onto the new record.

To manage these settings effectively, follow these steps:

1. Check the primary record: Identify which record you intend to keep as the primary profile. In HubSpot, this record's properties are selected by default according to HubSpot.
2. Configure overrides: If you need to keep specific data from the secondary record, use the override settings. Remember that you can set up to 20 property overrides on each merge rule according to HubSpot.
3. Verify status flags: Look for the "Do not service" flag in Housecall Pro.

Handling location and child record constraints

Merging records involves specific structural rules that limit which items can be combined and how related data behaves. Understanding these constraints prevents data loss and maintains record integrity during the cleanup process.

ServiceTitan defines a strict boundary for location records. When merging location records, you can only merge locations that belong to the same customer record ServiceTitan. This rule means that if two location profiles are attached to different customer entries, the platform does not allow them to be merged into a single location profile.

Microsoft describes the behavior of related data during a merge in Power Apps. When you merge a row, any related or child rows are also merged Microsoft. This automatic inclusion means that the merge action is not limited to the primary record you select. Any subordinate records linked to the primary row are processed simultaneously. You do not need to manually select each child row to include it in the merge. The system handles the relationship logic automatically. This behavior requires you to review all related records before merging to ensure that no unintended data is combined or lost.

Bulk actions and undo windows

When you have a list of potential duplicates, you can process them together rather than one by one. According to HubSpot, you can reject, merge, or merge in bulk the potential duplicates identified by the HubSpot default rule. This bulk capability allows office managers to clear out multiple flagged records in a single action, which is useful when a data import or a long period of manual entry has created a large number of near-identical profiles.

Before you commit to a bulk merge, it is critical to understand the constraints on reversing the action. HubSpot provides an undo list for recent merges, but this safety net has a strict condition. According to HubSpot, records won't appear in the undo list if you make property value or other changes to the records during the 14-day period. This means that the window for undoing a merge is not just a matter of time; it is also a matter of inactivity. If you edit a phone number, update a billing address, or modify any other property on the merged records within that 14-day window, the option to undo the merge is removed for those specific records.

Example row for merge verification

Use this example to verify details before finalizing a merge. HubSpot notes that a warning appears if a rule matches more than 10% of all records in your account and the average group size is greater than three, so check your match volume before proceeding HubSpot. The platform also provides similarity options of 30% and up so operations managers can review potential duplicate contacts that aren't immediately identifiable HubSpot. Housecall Pro states that if everything is correct, you click Merge Customers to finalize the merge Housecall Pro. The row labelled Example shows a finished line in plain words.

Review your entries to ensure no rule triggers the HubSpot warning threshold. Confirm that the Housecall Pro merge action is ready to be clicked only after all fields are verified. Keep this sheet with your site records for future reference, next to the Construction Daily Log Checklist for Supervisors and Merge duplicate customer records: 6 rules.

Illustrative example of a small merge review

In this illustrative pass, an office lists 8 possible duplicate pairs. The clerk keeps one primary profile and marks the other as the record to remove. They choose 2 overrides and stay under an illustrative cap of 20. They picture a 14 day window with no edits, so an undo list can still include the profiles. They merge locations only when both sit on the same customer. They pause on a practice rule that covers more than 10 percent of records when the average group is greater than 3. They also look at a similarity cut near 30 percent when a pair is not obvious. They click merge only after those checks agree.

Review your current customer list for obvious duplicates and verify your admin permissions before attempting a merge.

FAQ: How to merge duplicate customer records in field service software

What permissions are required to merge records in HubSpot?

You need Merge records or Super Admin permissions to merge records in HubSpot, according to HubSpot. Verify your access level before attempting a merge action.

Can you merge location records that belong to different customers in ServiceTitan?

No, you can only merge locations that belong to the same customer record, according to ServiceTitan. Cross-customer location merging is not permitted.

What happens to the 'Do not service' flag when merging customers in Housecall Pro?

If any customer marked as Do not service is merged, the merged customer will also be marked as Do not service, according to Housecall Pro.

How many property overrides can you set on each HubSpot merge rule?

You can set up to 20 property overrides on each merge rule, according to HubSpot.

What is the time limit to undo a merge in HubSpot if no changes are made?

Records won't appear in the undo list if you make property value or other changes to the records during the 14-day period, according to HubSpot. Avoid editing merged records to preserve the undo option.