HubSpot, RevOps

HubSpot lifecycle stages: how to define and enforce them

Posted 16 Nov, 2026 by

Every HubSpot portal has lifecycle stages. Almost none have a written definition of what moves a record into each one, who owns the record once it arrives, and when it is allowed to move back. That gap is why marketing and sales argue about MQL (marketing qualified lead) volume and why the funnel report cannot be trusted at board level.

The fix is a one-page definitions table, agreed by the heads of marketing and sales, and three portal settings that enforce it. Here is what the table should say and where most portals go wrong.

 

What should each HubSpot lifecycle stage mean?

Each stage is a statement about the relationship, set by a specific event, owned by a specific team. If you cannot name the event and the owner, the stage is decoration.

Subscriber is someone who has opted into content and nothing more. Set by a newsletter or blog subscription form. Owned by marketing. Lead is anyone who has converted on a form or been created by sales or an integration and is not yet qualified. Set on creation. Owned by marketing until qualified.

Marketing Qualified Lead (MQL) is a lead who has met the agreed qualification threshold and is ready for sales to work. Set by one determinant, covered below. Owned by sales from the moment it is set, with a response-time expectation attached.

Sales Qualified Lead (SQL) is an MQL that sales has spoken to and confirmed there is a real problem, a plausible fit and a reason to continue. Set by a rep changing lead status to Qualified. Owned by sales.

Opportunity is a contact associated with an open deal. Set automatically when the deal is created. Customer is a contact associated with a closed-won deal, set automatically on close.

Evangelist is a customer who actively refers or advocates, set manually and rarely. Other is for anyone who will never buy: partners, vendors, investors, employees, competitors. Other is the most under-used stage in HubSpot, and it is why so many funnels carry hundreds of records that were never leads.

 

What should set the MQL stage in HubSpot?

One determinant, and only one. Either a HubSpot lead score crossing a threshold, or an explicit hand-raise such as a demo request or pricing enquiry. Never a generic form fill, and never solely a rep's instinct.

Portals that let three different workflows set MQL end up with three different definitions and no way to report on any of them. Pick the determinant, write it down, and build one workflow that sets the stage. If the determinant is score, the score needs to be built from real conversion data rather than gut feel. If it is a hand-raise, the qualifying forms need to be named and the rest excluded.

The MQL definition is also where the handover is designed. What sales does in the first hour after a contact becomes MQL, and what happens if they do not, is the part most portals get wrong.

 

Lifecycle stage vs lead status in HubSpot

Lifecycle stage describes where the relationship is. Lead status describes what sales is doing about it right now. They answer different questions and they should never be used to mean the same thing.

A contact can be an MQL with a lead status of New, Attempting, Connected, or Unqualified. The lifecycle stage only changes when the relationship changes, when the rep qualifies the contact and moves lead status to Qualified, which is the trigger for SQL. Portals that skip lead status and try to run the working funnel through lifecycle stage alone end up with a stage called Sales Accepted that nobody can define.

 

Which HubSpot lifecycle stage settings stop the funnel report lying?

Three settings and one rule. Get them right and most of the reporting problems disappear without a data clean-up.

First, in the lifecycle stage settings, decide whether the company stage syncs from contacts and whether contact stage syncs from the company. The default sync behaviour surprises people: a single new contact at an existing customer can push a company back to Lead if the settings are wrong. Second, keep the setting that sets Opportunity on deal creation and Customer on closed won switched on, and do not build workflows that duplicate it. Third, use the lifecycle stage pipeline rules to stop records being moved backwards by hand. HubSpot’s own automation only moves stages forward, so a customer who fills in a webinar form will not revert to Lead, but a manual edit or an integration can undo that unless the rule is on.

The rule is that lifecycle stage moves backwards only by deliberate decision, cleared and reset by a workflow with a written reason. Recycled MQLs, churned customers and disqualified leads each need an explicit path, or the funnel counts them twice.

 

How to audit how lifecycle stages are set in HubSpot

Run a Change Source analysis before you touch anything. Build a contacts report on Lifecycle stage with the property history, and look at what set each stage: form submission, workflow, import, integration, or a user. Most portals discover that a third of their MQLs were set by a list import two years ago and another third by a workflow nobody remembers building.

That analysis produces two things: the list of workflows and integrations to retire, and the backfill plan for the records currently in the wrong stage. Do the definitions first, the retirement second, and the backfill last. Backfilling into definitions that have not been agreed is how the same mess gets rebuilt.

If your MQL number is disputed every month and nobody can say what a lifecycle stage means without opening a workflow, that is the first thing a RevOps Audit fixes. The definitions table comes out of the first two sessions and the settings take an afternoon.

 

Get a RevOps Audit

 

FAQs

Both, with the sync rules decided deliberately. In most B2B portals the company stage should reflect the most advanced contact, and a new contact should inherit the company's stage rather than reset it.
Yes, and it should be allowed. An inbound demo request can go straight from Lead to MQL to Opportunity in a day. What matters is that each stage is set by its defined event, not that every record passes through every stage.
MQL is set by the system when a defined qualification threshold is met. SQL is set when a rep confirms fit after a conversation. One is a marketing signal, the other is a sales judgement.
Whenever the go-to-market motion changes materially, and at least annually. A new product line, a move upmarket or a change in the MQL determinant all warrant a review.