If you can't answer the question "How many MQLs did we generate last month, and how many became opportunities?" with confidence, your lifecycle stages are probably broken.
HubSpot lifecycle stages are the property that tracks where every contact and company sits in your marketing and sales process, from anonymous visitor to closed customer. They're the backbone of funnel reporting, the trigger for automation, and the shared language that marketing and sales use (or should use) to stay aligned.
When lifecycle stages are set up correctly, everything downstream works better: lead scoring has a foundation, workflows trigger at the right time, handoffs happen smoothly, and reporting actually tells the truth about your funnel. When they're wrong (undefined, inconsistent, or not automated) every report is suspect, every handoff is a guess, and marketing-sales alignment is a fiction.
Key takeaway: Lifecycle stages aren't just a CRM feature. They're the framework that connects your marketing activity to your sales pipeline. Getting them right is one of the highest-leverage things you can do inside HubSpot and getting them wrong quietly undermines everything else.
Lifecycle stages are a default contact and company property in HubSpot that categorize where a record sits in your marketing and sales process. They represent the stages of your buyer's journey, from first touch to closed customer, and serve as the foundation for funnel reporting, automation triggers, and team handoffs.
HubSpot provides eight default lifecycle stages:
HubSpot also now supports custom lifecycle stages, which allow you to add stages beyond the defaults to match your specific business process. This is particularly useful for B2B companies with more nuanced funnels.
A few important mechanics to understand (HubSpot's documentation on using lifecycle stages covers the full technical detail):
The default stages are a reasonable starting point, but most B2B companies need to customize definitions, criteria, and transitions to match their actual sales process. The goal is to make lifecycle stages reflect reality, not force your process to fit HubSpot's defaults.
Before touching HubSpot, document how prospects actually move through your sales process today. Interview your marketing team, your sales team, and your sales leadership. Answer these questions:
Vague definitions create inconsistency. Every lifecycle stage should have criteria that are specific enough for any team member to apply consistently. Here's an example framework for a B2B SaaS company:
|
Lifecycle Stage |
Definition |
Trigger |
|
Subscriber |
Website visitor or event attendee who provides a valid email address |
Newsletter signup, blog subscription |
|
Lead |
Contact whose company fits your target market criteria (industry, size, tech stack) |
Form submission, content download, chat conversation |
|
MQL |
Contact who demonstrates intent through high-value actions or reaches lead scoring threshold |
Lead score reaches 70+, requests a demo, submits "Contact Us" form |
|
SQL |
MQL that sales has engaged with and confirmed as worth pursuing |
Completed discovery call, scheduled meeting, active email conversation |
|
Opportunity |
Contact associated with an active deal in the pipeline |
Deal created in HubSpot or synced from Salesforce |
|
Customer |
Contact associated with a closed-won deal |
Deal marked closed-won |
The most important thing: marketing and sales must agree on these definitions. If marketing defines MQL one way and sales defines it another, every handoff becomes a debate instead of a process.
HubSpot now lets you create custom lifecycle stages beyond the eight defaults. Consider adding custom stages only when there's a meaningful, measurable shift in the buyer's relationship that the defaults don't capture.
Good reasons to add a custom stage:
Common mistake: adding too many custom stages. Every stage you add is a stage you need to automate, report on, and maintain. More than 8–10 total stages usually introduces more complexity than value.
This is one of the most common points of confusion in HubSpot and getting it wrong creates messy data, misaligned teams, and broken reporting. Lifecycle stage tracks where a contact is in your funnel. Lead status tracks what sales is doing with that contact right now.
Lifecycle stage answers: "Where is this person in our marketing and sales process?" It's a macro-level view: Subscriber, Lead, MQL, SQL, Opportunity, Customer. It moves forward as the contact progresses through your funnel.
Lead status answers: "What is the current sales disposition of this contact?" It's a micro-level view: New, Attempting to Contact, Connected, Open Deal, Unqualified, Bad Timing. It changes frequently as sales works the lead.
Think of lead status as a subset of lifecycle stage. A contact can be in the SQL lifecycle stage while their lead status cycles through "New" → "Attempting to Contact" → "Connected" → "Open Deal." The lifecycle stage stays at SQL until a deal is created (moving them to Opportunity). The lead status reflects the real-time activity within that stage.
|
Property |
Scope |
Changes |
Owned By |
Example Values |
|
Lifecycle stage |
Full buyer journey |
Rarely (major milestones) |
Shared: marketing + sales |
Lead, MQL, SQL, Opportunity, Customer |
|
Lead status |
Sales activity within a stage |
Frequently (daily/weekly) |
Sales |
New, Attempting Contact, Connected, Unqualified |
Common mistake: using lead status instead of lifecycle stages, or treating them as interchangeable. They serve different purposes and should never be merged into a single property. Keep both, define both, and train both teams on the difference.
Manually updating lifecycle stages is unsustainable. Automation is what makes lifecycle stages reliable and reliable stages are what make funnel reporting trustworthy.
The transitions that lend themselves best to automation are those with measurable, unambiguous triggers:
Not every MQL becomes an SQL. Not every SQL becomes an opportunity. You need automation that handles contacts who stall:
HubSpot now allows backward lifecycle transitions, but that doesn't mean you should use them freely. Moving a contact from SQL back to Lead corrupts your funnel reporting by erasing the record of their first progression. If a contact stalls or is disqualified, use lead status to reflect that, not a lifecycle stage regression.
The only exception: contacts that were incorrectly staged (e.g., imported with the wrong stage or auto-set by a misconfigured workflow). In those cases, a manual correction is appropriate.
If your marketing team works in HubSpot and your sales team works in Salesforce, lifecycle stage alignment is one of the most critical, and most frequently botched, aspects of your integration. Misalignment here is the root cause of most marketing-sales attribution disputes.
HubSpot lifecycle stages and Salesforce opportunity stages serve different purposes but need to be synchronized:
|
HubSpot Lifecycle Stage |
Salesforce Equivalent |
|
Lead |
Lead (Salesforce Lead object) |
|
MQL |
Lead with status "Marketing Qualified" or converted Contact |
|
SQL |
Converted Contact with active engagement |
|
Opportunity |
Opportunity (linked to Account and Contact) |
|
Customer |
Opportunity at Closed/Won stage |
The most common failure point is the MQL-to-SQL handoff. In HubSpot, MQL is a lifecycle stage on the contact record. In Salesforce, the equivalent is either a Lead with a specific status or a Contact that has been converted from a Lead. If your sync rules don't account for this structural difference, MQLs can get lost in the gap between the two systems
Another common issue: Salesforce opportunity stages don't map 1:1 to HubSpot lifecycle stages. Salesforce might have six opportunity stages (Discovery, Demo, Proposal, Negotiation, Closed Won, Closed Lost), but HubSpot has only one lifecycle stage for all of them: "Opportunity." You need to decide whether to track Salesforce deal stages in HubSpot as a separate property or consolidate them.
The consequences are quiet at first and compounding over time. Broken lifecycle stages don't throw error messages. They produce bad data that looks legitimate, until someone tries to make a decision based on it.
If contacts are stuck in the wrong stages, your funnel metrics are inaccurate — a symptom of the broader CRM data quality problems that compound over time. You might show a healthy volume of MQLs, but if half of them were never actually qualified — they just got auto-set by a misconfigured form — your conversion rates are inflated and your forecasts are unreliable.
When marketing says "We sent you 200 MQLs" and sales says "We only got 50 that were worth calling," the problem is almost always a lifecycle stage definition problem. Without shared criteria for what constitutes an MQL, the handoff is subjective and subjective handoffs breed blame.
Revenue attribution depends on contacts progressing through lifecycle stages in a traceable, timestamped sequence. If stage transitions aren't automated or are inconsistently applied, attribution models can't accurately connect marketing touchpoints to revenue outcomes.
Workflows triggered by lifecycle stage changes will misfire if contacts are in the wrong stage. A nurture sequence designed for MQLs might enroll contacts who are already in active sales conversations. A lead routing workflow might miss contacts entirely because their stage was never updated.
The ultimate cost of broken lifecycle stages is strategic blindness. You can't measure funnel velocity, conversion rates, or channel effectiveness if the funnel itself isn't defined consistently in your system. And if you can't measure it, you can't optimize it — or prove its value to leadership.
Not exactly — you can't rename the built-in defaults like "Lead" or "MQL." But HubSpot now allows you to create custom lifecycle stages and reorder them alongside the defaults. If a default stage doesn't fit your terminology, you can add a custom stage with your preferred name and stop using the default. Just be aware that any workflows, reports, or integrations referencing the old stage will need to be updated.
For most B2B companies, 6–8 stages is the sweet spot: Subscriber, Lead, MQL, SQL, Opportunity, Customer, plus 1–2 custom stages if your process warrants them (e.g., Product Qualified Lead, Former Customer). More than 10 stages usually creates complexity that slows teams down and makes reporting harder to interpret. Only add a custom stage if it represents a genuinely distinct, measurable phase of the buyer journey.
Both. HubSpot lifecycle stages apply to both contact and company records. For B2B, this is important because buying decisions are made at the company level, not just the individual level. Configure HubSpot to sync lifecycle stages between contacts and their associated companies so both records reflect the same funnel position. This is especially critical for account-based marketing strategies.
First, define "stuck." Create a report showing contacts who have been in the same lifecycle stage for longer than your average time-to-convert. For contacts stuck at MQL, check whether sales is reviewing them within SLA. For contacts stuck at SQL, check whether deals are being created. For contacts stuck at Lead, check your scoring criteria as they may need a lower threshold or different qualification triggers. Use lead status (e.g., "Nurture" or "Bad Timing") to dispositional stalled contacts without corrupting your lifecycle stage data.
Lifecycle stages themselves don't directly affect pricing, but the contacts in those stages do. HubSpot bills based on your marketing contact tier. Contacts stuck in early stages (Subscriber, Lead) who never progress might be inflating your contact count, and your bill, without contributing to pipeline. Regular lifecycle hygiene (archiving unengaged contacts, purging bounces) keeps your database lean and your costs aligned with actual value.
Every metric your leadership cares about (pipeline growth, conversion rates, marketing ROI, sales velocity) depends on lifecycle stages being defined correctly, automated reliably, and maintained consistently.
This isn't glamorous work. Nobody gets excited about configuring lifecycle stage transitions. But it's the foundation that makes everything else in your HubSpot portal trustworthy. When lifecycle stages are right, your reports tell the truth. Your automation fires on time. Your handoffs are clean. And your teams operate from a shared definition of what "qualified" actually means.
When they're wrong, none of that works, and the symptoms (unreliable reporting, marketing-sales finger-pointing, attribution gaps) are often blamed on everything except the real root cause.
Want to see how your lifecycle stages stack up? Book a free discovery call and I'll review your current framework, identify gaps in your definitions and automation, and map out what a properly designed lifecycle model looks like for your specific business.
Anna Connolly is a HubSpot Solutions Consultant and marketing operations strategist with 9+ years of experience helping B2B marketing and RevOps teams fix broken CRM systems, clean up messy data, and build automation that scales. Learn more →