HubSpot Lifecycle Stages: How They Work and How to Keep Them Accurate

What are HubSpot lifecycle stages?

HubSpot lifecycle stages are the values of a default property, Lifecycle stage, that records where a contact or company sits in your relationship with them, from first sign-up to paying customer. Out of the box, HubSpot provides seven stages in this order:

1. Subscriber: has opted in to hear from you, usually a blog or newsletter signup.
2. Lead: has shown more interest than a subscriber, for example by filling in a content or contact form.
3. Marketing Qualified Lead (MQL): marketing considers them ready for sales attention.
4. Sales Qualified Lead (SQL): sales has accepted them as a real prospect.
5. Opportunity: associated with a deal.
6. Customer: has at least one closed won deal.
7. Evangelist: a customer who actively advocates for you.

There’s also Other, for records that don’t fit any stage, such as partners, suppliers or job applicants.

The stage names come with HubSpot. The definitions behind MQL and SQL don’t. HubSpot can’t decide what “marketing qualified” means for your business, and this is where most lifecycle problems begin.

Define each stage before you automate it

Before touching settings, write a one-line entry rule for each stage you use. For example:

• Lead: submitted any form other than newsletter signup.
• MQL: lead score reached the agreed threshold, or requested a demo.
• SQL: a sales rep has reviewed the record and confirmed fit.
• Opportunity: a deal exists in the sales pipeline.
• Customer: a deal has been closed won, or an active subscription exists in billing.

Agree these with sales and marketing together. If marketing counts MQLs by score and sales thinks an MQL means “someone asked to talk to us”, every funnel report will cause an argument.

You also don’t need every stage. Plenty of B2B companies skip Subscriber or Evangelist entirely. An unused stage is better than a stage everybody interprets differently.

How do lifecycle stages move forward?

HubSpot’s automatic updates only ever move lifecycle stages forward. Forms, imports, integrations, the API and workflows can all set a later stage, but none of them can set an earlier stage while a value already exists. That protects you from a newsletter signup downgrading a customer to subscriber. It also means records won’t move back on their own.

Several settings change stages automatically. You’ll find them under Settings > Data Management > Objects > Contacts, on the Lifecycle Stage tab:

• Set lifecycle stage when a contact or company is created (Pipeline Rules tab) assigns a default stage to new records. Forms can also set their own default, which overrides it.
• Sync lifecycle stages (Automate tab) copies the primary company’s stage to its associated contacts. The sync only goes one way, from company to contact.
• Set lifecycle stage when a deal is created moves associated contacts and companies to a stage you choose when their first deal is created.
• Set lifecycle stage when a deal is won does the same when an associated deal closes as won.
• Set lifecycle stage when a lead is associated applies a stage when a record from HubSpot’s leads object is associated with the contact.

Because these settings respect the forward-only rule, they won’t pull anyone back. If a company is set to Lead, a contact at Subscriber moves up to Lead, while a contact already at Opportunity stays where it is.

These settings are useful but blunt. Imagine a company is marked as Customer. With sync turned on, every contact at that company becomes a Customer too, including the ex-employee, the agency contact and the person from accounts who only ever received invoices. Your “customer” segment now contains people who’ve never bought or used anything.

Can HubSpot lifecycle stages move backward?

Yes, but only when you do it deliberately. There’s no setting that lets stages move backward automatically. To set an earlier stage, you either change the value directly or clear the existing value first and then set the new one.

The options:

• Manually on a record. Open the record and choose an earlier stage. This works without clearing.
• Bulk edit from a list or index page. Select records, click Edit, choose Lifecycle stage and pick the value.
• Import. Imports only move stages forward, so clear the lifecycle stage on those records before importing the earlier value.
• Workflow. Use two Edit record actions in a row. The first sets Lifecycle stage with Clear existing property value ticked. The second sets the new stage. Workflows need a Professional or Enterprise subscription.
• Integrations that sync the property, such as Salesforce, can also set it.

Check the property history on any record to see which source made each change. It’s the fastest way to find out why a contact landed in the wrong stage.

When should a record move backward?

