Take Control of Lifecycle Stage When Merging HubSpot Duplicates

HubSpot enforces a strict rule for Lifecycle Stage: it can only move forward in the funnel. When duplicates are merged — whether directly in HubSpot or through Insycle's native merge — HubSpot automatically keeps the stage furthest down the funnel, no exceptions. If your master record is a Lead but another duplicate is a Customer, the merged record becomes a Customer, regardless of your intent.

For teams that need to retain an earlier Lifecycle Stage after a merge — for example, to flag a record for re-nurturing or to match an internal classification — there was previously no way to override this.

Insycle now lets you control exactly which Lifecycle Stage is retained using Native merge, even if it's earlier in the funnel than the default HubSpot behavior would select. You can designate a specific stage from either the master record or any duplicate in the group, and Insycle will apply it to the merged record — bypassing HubSpot's usual funnel-progression rule. This applies to HubSpot contacts and companies.

For example, if your master record is tagged as Lead and a duplicate is tagged as Customer, Insycle can retain Lead on the merged record — something that isn't possible when merging directly in HubSpot.

To use this, go to the Merge Duplicates module, under 3. Merge Logic on the Method tab, make sure your Merge API is set to Native, and then set your Lifecycle Stage selection rule on the Fields tab.

Learn more about merging duplicates in HubSpot.