Retain a specific HubSpot Lifecycle Stage during a Native merge, even when it is earlier in the funnel than HubSpot's default behavior would select.
HubSpot treats Lifecycle Stage as a protected field. By design, HubSpot only lets Lifecycle Stage move forward in the funnel—a contact or company cannot be set to an earlier stage without first clearing the existing value. When duplicate contacts or companies are merged, HubSpot enforces this rule automatically: it always keeps the Lifecycle Stage furthest down the funnel, regardless of which record is selected as the master.
Insycle lets you override HubSpot's default Lifecycle Stage behavior during a Native merge. By adding a field retention rule for Lifecycle Stage in 3. Merge Logic of the Merge Duplicates module, you can specify which stage to retain after the merge—including a stage earlier in the funnel than HubSpot would otherwise select. This applies only to HubSpot contacts and companies.
Retaining a Specific Lifecycle Stage During a Merge
- Navigate to Data Management > Merge Duplicates and select your HubSpot database and object type (Contacts or Companies).
- In 1. Find Duplicates, configure your matching fields to identify potential duplicates, then click Find.
- In 2. Review Duplicates, review the duplicate groups to confirm the results look correct before proceeding.
- In 3. Merge Logic, click the Method tab and confirm the Merge API is set to Native.
- Click the Fields tab, then click Add Rule.
- Under Field Name, select Lifecycle Stage.
- Under Criteria, select the option that matches how you want the stage to be determined.
- If applicable, set a Condition to further specify which value to retain.
The image above shows the Fields tab in 3. Merge Logic of the Merge Duplicates module, with Lifecycle Stage configured using the 'From record based on other field value' criteria, with Create Date as the Other Field and earliest as the Condition.
Choosing a Criteria for Lifecycle Stage
The right Criteria depends on how you want Insycle to determine which stage to keep. The most common options for Lifecycle Stage are:
From master record — Retains the Lifecycle Stage from whichever record is selected as the master. Use this when your master selection rule already identifies the record with the correct stage.
From record where value — Selects the stage from the record in the duplicate group whose Lifecycle Stage matches a condition you specify. For example, retain the stage from the record where Lifecycle Stage is Lead.
From record based on other field value — Uses a different field to determine which record's Lifecycle Stage to keep. For example, retain the Lifecycle Stage from the record with the earliest Create Date.
Most frequent value — Keeps whichever Lifecycle Stage appears most often across the records in the duplicate group.
For full descriptions of all available criteria and condition options, see Keeping the Right Data When Records Merge.
Additional Resources
FAQs & Troubleshooting
- Check out the Merging Duplicates FAQs for a complete list of questions about merging HubSpot duplicates.
- Review the Merge Duplicates Troubleshooting article if you're not seeing the results you expect when merging records.
Related Help Articles