Skip to content
Book a build

Why does a contact's lifecycle stage keep changing in HubSpot?

A HubSpot lifecycle stage keeps changing because several tools can write it: lifecycle automation settings (deal created, deal won, company sync), forms, imports, integrations and workflows. A stage that goes backward almost always means something cleared the value and then set an earlier one. Open the contact's property history: the Source column tells you which tool made each change.

On this page

What HubSpot does natively

Lifecycle stage has more writers than almost any other property.

WriterWhen it changes the stageCan it go backward?
Sync lifecycle stages (company to contact)When a primary company is associated, or its stage changesNo: the setting won’t set values backwards
Set stage when a deal is created / wonWhen the first deal is created, or a deal is closed wonNo
Set stage when a lead is associatedWhen a lead record is associatedNo
Default stage on createWhen a contact or company is createdNot applicable
Forms, imports, API, integrationsOn submission, import or syncOnly forward, unless the value is cleared first
WorkflowsOn the Edit record actionOnly forward; a workflow can clear the value, then set an earlier one
Manual editWhenever a user changes itYes

Two rules explain most surprises. HubSpot tools only move the default lifecycle stage forward. And anything that clears the value first removes that protection, so a workflow that clears and resets the stage can move contacts backward at scale.

How to find what keeps changing the lifecycle stage

  1. Open one affected contact and view the property history for Lifecycle stage. Each row shows the value, the date and the source.
  2. Look for a clear right before the backward change. An empty value followed by an earlier stage is the signature of a workflow or integration resetting it.
  3. Check the automation settings under Settings > Objects > Contacts > Lifecycle Stage. Note which deal, lead and company-sync settings are on.
  4. List every workflow that writes Lifecycle stage. Start from the property’s usage view and open each workflow. See which workflows use or edit a property.
  5. Check integrations that sync lifecycle stage, and any import that included the column.
  6. Pick one owner. Decide which tool sets each stage and turn the rest off, or have them set a flag property the owner reads.

Common mistakes

  • Two workflows with opposite rules. One promotes contacts to MQL on a score; another resets them to Lead when the score drops. Both are working as configured.
  • Company sync plus contact-level workflows. A company change overwrites what the contact workflow set.
  • Fixing the symptom. Adding a third workflow to “correct” the stage creates a loop. See how to set lifecycle stage with a workflow.

Where Jetstack AI fits

A Jetstack AI Workflow Audit flags competing actions, for example two workflows setting lifecycle stage to different values for the same contacts, and shows every workflow that writes the property. The findings describe configuration, not which records actually collided, so confirm with property history before you change anything. See how conflicts are reported.

Once you’ve picked one owner per stage, build that owner workflow with Jetstack AI Projects. Write each stage’s entry rule in the brief, review the plan, approve generation, then approve deployment separately and check the receipt read back from HubSpot. Projects doesn’t edit the competing workflows: it creates the replacement switched off, and you turn the old ones off in HubSpot once it’s tested. Projects is currently in limited release; see what Projects can build.

Sources

Checked October 29, 2026. HubSpot changes its products often; tell us at team@jetstack.ai if something here is out of date.

Workflows & automation

See what needs work before you change it.

A read-only Portal Audit and Workflow Audit score the portal, trace dependencies and turn findings into a branded report.

Explore Portal Audit

Workflows & automation

Related questions.

Why does a contact's lifecycle stage keep changing in HubSpot?

A HubSpot lifecycle stage keeps changing because several tools can write it: lifecycle automation settings (deal created, deal won, company sync), forms, imports, integrations and workflows. A stage that goes backward almost always means something cleared the value and then set an earlier one. Open the contact's property history: the Source column tells you which tool made each change.

Why does my contact's lifecycle stage match its company?

Probably the Sync lifecycle stages setting. When it's on, a change to the primary company's stage updates its associated contacts. It's one-way: changing a contact doesn't change the company.

Can a workflow move lifecycle stage backward?

Not in one step. HubSpot tools, workflows included, only move the default lifecycle stage forward. To set an earlier stage, a workflow has to clear the value first and then set the new one.

Why didn't my workflow change the lifecycle stage at all?

If the new value is earlier than the current one, the action fails with an error saying it would have set the stage backwards. Check the workflow's action log.