Move a record backward when its old stage would cause the wrong action. The usual case is a lost deal. A contact whose only deal was closed lost is no longer an opportunity, and leaving them there keeps them out of nurture and inflates pipeline-stage reports. A workflow triggered by deal stage = closed lost can clear the stage and set it back to Lead (or MQL, if that’s how you treat recycled leads).

Churned customers need more thought. Some teams move them back to Lead. Others add a custom stage like “Former customer”, or keep the Customer stage and track status separately with a property such as “Customer status: active / churned”. The right answer depends on what your reports and workflows need to know. Moving a churned customer back to Lead makes them look like a new prospect, which can distort acquisition reports.

What happens to stage dates when you move backward?

HubSpot keeps two kinds of date property for each stage. Date entered [stage] and Date exited [stage] record transitions and aren’t wiped when a record moves back. Latest time in [stage] and Cumulative time in [stage] track how long records spend in each stage; these need a Professional or Enterprise subscription.

The older Became a [stage] date properties behave differently. When you set an earlier stage, the date for the later stage is cleared. If any of your reports or workflows still use the “Became a…” properties, check them before you start moving records backward.

Lifecycle stage vs lead status

Lifecycle stage describes where someone is in the overall relationship. Lead status describes what sales is doing with them right now. HubSpot treats lead status as a set of sub-stages within Sales Qualified Lead. Its default values are New, Open, In Progress, Open Deal, Unqualified, Attempted to Contact, Connected and Bad Timing, and you can edit them.

In practice, lifecycle stage answers “what kind of record is this?” and lead status answers “where is the sales conversation?” A record can be an SQL with lead status Attempted to Contact for a week, then Connected, then Open Deal, all without its lifecycle stage changing until a deal is created.

Trouble starts when the two contradict each other, like a Customer with lead status New, or an MQL with lead status Open Deal. Usually that means one property is updated by automation and the other by hand, and nobody has defined which takes priority. A simple rule set helps:

• lead status is only used while a record is MQL or SQL
• moving to Opportunity sets lead status to Open Deal
• marking a lead Unqualified triggers a decision: back to nurture, or to Other

HubSpot’s Sales Hub also has a separate leads object with its own lead pipeline and stages, which some teams use for prospecting work in place of lead status. If you use it, decide which one your reps update and which one reports read from. Two properties tracking the same thing will drift apart.

Why are HubSpot lifecycle stages inaccurate?

They’re usually inaccurate because several tools write to the same property and nothing moves records back. The most common causes we find:

• Form defaults. A form sets new contacts to Lead or MQL regardless of what they actually did.
• Imports. A trade-show list is imported with every row marked as Lead, or an old CRM export marks everyone as Customer.
• Company sync. Every contact at a customer company becomes a Customer.
• Deal creation. Every contact associated with a deal becomes an Opportunity, even people who were only copied on emails.
• No backward path. Lost deals and churned customers never leave their stage.
• Competing workflows. One workflow sets MQL on score, another sets it on demo request, and a third resets it after a property change.

The fix is rarely another workflow. Start by listing everything that writes to Lifecycle stage. The Used In column on the Lifecycle Stage settings tab shows where each stage is referenced in lists, reports and views. Then compare that list against your written definitions and remove or change anything that doesn’t fit.

Customizing stages

Users with Super Admin permissions can add, rename and reorder lifecycle stages from the same settings tab. A stage can’t be deleted while records are in it, while it’s referenced elsewhere in HubSpot, or while it’s the default for a connected app. Move the records and remove the references first.

Customize carefully. Renaming “Evangelist” to “Advocate” is harmless. Inserting a stage between SQL and Opportunity changes the order every forward-only rule depends on, so check your workflows, forms and sync settings afterward.

A short checklist

• Each stage you use has a written entry rule that sales and marketing have both agreed.
• Every form, import template, integration and workflow that sets the stage is listed.
• Default stage settings for new records, deals and company sync match your definitions.
• Lost deals and churned customers have a deliberate path, and it’s documented.
• Lead status values are only used where they make sense, and don’t contradict the stage.
• Reports use the Date entered / Date exited properties rather than the older “Became a…” dates.

If you’re reviewing lifecycle stages as part of a wider clean-up, our walkthrough on how to audit your CRM covers the data, automation and reporting checks that sit around it. For a broader view of the platform, see our HubSpot page.