HubSpot lifecycle stages track where a contact or company sits in your funnel — from Subscriber through Lead, MQL, SQL, Opportunity, Customer, and Evangelist. That's the easy part. The hard part is that in most portals, nobody agreed on what those words mean, three forgotten workflows are setting them, and the funnel report they feed is quietly wrong.
If marketing and sales in your company argue about what an MQL is, this post is the meeting you've been avoiding — in written form.
What does each HubSpot lifecycle stage actually mean?
Each stage marks a commitment level: how far this person has moved from stranger toward customer. HubSpot ships defaults, but the definitions only work if your team fills them in with specifics. Here's the framework we give clients:
Subscriber
They opted into content — a newsletter, a blog subscription. They know you exist. That's all you can claim.
Lead
They converted on something more substantial than a subscription: a guide download, a webinar registration. Interest, not intent.
Marketing Qualified Lead (MQL)
Marketing believes this person is worth sales attention, based on criteria both teams agreed to — fit plus meaningful engagement. The agreement is the whole point. An MQL definition written by marketing alone is just a compliment marketing pays itself.
Sales Qualified Lead (SQL)
Sales looked at the MQL and accepted it: right company, real need, worth working. This is a human judgment, and it belongs to sales.
Opportunity
There's an actual deal attached. Ideally this stage is set automatically when a deal is created — no debate required.
Customer
A deal closed won. Also best set automatically.
Evangelist and Other
Evangelist is for genuine advocates — referrers, reviewers, reference customers. Other is the escape hatch for records that don't fit the funnel: partners, vendors, competitors, your own employees.
Who should own each lifecycle stage transition?
Marketing owns the transitions up to MQL, sales owns SQL onward, and automation should handle the mechanical ones. Ambiguity about ownership is where funnels go to die.
- Subscriber, Lead, MQL — set by marketing's rules, ideally via a small number of documented workflows tied to conversion events and scoring.
- SQL — set by a salesperson (or by a rep-triggered action like booking a qualification call). If a workflow is promoting contacts to SQL without a human decision, your SQL count is decorative.
- Opportunity and Customer — set automatically by deal creation and deal closed-won. Removing humans from these two transitions eliminates the most common reporting gaps.
Write the ownership down. One page. Pin it where both teams can see it.
What is the lifecycle stage one-way-street gotcha?
By default, HubSpot only moves lifecycle stage forward — a workflow or sync trying to set a contact from Customer back to Lead will silently do nothing unless you clear the value first. This surprises almost everyone at least once.
It's a sensible default: a customer who downloads an ebook shouldn't demote back to Lead. But it bites you during cleanups and migrations, when you're trying to correct records that were set too far forward by some ancient workflow. To move a stage backward, you have to clear the lifecycle stage value first, then set the correct one — workflows can do both steps. Portal settings can also allow backward syncs in specific cases, but treat backward movement as a deliberate, documented exception, not a routine.
Related gotcha: bulk imports. An import that includes a lifecycle stage column can shove thousands of records forward in one click, and there's no bulk undo. Check that column twice.
How do you fix lifecycle stages that are already a mess?
Fixing broken lifecycle stages is a three-step job: agree on definitions, correct the existing records, then lock down what's allowed to set the field.
- Get the definitions agreed. Marketing and sales, same meeting, one page of definitions with specific criteria for MQL and SQL. This is the step teams skip, and it's why the fix never holds.
- Repair the records. Build filtered views for contradictions — Customers with no closed-won deal, Opportunities with no deal at all, MQLs created before your scoring existed. Fix in bulk where the logic is unambiguous. Remember the one-way street: backward corrections need the clear-then-set pattern.
- Reduce the writers. Inventory everything currently setting lifecycle stage — workflows, integrations, forms, imports, humans — and cut it down to your documented set. A field with twelve writers has no meaning; a field with three documented ones is a reporting asset.
What's the payoff for getting lifecycle stages right?
Trustworthy funnel reporting — conversion rates between stages, velocity through the funnel, and a marketing-to-sales handoff you can actually measure. When lifecycle stage means one thing, you can finally answer the questions leadership keeps asking: how many MQLs became customers last quarter, where do leads stall, and is marketing's definition of qualified producing revenue or just activity.
It also ends the MQL argument, because the argument was never really about leads — it was about the absence of a shared definition. Trade-off worth naming: tighter MQL criteria means fewer MQLs on the dashboard. That dip is honest, and the close rates that follow will defend it.
If your stages are set by workflows nobody remembers and the repair feels bigger than a spare afternoon, our HubSpot team rebuilds lifecycle architecture for clients regularly — definitions, automation, and the cleanup in between. Get in touch and we'll take a look at your funnel.
Frequently Asked Questions
What is the difference between MQL and SQL in HubSpot?
An MQL (Marketing Qualified Lead) is a contact marketing has deemed ready for sales attention based on agreed fit and engagement criteria. An SQL (Sales Qualified Lead) is an MQL that sales has reviewed and accepted as worth pursuing. The key difference is who decides: marketing's rules set MQL, a salesperson's judgment sets SQL.
Can HubSpot lifecycle stages move backward?
Not by default. HubSpot only moves lifecycle stage forward — attempts to set an earlier stage are ignored unless the field is cleared first. To correct a record backward, clear the lifecycle stage value, then set the right one. Workflows can automate both steps, but backward movement should be a deliberate exception.
Who should set lifecycle stages in HubSpot — workflows or people?
Both, with clear ownership. Automation should handle mechanical transitions: conversion-based stages like Lead and MQL, plus Opportunity and Customer via deal creation and closed-won. Humans should own judgment calls, especially SQL. The failure mode is ambiguity — when a dozen undocumented workflows write to the field, it stops meaning anything.