1. Insycle
  2. Merge Duplicates: Find and Merge Duplicate CRM Records
  3. Common Scenarios

Merging Only Groups Where at Least One Record Has a Key Value

header-pizza-merge-machine.png

When deduplicating records in the Merge Duplicates module, not every duplicate group contains the data needed to produce a reliable merged result. Some groups may consist entirely of records in which a critical field — such as a lead score, an assigned account manager, a subscription status, or an integration ID — is empty for every record in the group. Merging those groups risks creating a master record that omits data essential to your business operations.

Insycle's At Least One Record With Non-Empty condition addresses this by requiring that at least one record in a duplicate group contains a value in a specified field. Any group where all records have that field empty is skipped during the merge process.

Configuring the "At Least One Record With Non-Empty" Condition

To set up this condition:

  1. Navigate to Data Management > Merge Duplicates and select your database and object type.
  2. In Step 1, on the Simple tab, configure your matching fields to identify potential duplicates.
  3. Click the Conditions tab.
  4. For the field you want to require a value in, set the Condition to At Least One Record With Non-Empty.
merge-duplicates-hubspot-leads-step-1-conditions-one-non-empty.png

The image above shows the Conditions tab in Step 1 of the Merge Duplicates module, with the Lead Pipeline field set to the At Least One Record With Non-Empty condition.

With this condition in place, Insycle will process duplicate groups only if at least one record has a value in the specified field. Groups where every record has that field empty will be skipped entirely and left for separate review.

Examples of Fields Where This Condition Is Useful

  • Lead Score — skip groups where no record has been scored, since those may not be ready for processing.
  • Account Manager — ensure the merged record will have an owner assigned.
  • Subscription Status — avoid merging groups where billing or subscription data is absent across all records.
  • Integration ID — skip groups where no record has a connection to an external system, ensuring those records are handled separately.

Additional Resources

Frequently Asked Questions

Related Help Articles

Related Blog Posts

Related articles