HubSpot Lifecycle Stages: The Funnel Logic Most Portals Get Wrong
HubSpot lifecycle stages are a default property on contacts and companies that tracks where a record sits in your funnel, from Subscriber through Evangelist. They power funnel reports, lead handoffs, and conversion-rate analysis — and in most portals we audit, they are set inconsistently, skipped entirely, or confused with lead status. Fix your lifecycle stage logic and every downstream report in HubSpot becomes trustworthy; leave it broken and your funnel metrics are fiction.
After auditing hundreds of portals, we can tell you the pattern: sales sets lifecycle stages by gut feel, marketing automation overwrites them, and nobody has written down what "MQL" actually means at the company. This article gives you the complete stage-by-stage reference, clears up the lifecycle stage vs lead status confusion once and for all, and ends with a checklist you can run against your own portal this week.
What Are HubSpot Lifecycle Stages? The Complete Default List
HubSpot lifecycle stages are a single-select default property (lifecyclestage) that exists on both contacts and companies and represents funnel position: Subscriber, Lead, Marketing Qualified Lead, Sales Qualified Lead, Opportunity, Customer, Evangelist, and Other. Each record holds exactly one value at a time, and HubSpot's funnel reports assume records move through the stages in order. The property can be set manually, by forms, by workflows, or automatically by HubSpot when a deal is created or won.
Here is the full default ladder, what each stage should mean, and who (or what) should be responsible for setting it:
| Lifecycle stage | Definition | Who/what sets it |
|---|---|---|
| Subscriber | Opted into blog or newsletter content only; no buying signal | Form submission or workflow |
| Lead | Converted on a non-subscription offer (guide, webinar, contact form) | Form submission or workflow |
| Marketing Qualified Lead (MQL) | Meets your documented marketing qualification bar (fit + engagement threshold) | Workflow, usually triggered by lead scoring |
| Sales Qualified Lead (SQL) | A human in sales has reviewed and accepted the lead as worth working | Sales rep, or workflow on lead-status change |
| Opportunity | An open deal is associated with the record | HubSpot automatically, when a deal is created |
| Customer | At least one deal has been closed-won | HubSpot automatically, when a deal is won |
| Evangelist | Active advocate: referrals, reviews, case-study participation | Manual, by CS or marketing |
| Other | Records that don't belong in the funnel: partners, vendors, investors, employees | Manual or import mapping |
Two of those rows matter more than teams realize. Opportunity and Customer are the only stages HubSpot sets automatically by default (a portal setting you can toggle), which means every stage before them depends entirely on your own discipline. A 40-person SaaS client of ours had 11,000 contacts sitting at "Lead" — including 300 paying customers — because deal-based sync was working fine but nothing had ever promoted anyone to MQL or SQL. Their funnel report showed a 0.4% Lead-to-MQL rate that the board interpreted as a marketing crisis. It was a data-entry crisis.
Book a free HubSpot audit. No onboarding calls, no meetings — click our invitation link to grant partner access to your portal, and we'll send you a full list of improvements within days.
Lifecycle Stage vs Lead Status: The Confusion That Breaks Portals
Lifecycle stage measures funnel position across the entire customer journey; lead status measures the working state of a lead within the sales-owned part of that journey. Lifecycle stage answers "how far has this record progressed?" while lead status answers "what is sales doing with it right now?" They are complementary properties, and using one to do the other's job is the single most common data-model mistake we find in audits.
The confusion is understandable — both properties sound like "where is this lead?" — but they operate on different axes:
| Lifecycle stage | Lead status | |
|---|---|---|
| Question it answers | Funnel position (journey-wide) | Sales working state (right now) |
| Direction | Forward-only (should never regress) | Loops freely (Open → Attempting → Connected → back to Open) |
| Owner | Shared: marketing early, sales mid, system late | Sales exclusively |
| Typical values | Subscriber → Evangelist (fixed ladder) | New, Open, Attempting contact, Connected, Unqualified, Bad timing (customizable) |
| Powers which reports | Funnel and conversion-rate reports | SLA, follow-up speed, and rep-activity reports |
| Can it repeat? | No — a Customer is never a Lead again | Yes — statuses reset with each new sales cycle |
| What "disqualified" looks like | Stays at current stage or moves to Other | Set to Unqualified, with a reason property |
The practical rule: when a rep decides a lead isn't worth pursuing, that's lead status = Unqualified — not a lifecycle demotion. When marketing's score threshold is crossed, that's lifecycle stage = MQL — not a lead status. An enterprise manufacturing client of ours had added "MQL" as a lead status value and used the MQL lifecycle stage, maintained by two different workflows with slightly different criteria. Roughly 20% of records disagreed with themselves, and their marketing-sourced pipeline number changed depending on which property the report used. Pick one axis per property and enforce it in your workflows.
Why You Must Never Skip Lifecycle Stages
HubSpot's funnel reports count a record as having passed through a stage only if the record actually held that stage value at some point — and every stage carries a hidden timestamp property ("Became a Marketing Qualified Lead date," and so on). If a contact jumps straight from Lead to Customer, the MQL, SQL, and Opportunity timestamps are never written, and that contact silently disappears from every intermediate conversion-rate calculation. Skipped stages don't just make reports slightly off; they make cohort funnel analysis structurally impossible.
This is the mechanism most admins miss. The lifecycle stage property itself only shows the current value; the historical funnel is reconstructed from those date-stamped properties. Consequences of skipping:
- Conversion rates overstate or understate wildly. If half your customers never held "SQL," your SQL-to-Customer rate looks superhuman while Lead-to-SQL looks broken.
- Velocity metrics vanish. Time-in-stage calculations need entry timestamps for both stages. No timestamp, no velocity.
- Attribution and lifecycle reporting stop agreeing. Revenue reports show customers your funnel report claims never existed as opportunities.
The standard fix is a "stage stamping" workflow pattern: whenever a record's lifecycle stage is set to a later stage, a workflow briefly checks whether earlier-stage dates are empty and backfills them (or, more simply, you enforce sequential movement in the workflows that promote records so skipping can't happen going forward). One important HubSpot behavior helps you here: by default, HubSpot will not let automation move a lifecycle stage backward — a stage can only be reset by clearing it first. Treat that as a feature. Forward-only is exactly the discipline the funnel model needs. If you're rebuilding this from scratch, our HubSpot implementation guide covers the correct build order.
Automation That Moves Lifecycle Stages (and What to Never Automate)
The reliable pattern is: automate every promotion that has an objective trigger, and reserve exactly one stage — SQL — for human judgment. Forms and workflows should set Subscriber and Lead, a scoring-driven workflow should set MQL, sales acceptance should set SQL, and HubSpot's native deal sync should own Opportunity and Customer. Portals fail when humans are asked to remember stages that a workflow could set, or when workflows set stages that require judgment.
A concrete automation map that works in most B2B portals:
- Subscriber: set by newsletter/blog form submissions (form options or a simple workflow).
- Lead: set on first non-subscriber conversion. Most portals can rely on HubSpot's default behavior here and only add workflows for edge cases (imports, integrations).
- MQL: one workflow, triggered by your score threshold or a high-intent action (demo request, pricing page + form). This is where lead scoring earns its keep — the score is the input, the lifecycle stage is the output.
- SQL: the one deliberate manual step. Best practice: the rep sets lead status to "Connected/Qualified," and a workflow translates that into lifecycle stage = SQL. The human makes the call; the automation does the data entry.
- Opportunity / Customer: leave HubSpot's automatic deal-based sync on (Settings → Objects → Contacts & Companies → lifecycle stage sync). Never build a competing workflow — dueling automations are how records flap between stages.
- Evangelist: manual only, or triggered by concrete events (submitted a review, referred a signed customer).
Also decide your company-to-contact sync policy: by default, updating a company's lifecycle stage can cascade to its contacts. That's usually right for Customer (everyone at a customer account is a customer) and usually wrong for MQL (one engaged contact doesn't qualify their 40 colleagues). Audit which direction your portal syncs before you trust any account-level funnel report — it's one of the first things we check in a HubSpot audit.
Custom Lifecycle Stages: Pros and Cons
HubSpot lets you rename, remove, and add custom lifecycle stages (available on higher-tier subscriptions — check HubSpot's current pricing page), and the honest guidance is: customize less than you want to. Custom stages are worth it when your business model genuinely doesn't map to the default ladder — PLG products with a "Product Qualified Lead" stage, or businesses with a formal "Onboarding" phase between won and live. They are a liability when they encode one team's vocabulary into a portal-wide property that every report, integration, and future hire must now decode.
| Pros of custom stages | Cons of custom stages | |
|---|---|---|
| Fit | Model PQL, Onboarding, Churned, or partner-specific journeys precisely | Default stages already fit ~80% of B2B funnels |
| Reporting | Funnel reports mirror how leadership actually talks about the funnel | Benchmarks and templates assume default stages; comparisons get harder |
| Integrations | — | Salesforce sync, attribution tools, and many apps expect default internal values; custom values need mapping everywhere |
| Maintenance | — | Every added stage needs an owner, entry criteria, and automation — forever |
Rules of thumb from our audits: never delete Opportunity or Customer (they're wired to deal automation); add at most one or two stages, each with a written definition and an automated or clearly owned entry trigger; and if the thing you want to track can loop or repeat — "Renewal," "At Risk" — it belongs in a custom property or a deal pipeline, not the lifecycle ladder. Lifecycle stages are forward-only by design; anything cyclical will fight the model.
HubSpot Lifecycle Stages Best Practices: The Fix-It Checklist
The fastest way to repair lifecycle stages is to define each stage in writing, backfill the obvious wrong values, and then automate promotions so drift can't recur. Run this checklist in order — definitions before data before automation — because automating an undefined stage just produces wrong values faster.
- Write a one-line definition for every stage you use, including the objective trigger for entry (e.g., "MQL = score ≥ 50 or demo request"). Get marketing and sales to sign the same document.
- Decide the lifecycle stage vs lead status split and remove any lead status values that duplicate lifecycle stages (and vice versa).
- Audit current data: build a simple report of contact count by lifecycle stage. Investigate anything implausible — thousands of blank values, customers stuck at Lead, or an empty MQL bucket.
- Fix the automatic sync settings: confirm deal-created → Opportunity and deal-won → Customer are on, and consciously choose your company→contact cascade behavior.
- Backfill the worst offenders: list-based bulk updates for paying customers not marked Customer, and "Other" for partners, vendors, and employees polluting the funnel.
- Build (or consolidate to) one promotion workflow per stage — one for MQL, one that maps sales acceptance to SQL. Delete competing workflows that touch
lifecyclestage. - Stamp the dates: verify "Became an X date" properties are populating for new records; add backfill logic if stages were being skipped.
- Lock down manual edits where possible (property-level permissions, available on higher-tier subscriptions) so reps change lead status, not lifecycle stage.
- Set a quarterly review: re-run the stage-distribution report and spot-check 20 records per stage against your written definitions.
FAQ
Can a HubSpot lifecycle stage move backward?
Not by default — HubSpot blocks backward moves from automation and syncs unless the value is cleared first. This is intentional: lifecycle stages model cumulative funnel progress, not current status. If you need a "regressed" state (a churned customer, a recycled lead), track it with lead status or a custom property rather than demoting the lifecycle stage.
What's the difference between lifecycle stage and lead status in HubSpot?
Lifecycle stage is the forward-only, journey-wide funnel position (Subscriber → Evangelist); lead status is sales's working state on a lead right now (Open, Attempting contact, Connected, Unqualified) and can loop freely. Use lifecycle stage for funnel and conversion reporting, lead status for follow-up and SLA reporting.
Which lifecycle stages does HubSpot set automatically?
Out of the box, HubSpot sets Opportunity when a deal is created with an associated contact/company, and Customer when a deal is closed-won — both controlled by a toggle in your object settings. Every other stage (Subscriber, Lead, MQL, SQL, Evangelist, Other) only changes when your forms, workflows, imports, or users change it.
Should I create custom lifecycle stages?
Only if your business model genuinely breaks the default ladder — a PQL stage for product-led growth or an Onboarding stage are legitimate cases. Keep additions to one or two, write entry criteria for each, never remove Opportunity or Customer, and remember that Salesforce sync and many integrations expect the default values.
How do I fix thousands of contacts with the wrong lifecycle stage?
Define your stages in writing first, then bulk-correct in order of certainty: active customers → Customer, partners/vendors/employees → Other, then score- or activity-based lists for MQL. Fix the automation that caused the drift before you backfill, or the bad values will simply regenerate.
Lifecycle stages are the spine of every funnel number your leadership team looks at. If the spine is bent, everything downstream — attribution, forecasting, marketing ROI — inherits the bend. Straighten it once, automate it properly, and the property maintains itself.
Book a free HubSpot audit. No onboarding calls, no meetings — click our invitation link to grant partner access to your portal, and we'll send you a full list of improvements within days.
