HubSpot lifecycle stages are one of the most powerful features in the platform and one of the most consistently broken. Teams configure the stages in the first month of their HubSpot setup, leave the definitions vague, update them manually when they remember, and then wonder why their funnel reporting is unreliable. Here is how to fix that.
There are three failure modes. The first is leaving the default stage names without defining what each stage means for your specific business. What makes a contact an MQL at your company is not the same as what makes one at every other HubSpot user. The default definition is a placeholder. You need to replace it.
The second failure mode is manual updates. If sales reps or marketing coordinators are manually updating lifecycle stages in contact records, the data will be incomplete, inconsistent, and always behind. Manual processes do not scale and do not produce reliable reporting data.
The third failure mode is not connecting lifecycle stages to reporting. Most teams set up stages, occasionally glance at them in individual contact records, and never build the funnel conversion reports that make stage data useful. Without reporting, lifecycle stages are metadata, not intelligence.
All three are fixable with documented criteria, automated workflows, and a monthly reporting cadence.
HubSpot provides eight stages out of the box. Here is what each is designed to represent and when to use defaults versus customizing them.
Subscriber: A contact who opted in to receive content from you but has not taken any action that indicates purchase intent. Blog subscribers, newsletter signups, podcast listeners who registered. Use the default definition. No changes needed.
Lead: A contact who has expressed some interest by completing a form or downloading a resource. They have identified themselves but have not yet met the criteria for marketing qualification. Use the default definition. The distinction between Lead and MQL is where your team needs to do the definitional work.
MQL (Marketing Qualified Lead): A contact who meets your defined threshold of behavioral and fit criteria, indicating they are ready for sales outreach. This stage requires your team to write a specific definition. "Marketing qualified" means nothing without documented criteria.
SQL (Sales Qualified Lead): A contact who a sales rep has reviewed and accepted as a legitimate sales opportunity. This stage should be owned by sales, not marketing. SQL requires a sales rep action, not a marketing automation trigger.
Opportunity: A contact associated with an open deal in HubSpot CRM. This stage should be automated: when a deal is created and associated with a contact, that contact's lifecycle stage becomes Opportunity.
Customer: A contact whose associated deal has moved to Closed Won. Automate this. Every time a deal closes, every associated contact should immediately become a Customer.
Evangelist: A contact who actively advocates for your product (writes reviews, provides references, speaks at events). This stage is typically manual because advocacy is hard to detect programmatically. Reserve it for contacts you explicitly identify as advocates.
Other: A catch-all for contacts who do not fit any of the above. Use sparingly. Contacts in "Other" are invisible in funnel reporting.
HubSpot allows you to rename lifecycle stages (except Subscriber and Customer, which are locked). Rename stages when your sales team uses different terminology internally. If your team says "SAL" (Sales Accepted Lead) instead of SQL, rename SQL to SAL. Terminology alignment matters because sales reps update records using the language they know.
Do not add new lifecycle stages beyond the 8 defaults unless you have a specific stage that HubSpot's default structure genuinely cannot represent. More stages mean more complexity and more opportunities for data gaps.
Before automating anything, write down exactly what a contact must do or be to reach each stage. Document these criteria in a shared definition that both marketing and sales sign off on. This document is as important as any HubSpot configuration.
A Marketing Qualified Lead at your company meets ALL of the following:
Fit criteria (must meet at least 2):
Behavioral criteria (must meet at least 1):
Exclusion criteria (disqualifies regardless of other criteria):
Write this down. Put it in your CRM documentation. Review it every quarter with both marketing and sales leadership. The definition is not static. As your product and market evolve, so does the MQL definition.
An SQL is a contact that a sales rep has reviewed and explicitly accepted as worth pursuing. SQL requires human judgment. It cannot be fully automated.
A typical SQL definition: MQL criteria are met AND a sales rep has completed an initial qualification conversation (phone call, email exchange, or discovery meeting) AND the contact has confirmed they are actively evaluating solutions AND there is a defined timeline for a decision.
The SQL stage moves in HubSpot when the sales rep manually updates it or when a deal is created with a close date. Do not automate SQL on behavioral triggers alone. Automating SQL bypasses the sales qualification step that makes the stage meaningful.
"MQL is a marketing judgment. SQL is a sales judgment. Automating SQL on marketing data alone is how you destroy sales trust in your CRM."
Opportunity should be automatic: if a contact is associated with a HubSpot deal that is not Closed Lost, the contact is an Opportunity. Build this as a workflow that runs daily.
Trigger: Contact is associated with a deal AND deal stage is not Closed Lost AND deal stage is not Closed Won. Action: Set lifecycle stage to Opportunity.
This is straightforward and avoids contacts being stuck at SQL stage after a deal has been created.
Customer should also be fully automatic. Any contact associated with a Closed Won deal is a Customer. Any contact previously marked Customer who becomes associated with a new open deal remains a Customer (do not revert stage backward).
HubSpot has a built-in setting to automatically update lifecycle stage to Customer when a deal closes. Enable this in CRM settings. Verify it is on. Many HubSpot instances have this disabled and rely on manual updates.
Automation is where documented criteria become operational. Build a workflow for each stage transition.
Trigger: Contact Score is greater than or equal to [MQL threshold] AND Contact is not in a more advanced lifecycle stage.
Actions:
Important: Include re-enrollment conditions. If a contact falls below the MQL threshold (score decays), do not automatically revert them to Lead. Score decay below threshold should trigger a separate review workflow, not an automatic lifecycle stage demotion.
Do not automate this stage transition based on marketing signals. Instead, create a task for the sales rep when MQL status is set and use a manual update or a sales rep action (deal creation, first meeting logged) as the SQL trigger.
Optional automation: if a contact books a meeting via HubSpot Meetings link AND is currently at MQL stage, automatically create a deal record and let the Opportunity workflow handle stage progression.
Trigger: Contact is associated with a deal AND deal stage changes to Closed Won.
Actions:
This should be verified as working for every deal close. Audit it monthly by pulling contacts associated with Closed Won deals in the last 30 days and confirming lifecycle stage is Customer.
The value of well-maintained lifecycle stages is in funnel reporting. Build these two reports in HubSpot and put them on your marketing dashboard.
HubSpot's Lifecycle Stage Funnel report shows the count of contacts at each stage and the conversion rate between stages. Look at:
If your MQL-to-SQL conversion is below 15%, either the MQL definition is too loose or the sales handoff process is broken. If SQL-to-Opportunity is below 40%, sales is accepting leads they cannot actually work.
Create a custom HubSpot report using your stage date properties. Track:
Increasing velocity means your funnel is accelerating. Decreasing velocity signals friction somewhere in the handoff or qualification process. A sudden spike in MQL-to-SQL days usually means sales capacity is constrained or the handoff SLA is not being met.
Common Lifecycle Stage Configuration Mistakes Using lifecycle stage as a substitute for deal stages: they track different things. Setting MQL via manual updates instead of automation: creates data gaps the moment anyone forgets. Not defining SQL criteria in writing: sales and marketing will define it differently in their heads. Reverting lifecycle stage backward automatically: contacts who were once MQLs and then went quiet should not drop back to Lead in automated reporting. Using lifecycle stages in HubSpot for contact objects only without syncing to associated company objects: creates reporting gaps in account-based programs.
Can a contact's lifecycle stage go backward (e.g., from MQL back to Lead)? Technically yes, but TPG recommends against it. HubSpot's default lifecycle stage property is designed to move forward. Allowing backward movement corrupts funnel reporting because a contact reappearing at Lead stage makes it look like new leads when it is actually churn within your existing database. If a contact was MQL and never converted, flag them in a separate property ("MQL Expired" or "Needs Re-Engagement") rather than reverting the lifecycle stage.
What is the difference between lifecycle stage and lead status in HubSpot? Lifecycle stage tracks the contact's position in the overall buyer journey across both marketing and sales. Lead status is a sales-specific property that tracks where a contact sits within the sales team's workflow (New, Attempting, Connected, Open, Unqualified). Use lifecycle stage for marketing-to-sales funnel reporting. Use lead status for sales rep activity tracking. Both should be configured and used, not one or the other.
How do I get sales to update lifecycle stages reliably? Do not rely on sales to manually update lifecycle stages. Automate every stage that marketing controls (Lead, MQL, Opportunity, Customer). For SQL, make the update as low-friction as possible: one field, one click, visible on the contact record dashboard. Tie SQL update to an existing sales action they already take, like creating a deal or logging a discovery call. The more the update is a standalone task, the less reliably it gets done.
Should lifecycle stages sync bidirectionally with Salesforce if we use both? Yes, with care. If Salesforce is your system of record for sales data, lifecycle stage updates in Salesforce should write back to HubSpot. Map HubSpot lifecycle stage to the closest equivalent Salesforce field (usually Lead Status or Contact Stage). Set the sync rules to be unidirectional for stages owned by sales (SQL, Opportunity) and unidirectional for stages owned by marketing (MQL, Lead). Bidirectional sync on all stages creates overwrite conflicts.
How many contacts should I expect to see at each lifecycle stage? The funnel naturally narrows at each stage. A healthy distribution for a mid-market B2B company might look like: 100,000 Subscribers, 20,000 Leads, 2,000 MQLs, 600 SQLs, 400 Opportunities, 120 new Customers per quarter. If the ratio between any two adjacent stages is extreme (more SQLs than MQLs, for example), it signals a data integrity problem rather than exceptional conversion performance.
The Pedowitz Group | pedowitzgroup.com | Revenue Marketing Experts Since 2007