Choose Your Merge Strategy: More Control for Complex Duplicate Scenarios

When merging duplicates, the right merge method depends on your CRM setup, the object types involved, and the level of control you need over the outcome. Until now, that choice has happened behind the scenes. The new Merge API setting — found on the Method tab in Step 3: Merge Logic — puts it in your hands.

Available for HubSpot and Salesforce users, the Merge API lets you choose between two merge approaches: Native, which uses your CRM's built-in merge logic, and Synthetic, which uses Insycle's custom merge logic for greater control over field retention, master record selection, and complex associations.

Insycle selects a sensible default based on your platform and object type — for example, Native is the default for HubSpot Contacts and Salesforce Contacts, Leads, and Accounts, while Synthetic is the default for object types that don't have native CRM merge support. But now you can override that default when your use case calls for it.

For example, a user merging HubSpot Contacts might switch from Native to Synthetic merge because they need the master record's ID to remain unchanged — such as when that record ID is referenced in an external system and changing it would break the connection.

Learn more:

• Native Merge vs. Synthetic Merge behavior in HubSpot
• Native Merge vs. Synthetic Merge behavior in Salesforce