A salesperson is following up with a qualified prospect, but the dashboard still calls that person a new lead. Before you add another status, check which question each field is supposed to answer. A useful HubSpot lifecycle map gives marketing and sales a shared definition of progress and a separate place to record the next sales action.
TLDR: Use lifecycle stage for the contact or company relationship, Lead Status for the agreed qualification or follow-up state, and a deal pipeline for an individual opportunity. Define the evidence and owner for each transition before building automation. Treat the separate leads object as a separate design decision.
Product documentation checked August 29, 2026. Examples below are fictional operating rules, not a universal HubSpot configuration.
HubSpot lifecycle stages vs Lead Status: the short answer
HubSpot lifecycle stages categorize contact and company records based on where they are in your marketing and sales process. The default Lead Status property describes sub-stages within the Sales Qualified Lead lifecycle stage. A deal stage tracks a specific opportunity, while a separate lead record can move through its own pipeline. These fields can inform the same customer journey, but they are not interchangeable. HubSpot: lifecycle stages.
Use lifecycle stage to answer, “How far has this relationship progressed?” Use Lead Status to answer, “What is sales doing with this qualified lead now?” Use the deal pipeline to answer, “What is happening with this purchase?” Your account may use custom lifecycle stages or customized Lead Status options, so inspect the current properties and workflows before applying a new map.
Start the design conversation with three questions: What relationship do we have with this person? What is the sales team doing now? Is there a specific commercial opportunity to manage? Keeping the answers distinct helps you choose which field a report should use.
For the broader record-management process, use our guide to tracking leads in HubSpot. Here, the task is to agree on definitions and transitions.
| Question your team needs to answer | Proposed home for the answer | Example of evidence to require |
|---|---|---|
| How far has this relationship progressed? | Contact or company lifecycle stage | A documented qualification or customer event |
| What is happening in the current sales follow-up? | Agreed Lead Status process | An attempted contact, a response or a recorded qualification decision |
| What is happening with this purchase? | The relevant deal record and pipeline | Evidence tied to that particular opportunity |
This is a recommended division of responsibility. It is not an instruction to overwrite existing values. Record your current usage beside the proposed usage so you can see what would change.
Review the default HubSpot lifecycle stages and Lead Status options
HubSpot currently documents eight default lifecycle stage options: Subscriber, Lead, Marketing Qualified Lead, Sales Qualified Lead, Opportunity, Customer, Evangelist and Other. The labels describe relationship progress. They do not supply the qualification evidence your sales and marketing teams should require.
HubSpot also documents eight default Lead Status options: New, Open, In Progress, Open Deal, Unqualified, Attempted to Contact, Connected and Bad Timing. Those options describe sales follow-up inside the default Sales Qualified Lead lifecycle stage. They can be customized, which is why your mapping exercise should start with the actual Contact: Lead Status property in your portal.
| Lifecycle stage question | Lead Status question | Deal or lead pipeline question |
|---|---|---|
| Where is this contact or company in the broader relationship? | What is the current sales outreach or qualification state? | Where is this individual opportunity or lead record in its process? |
The default options are a reference point. Your operating definition still needs entry evidence, an owner and an exception rule for every stage or status you use.
Keep the leads object separate from the contact property
HubSpot also supports pipelines for lead records. Its documentation lists Sales Hub Professional or Enterprise as required to manage lead object pipelines. A lead record's pipeline stage and a contact's Lead Status property are separate concepts. Check which one your team uses before designing reports or automation around the word “lead.” HubSpot: object pipelines.
We recommend writing the object and property together in your specification, such as “Contact: Lead Status.” Avoid shorthand such as “update the lead stage,” which leaves the administrator to interpret the intended field.
If you use both mechanisms, name the source of each report. Decide whether one process should inform the other, who approves that relationship, and what happens when their values disagree. Do not add a second tracking system merely because it is available.
Build a lifecycle map with entry evidence
The following map is a fictional example for a B2B team. The qualification choices are illustrative and should be replaced with your approved criteria. They are not HubSpot defaults or performance benchmarks.
| Proposed lifecycle outcome | Evidence the fictional team requires | Follow-up decision | Accountable role |
|---|---|---|---|
| Lead | A relevant inquiry has been captured | Decide whether marketing review is needed | Marketing operations lead |
| Marketing qualified lead | The inquiry meets the team's documented fit and interest criteria | Request sales review | Marketing lead |
| Sales qualified lead | Sales accepts the inquiry and records why it is qualified | Track outreach and qualification through the agreed status process | Sales manager |
| Opportunity | A specific purchase is being evaluated and the relevant deal is identified | Maintain the deal without rewriting contact history at every deal change | Deal owner |
| Customer | A verified purchase event satisfies the team's customer definition | Begin the agreed customer handoff | Customer operations lead |
For each row, add the evidence location, the person allowed to change the value, and the event that should trigger review. A title such as “qualified” is incomplete until two people can apply it to the same record and explain the same decision.
Our recommended acceptance test is simple: give marketing and sales the same fictional records without the expected answers. Compare their classifications. Resolve disagreements in the definitions before turning the map into automation.
Decide how to handle three awkward cases
A customer starts a new buying conversation
In this fictional case, a customer asks about an additional service. We recommend preserving the established customer relationship and tracking the new purchase separately. Record the new interest and its owner without making the person appear to be a first-time prospect again.
Ask your reporting owner whether a new opportunity should count toward pipeline, customer expansion or another defined category. That is a reporting decision your lifecycle field alone cannot settle.
A qualified prospect says “not this quarter”
We recommend documenting the reason, the next review date and the person responsible for the follow-up. Decide whether this means sales qualification was incorrect or whether a qualified relationship simply has no current purchase timing.
Those are different findings. A blanket rule that resets every delayed conversation to an early lifecycle stage can erase the distinction your team needs to analyze. Review the history before approving a reset.
A company has contacts at different levels of engagement
In this fictional example, one contact is discussing a purchase while another only receives operational communications. We recommend agreeing on how company-level reporting should summarize that situation. Do not assume every contact should inherit the most advanced relationship automatically.
Document any company-to-contact synchronization you already use and test the intended outcome with approved examples. The map should explain which record changed and why.
Review transition behavior before automating
HubSpot documents that automatic lifecycle updates generally move records forward. Certain methods of setting an earlier stage require clearing the current value first. That is a consequential data change, not a routine cleanup step. Have an authorized administrator review the current method and reporting effects before any reset. HubSpot: lifecycle update behavior.
We recommend testing the proposed transitions in an approved test environment or with tightly scoped test records. Include repeated events, missing owners, conflicting updates and a record that already has a later lifecycle stage. Do not enable broad enrollment merely to see what happens.
Keep the wider sales funnel design connected to these definitions, while leaving detailed deal-stage exit criteria in the deal process.
Make reports answer one question at a time
Before changing a dashboard, write the question above the chart. “How many people have reached sales qualification?” and “How many sales conversations need follow-up?” should have different definitions and may use different fields.
We recommend reviewing four items for every affected report:
- Population: Specify the object, date range and excluded records.
- Meaning: State whether the chart shows a current value, a historical transition or a sales activity.
- Ownership: Name the person who resolves missing or conflicting values.
- Change impact: Compare the old and proposed results on a controlled sample before replacing the report.
Do not infer historical conversion rates from a current-status snapshot without checking what the report actually measures. Keep the old report definition until the owner accepts the replacement.
Frequently asked questions
Should Lead Status and lifecycle stage have the same options?
We recommend separate options because the fields answer different business questions. Define the relationship and the current follow-up process independently, then document any approved connection between them.
Should a customer move backward when a new deal opens?
We recommend preserving the established customer relationship and managing the new purchase on its relevant deal. Review any existing automation before changing that behavior.
Do we need the leads object to create a useful mapping?
Start by identifying the records and fields your team actually uses. A useful mapping needs clear definitions, evidence and ownership. Evaluate the separate leads object against your sales process and subscription before adding it.
What should we approve before turning on automation?
Approve the object and property, entry evidence, allowed transition, accountable owner, exception handling and test results. Keep any broad enrollment or historical reset in a separate change approval.
Give the map an owner
A lifecycle map is useful when someone can explain an unexpected value and maintain the rule that produced it. Our HubSpot sales services can help you review that process and its reporting dependencies.
Use the HubSpot Portal Audit Scorecard to capture the unresolved definitions and assign the next review. Start with one disputed transition, agree on its evidence, and make the same decision reproducible.
