HubSpot MQL definition and lifecycle stages: a 2026 reference

Published June 16, 2026

HubSpot’s data model includes a Lifecycle Stage property that ships with default stages: Subscriber, Lead, Marketing Qualified Lead, Sales Qualified Lead, Opportunity, Customer, Evangelist, and Other. The property is on every Contact and Company record by default.

The default lifecycle stages are a starting point, not a finished system. Most B2B SaaS teams need to customize what each stage means, when contacts move between them, and how the transitions are tracked. This post is a quick reference for how MQL specifically works in HubSpot, and how to set it up in a way that holds up.

How HubSpot defines MQL by default

HubSpot’s official definition of Marketing Qualified Lead is: “Contacts who have engaged with the team’s marketing efforts, but are still not ready to receive a sales call. An example of an MQL is a contact who fills out a landing page form for an offer.”

That’s deliberately broad. HubSpot doesn’t impose a specific scoring threshold or set of criteria; the meaning is yours to define. HubSpot’s own documentation is explicit that the MQL stage “is not set automatically by HubSpot” and that you qualify contacts into it through your own lead scoring criteria and workflows (HubSpot Knowledge Base, “Use contact and company lifecycle stages”). If you want a definition you can actually operate against, our working definition of an MQL covers the fit and interest signals that hold up across teams.

For most B2B SaaS businesses, the HubSpot default isn’t tight enough. A landing page form fill is not necessarily an MQL; it could be a researcher, a competitor, or a casual subscriber. Tightening the definition is a required step for operational use.

How to set the MQL transition in HubSpot

Three ways to move contacts to the MQL Lifecycle Stage in HubSpot:

1. Manually. A team member updates the Lifecycle Stage property on the contact record. Fine for small teams, doesn’t scale.

2. Via workflow. A HubSpot Workflow that triggers when criteria are met (score threshold, specific form submission, etc.) and updates the Lifecycle Stage. The standard approach for most B2B teams.

3. Via integration or API. External systems (lead scoring platforms, intent data tools, etc.) can update the Lifecycle Stage property via the HubSpot API.

The workflow approach is the most common. The pattern:

Trigger: Lead Score reaches 80+ AND Industry is in target list AND Company Size is 100-500
Action: Set Lifecycle Stage to "Marketing Qualified Lead"
Action: Notify SDR via Slack with score breakdown

The full HubSpot lead scoring setup guide walks this workflow build step by step.

The HubSpot lifecycle stage flow

HubSpot’s default stages, in typical order:

  • Subscriber: opted into communications, no buying signals yet
  • Lead: identified as a potential customer, hasn’t met MQL criteria
  • Marketing Qualified Lead (MQL): met your marketing-qualified threshold
  • Sales Qualified Lead (SQL): validated by sales as a real near-term opportunity
  • Opportunity: has an open deal record
  • Customer: has a closed-won deal
  • Evangelist: customer who promotes your product (often manually set)
  • Other: catch-all

HubSpot will not move a contact backward through these stages by default. Per HubSpot’s documentation, default automatic updates to the Lifecycle Stage property only move the stage forward, and tools like imports, forms, the API, and workflows can only set the default property forward unless you first clear the existing value (HubSpot Knowledge Base, “Use contact and company lifecycle stages”). If a contact reaches Customer and then their deal closes-lost on a renewal, they won’t automatically demote to Lead. You can configure backward transitions explicitly in workflows, but think carefully about the implications before doing so.

Adding a SAL (Sales Accepted Lead) stage

HubSpot supports custom Lifecycle Stage values on Marketing Hub Pro and Enterprise. Many B2B SaaS teams add a custom “Sales Accepted Lead” stage between MQL and SQL to track handoff acceptance separately from qualification.

The flow becomes:

  • Subscriber → Lead → MQL → SAL → SQL → Opportunity → Customer

The SAL stage is the explicit acknowledgment by sales that the lead is worth a first touch. It splits the MQL→SQL transition into two measurable conversion rates and makes handoff health diagnosable. For the full lifecycle and why that split matters, see MQL vs SQL: a RevOps guide.

How to write a HubSpot-friendly MQL definition

A working MQL definition for HubSpot has two components:

1. Fit criteria (typically a score threshold or specific property values):

  • Lead Score ≥ 80, OR
  • Industry is in target list AND Company Size is in target band AND Country is in target geography

2. Interest criteria (specific actions):

  • Submitted a form on /demo, /pricing, /contact, OR
  • Started a free trial, OR
  • Engagement Score ≥ 60

Both are required. A workflow that triggers on the AND of fit and interest criteria, then sets Lifecycle Stage to MQL, gives you an operational definition that produces consistent transitions.

The validation report

Once your MQL workflow is running, the metric to watch is MQL→SQL conversion rate. Build a HubSpot Custom Report that tracks this over a rolling 90-day window. If the rate is dropping, your scoring is becoming less predictive (the score isn’t matching reality anymore), or your channel mix has shifted, or your sales capacity is constrained.

The native HubSpot reporting tool makes this report buildable but not built-in. You’ll create it manually in Reports.

Common HubSpot MQL setup mistakes

Quick list of traps:

Default stages without a workflow. Some teams enable MQL as a stage but never automate the transition; contacts only move when someone manually edits the property. The data is unreliable as a result.

Score-only triggers without fit criteria. A score-only trigger means leads from the wrong industry can hit MQL just by hitting a pricing page enough times. Always require fit criteria alongside engagement.

Mismatched workflow rules and documented definition. The MQL definition in your team’s wiki says one thing; the workflow rules in HubSpot do another. Audit quarterly to keep them aligned.

Backward transitions that surprise. Workflows that move contacts back from MQL to Subscriber when they unsubscribe, or back from SQL to MQL on inactivity, can create reporting confusion. Use them deliberately.

If your transitions look right but the leads still underperform, the problem is usually upstream in the score itself. We cover that failure mode in why HubSpot lead scoring stops working.

A short summary

HubSpot’s default Lifecycle Stage property includes MQL but doesn’t impose a specific definition. You define it via workflow rules combining fit and interest criteria. The MQL→SAL→SQL flow with a custom SAL stage in between is the most diagnosable shape for B2B SaaS teams. Validation report on MQL→SQL conversion is the single most useful metric to track over time.