On this page
What HubSpot supports natively
| Lifecycle stage | Lead status | Deal stage | |
|---|---|---|---|
| Lives on | Contacts and companies | Contacts and companies (a separate property on each) | Deals (one per deal, per pipeline) |
| Answers | Where is this person or company in the relationship? | What is sales doing with this lead? | Where is this deal in the buying process? |
| Defaults | Subscriber, Lead, MQL, SQL, Opportunity, Customer, Evangelist, Other | Contacts: New, Open, In Progress, Open Deal, Unqualified, Attempted to Contact, Connected, Bad Timing. Companies: five default options | Sales Pipeline: Appointment scheduled, Qualified to buy, Presentation scheduled, Decision maker bought-in, Contract sent, Closed won, Closed lost |
| Moves | Imports, forms, the API, integrations and workflows only move it forward unless it’s cleared first; users can set an earlier stage by hand | Whenever it’s set | Any direction, unless pipeline rules restrict it |
| Automated by HubSpot | Yes: deal created, deal won, lead associated, company sync settings | No, unless you build a workflow | Pipeline rules and your workflows |
HubSpot links them in a few places: it describes lead status as the sub-stages within Sales Qualified Lead, and its lifecycle settings can set a contact’s stage when an associated deal is created or won.
How lifecycle stage, lead status and deal stage hand off
A clean setup reads like one story:
- Marketing qualifies. A scoring workflow moves the contact to MQL.
- Sales accepts. The rep, or a routing workflow, moves the contact to SQL and lead status becomes New.
- Sales works the lead. Lead status moves through Attempted to Contact and Connected. Lifecycle stage doesn’t change.
- A deal is created. Deal stage starts at the first pipeline stage, the lifecycle setting moves the contact to Opportunity, and lead status can be set to Open Deal.
- The deal closes won. The deal-won setting moves associated contacts and companies to Customer.
Each property has one job and one owner at each step.
Common mistakes
- Using lifecycle stage as a sales activity tracker. Adding “Contacted” or “Demo booked” as lifecycle stages duplicates lead status or deal stage, and forward-only automation makes it hard to correct.
- Putting lost deals back into lifecycle. A closed-lost deal is a deal stage. What happens to the contact (stays Opportunity, goes to Other, lead status Bad Timing) is a decision to write down.
- Several workflows writing the same stage. That’s the usual reason lifecycle stage keeps changing.
For definitions of each stage, see HubSpot lifecycle stages and HubSpot lead status.
Where Jetstack AI fits
If you’re designing this from scratch, Jetstack AI Projects turns your agreed definitions into a plan you review: lifecycle stages, deal pipelines, properties and the workflows that move records between them. Approving the plan generates the assets, deployment is a separate approval, and the receipt shows what was created, read back from HubSpot. Workflows are created switched off. Projects is currently in limited release; see what Projects can build. To check an existing portal, a Jetstack Workflow Audit flags every lifecycle stage or lead status property that two or more enabled workflows write with different or dynamic values, with the exact actions as evidence.
Sources
- Use contact and company lifecycle stages (HubSpot Knowledge Base)
- Manage how lifecycle stages sync between objects (HubSpot Knowledge Base)
- Set up and customize pipelines (HubSpot Knowledge Base)
- HubSpot's default company properties: Lead status (HubSpot Knowledge Base)
Checked October 30, 2026. HubSpot changes its products often; tell us at team@jetstack.ai if something here is out of date.
Workflows & automation
Turn the brief into approved HubSpot assets.
Projects plans the build against the client portal, generates the assets and deploys them only after you approve.
Explore Projects