Lifecycle stage is the single most-referenced property in a typical HubSpot account, and the one most likely to be quietly wrong. It drives list segmentation, workflow enrollment, funnel reports, and the handoff between marketing and sales. It is also a plain dropdown field that anyone can edit, which is exactly how a database ends up with 4,000 contacts sitting at Lead forever and a funnel report nobody trusts.
This guide covers what HubSpot lifecycle stages actually are, the eight defaults and what each one should mean, how lifecycle stage differs from deal stage and lead status (the distinction that trips up most teams), the automation settings that are off until you turn them on, how to create custom stages, and the mistakes that produce funnel data you have to hand-correct.
In this article
1.
2.
3.
4.
5.
6.
7.
8.
9.
What HubSpot lifecycle stages actually are
Lifecycle stage is a single dropdown property, internal name lifecyclestage, that exists on both the contact and company objects. It answers one question: how far along is this person or account in the journey from stranger to customer.
It is not a pipeline. It is not a status. It is a coarse position marker, and it is deliberately coarse, because it has to hold up across marketing reporting, sales handoff, and revenue attribution all at once.
Segmentation
Nearly every useful list in HubSpot filters on lifecycle stage. "MQLs created this month" is a lifecycle stage filter.
Workflow enrollment
Workflows commonly trigger on a lifecycle stage change, which is how a contact hitting MQL fires a sales notification.
Funnel reporting
HubSpot's funnel reports count records by stage. If the stage is wrong, the funnel is fiction.
Calculated date properties
HubSpot automatically stamps a "became a X date" property for each stage, which is what velocity reporting runs on.
The 8 default HubSpot lifecycle stages
HubSpot ships eight stages out of the box, in this order:
-
Subscriber. They opted in to hear from you. A blog subscriber. No buying signal whatsoever.
-
Lead. They converted on something more meaningful than a newsletter. A content download, a webinar, a pricing page form.
-
Marketing Qualified Lead. They cleared whatever bar marketing set. This is the first stage where the definition is yours rather than HubSpot's.
-
Sales Qualified Lead. Sales looked at them and agreed they are worth real time. The handoff has been accepted, not just offered.
-
Opportunity. An active deal exists. Someone is working a real revenue opportunity.
-
Customer. Closed won. They pay you.
-
Evangelist. A customer who actively refers you. Very few teams use this stage honestly, and that is fine.
-
Other. The catch-all. Partners, job applicants, vendors, competitors browsing your pricing page. Anyone who should not pollute the funnel.
Stages 1 and 2 are HubSpot's definitions. Stages 3 onward are yours, and nobody will tell you if you get them wrong.
The defaults are genuinely good, and unlike HubSpot's default deal stages, most teams should keep them. The failure mode here is almost never the stage list. It is that MQL means three different things to three different people.
Lifecycle stage vs deal stage vs lead status
This is the distinction worth getting right, because all three fields look like "how far along is this" and they answer different questions.
Lives on the contact and company. One value per record. Describes the relationship, not any single transaction.
Lives on the deal. A contact can be attached to several deals at different stages while holding one lifecycle stage.
Lives on the contact as a sub-status. New, Attempted to Contact, Connected, Unqualified. It cycles; lifecycle stage does not.
The clean mental model: lifecycle stage is the relationship, deal stage is the transaction, lead status is the touch. A repeat customer with two open renewals has one lifecycle stage (Customer) and two deal stages (whatever each renewal is doing). Trying to encode all of that in lifecycle stage is how teams end up inventing stages like "Customer with open upsell" and then wondering why the funnel report double-counts.
For more on how the underlying fields work and how to name them, see the guide to HubSpot contact properties.
The lifecycle stage automation settings are off by default
Here is the part that catches nearly everyone. HubSpot has a set of built-in lifecycle stage automations, and none of the important ones are enabled out of the box. Teams assume the CRM is setting stages for them, never check, and six months later every contact is still sitting at Lead.
The settings live in Settings, Data Management, Objects, Contacts, Lifecycle Stage. The toggles available:
Set lifecycle stage when a contact or company is created
Pick the stage every new record lands on. Usually Lead or Subscriber.
Set lifecycle stage when a deal is created
Move associated contacts to a stage (typically Opportunity) the moment a deal is created against them.
Set lifecycle stage when a deal is won
Move associated contacts to Customer on closed won. This is the one whose absence is most obvious in reporting.
Set lifecycle stage when a lead is associated
Move the record when a lead object gets attached.
Sync lifecycle stages
Apply the primary company's lifecycle stage down to its associated contacts, so the account and its people agree.
Turn on the deal-created and deal-won toggles at minimum. Those two cover the transitions that matter most and that reps will never do by hand reliably. The broader problem of reps not maintaining the CRM is worth solving structurally rather than through nagging, which the guide on getting sales reps to actually update HubSpot digs into.
Why lifecycle stages only move forward
HubSpot's lifecycle stage settings will never set a stage backwards. This is deliberate and it is the right default, but it surprises people.
If a contact is already at Customer and a new deal gets created against them, the deal-created automation will not knock them back to Opportunity. The stage holds. Same for every other built-in setting.
The consequence: if you genuinely need to move a record to an earlier stage, you have to clear the existing value first, then set the new one. In a workflow that is two actions, a clear followed by a set. Skip the clear and the workflow will appear to run successfully and change nothing at all, which is a genuinely annoying thing to debug.
- 1
Clear the property
Add a "Clear property value" action targeting Lifecycle stage.
- 2
Set the new stage
Add a "Set property value" action with the earlier stage you want.
- 3
Order them correctly
The clear has to come first. Reversed, the set gets ignored and nothing appears to happen.
How to create custom lifecycle stages
Custom lifecycle stages are available on all products and plans, which contradicts a lot of the advice floating around claiming they are Enterprise-only. What you do need is Super Admin permissions.
- 1
Open object settings
Go to Settings, then Data Management, then Objects.
- 2
Select Contacts
Click the "Select an object" dropdown and choose Contacts.
- 3
Open the Lifecycle Stage tab
Find the lifecycle stage configuration panel.
- 4
Create the stage
Enter a name and click Create lifecycle stage. HubSpot generates the calculated date properties for it automatically.
- 5
Reorder if needed
Drag stages into the right sequence. Order matters, because forward-only movement is evaluated against it.
Common HubSpot lifecycle stage mistakes
Assuming the automations are on
They are not. This single assumption accounts for more broken HubSpot funnels than anything else on this list.
Using lifecycle stage as a pipeline
Adding stages like "Demo Booked" or "Proposal Sent" duplicates the deal pipeline in a field that only holds one value and only moves forward. Put that in deal stages.
No written definition of MQL and SQL
If marketing and sales cannot state the bar in one sentence each, the funnel report between those two stages is measuring disagreement, not demand.
Forgetting the clear step
Workflows that set a stage backwards without clearing first fail silently. Nothing errors. Nothing changes.
Ignoring Other
Partners, applicants, and vendors sitting at Lead inflate the top of the funnel permanently. Route them to Other.
Before you trust your funnel report
- The lifecycle stage settings page has been opened and the deal-created and deal-won toggles are on.
- MQL and SQL each have a one-sentence definition both teams have seen.
- Non-buyers (partners, applicants, vendors) are routed to Other, not Lead.
- Any backwards-moving workflow clears the property before setting it.
- Company records carry a lifecycle stage, not just contacts.
Keep the Context Behind Every Stage Change
A lifecycle stage tells you where a contact is. It never tells you why. NoteLinker surfaces your Notion notes right on the matching HubSpot contact and deal records, so the reasoning behind the stage sits next to the stage itself.
Pulling it all together
Lifecycle stages are simple enough that most teams never audit them, and load-bearing enough that when they drift, everything downstream drifts with them. The three things that matter: open the settings page and turn on the automations HubSpot left off, write down what MQL and SQL mean so the field measures reality instead of opinion, and keep lifecycle stage on the relationship rather than trying to make it do the deal pipeline's job.
Do those and the funnel report becomes something you can act on. Skip them and you get what most accounts have, which is thousands of contacts frozen at Lead, a Customer count that lags closed won by however long it takes someone to notice, and a marketing-to-sales conversation that relitigates the definition of MQL every quarter.
