How do I set lifecycle stage from lead score in HubSpot?
Short answer
One workflow, one number. Enroll on the score property alone, filter on the stage you are moving from, ... set Lifecycle stage to Marketing Qualified Lead, notify marketing ops.
Marketing Hub Professional, around thirty minutes. Keep the threshold inside that single workflow so sales gets one documented answer to why a contact qualified. The trap: lifecycle never walks backwards by itself, so any demotion needs a mirror property holding the highest stage reached and an explicit reset.
Read the whole answerShow less
What a spec looks like
The nine sections, and the files
Every spec follows the same nine sections, so a team reads one and knows how to read all of them.
- Outcome, when to use it and when not to
- Prerequisites: properties, lists, tiers, with the JSON to create them
- Enrollment and re-enrollment, then every step with its parameters
- Known pitfalls, a test plan, variants, and the YAML build spec
PDF, Markdown, properties JSON, workflow JSON, custom code where used. Test plan and known pitfalls in every spec.
Each spec states its minimum tier. The 12 free ones open in full, the others show their public preview.
The 17 specs, in build order
One threshold, written down once
Turns a score into a stage, a routing decision and a priority band, with the number living in one place rather than in four.
What each spec doesHide
The handoff, and the gate on it
Moves the contact to Sales Qualified Lead on real intent, assigns an SDR, and makes sales say yes out loud before the lead is theirs.
What each spec doesHide
Movement in the other direction
Catches the accidental downgrade, performs the deliberate one, and chases anything that stopped moving at all.
What each spec doesHide
Stages the deal decides, not marketing
Syncs contact and company lifecycle from the deal that closed, so a customer stops being labelled a lead.
What each spec doesHide
Prove it moved
Timestamps every first entry into a stage, alerts on the milestones, and counts transitions once a month.
What each spec doesHide
The 3 things that break this, and how the specs stop them
Lifecycle stage never walks backwards on its own
This is the behaviour behind the question everyone searches for.
Nothing in the funnel moves a contact down a stage automatically, and the form level Set lifecycle stage option never moves a contact backwards either. So a demotion has to be built on purpose, and the guard against an accidental one needs a second property recording the highest stage the contact ever reached. Backfill that mirror property before switching the guard on, or every existing contact reads as having no history and its current stage looks like forward movement on the first pass.
How the specs stop itShow less
Two systems writing the same property
A form with the Set lifecycle stage option enabled, a deal based workflow, an import and a scoring workflow can all write Lifecycle stage on the same contact within a minute.
They will disagree and the last write wins, which is why funnel numbers change when nobody changed anything. Decide which system owns the property at each stage of the funnel and write it down. The regression guard also re-fires its own trigger when it corrects a value, so test that second pass exits cleanly before rollout.
How the specs stop itShow less
A threshold is a number that ages
The score number is chosen once and then quietly outlives the model it was calibrated against.
Add a new positive signal to the scoring rules and every contact's score shifts, while the threshold in the workflow stays where it was. The legacy default score behaves differently from a custom model built in the scoring tool, so confirm which one is actually active before setting bands. And a contact hovering at the boundary will cross it repeatedly, which is what the stage filter and the owner check exist to absorb.
How the specs stop itShow less
What this bundle builds
The funnel report that nobody trusts. Marketing says four hundred MQLs last month, sales remembers about eighty worth calling, and the conversion rate between them has been quietly meaningless for a year. Almost always the cause is the same: Lifecycle stage is written by four different things, none of which agrees about what the stages mean.
Seventeen specs put one set of rules on that property. A score crosses a documented threshold and the contact becomes an MQL, with the number held in one workflow so there is a single answer to why. An SDR gets assigned and a task at the same moment, and a second path does the same job from a product usage signal rather than a score. Real buying intent moves the contact to SQL, notifies the rep and stops the nurture. Then the acceptance gate: the rep has two business days to accept or reject with a reason, which is how you find out that sales disagrees instead of watching leads go quiet.
The other half is movement downwards, which almost no portal builds. A contact whose only deal is lost drops back to MQL. An accidental downgrade gets corrected within minutes against the highest stage ever reached. Bad-fit leads move to Other rather than distorting the rates. And three reporting specs timestamp every first entry, so the whole thing can finally be measured.
Read the restShow less
How the pieces fit together
The mirror property first. Create the highest stage reached field and backfill it across existing contacts before anything else runs, because the regression guard compares against it and an empty field turns every current stage into apparent forward movement.
Then the promotion workflow and its threshold, alone, until it behaves. Scope re-enrollment to the score property only, or a contact that reads a blog post three times a day re-enrolls all afternoon. The routing and priority band specs read the same number, so build them after the threshold is settled rather than alongside it.
The handoff next, then the acceptance gate on top of it. Those two share the stage filter, and the gate adds a Wait until with an expiry, so test the expiry path first. SDR assignment depends on ownership being unset when the contact qualifies, worth confirming before wiring it.
Demotion and disqualification last, once the forward direction is stable and sales leadership has agreed a stage can go down. The timestamp spec can be built at any point, and the earlier it exists the more history your first funnel report has.
What you get
- 17 specs, from a 15 minute stage sync to a 75 minute monthly transition digest, roughly 9 hours of build with testing
- Each spec as PDF and Markdown, with enrollment criteria, the step list, a diagram, a test plan and the known pitfalls written out
- Properties JSON: 20 property definitions across contacts and companies, including the highest stage reached mirror, the sales acceptance status and the stage entry timestamps
- Workflow JSON in Automation API format, switched off on import
- Custom coded actions in 1 spec only, the monthly transition count that reads property history
- Tier stated per spec: 14 Marketing Hub Professional, 2 Sales Hub Professional, 1 Data Hub Professional
- Test plans that cover the backwards path: the import that downgrades, the rejected lead, the contact that re-qualifies after a demotion
- Install in one click for Full and Agency buyers
Who it is for, and who should skip it
For the marketing ops person who has to present funnel conversion to a leadership team that has already stopped believing the numbers. Also for anyone setting up a new portal who would rather define the stage rules once, in writing, than discover them later from four workflows built by three people who have all left.
Skip it if your portal has no scoring model yet, because a threshold on a score nobody has calibrated is a number pretending to be a decision. Build the model first, then come back. Skip the acceptance gate if sales is two people who talk to marketing daily, since the ceremony costs more than it returns at that size. And if lifecycle is one symptom of a portal where every property is contested, the full library covers the rest of the argument too.
Questions admins ask
How do I set lifecycle stage from lead score in HubSpot?
A contact based workflow with re-enrollment scoped to the score property alone, so page views and email opens do not re-check the same record all day. Filter on the current stage you are promoting from, set Lifecycle stage to Marketing Qualified Lead, and notify marketing ops. About thirty minutes. Keep the threshold value in this one workflow, because the first question sales asks is why a contact is an MQL and the answer needs to be a single documented number.
Why did my contact's lifecycle stage move backwards?
Something wrote it, because nothing reverses a stage on its own. The usual suspects are an import mapping that included the property, a form with its own stage setting, or a second workflow with branch logic that sets a stage without filtering on the current one. The spec in this bundle corrects it within minutes against a mirror property holding the highest stage reached, and tells marketing ops. Expect a short window where a report reads the wrong value, since the correction is not instant.
Can a workflow move a contact from SQL back to MQL?
Yes, and it should when the only open deal is Closed Lost or has gone stale, otherwise dead SQLs are carried forward in the funnel forever. Two cautions. Counting a contact's open associated deals inside a workflow filter is not consistently available, so a rollup property is the honest fallback. And demotion can conflict with compensation or reporting rules that treat SQL as a one-way gate, so agree it with sales leadership before switching it on.
Should lifecycle stage and lead status be automated together?
Keep them separate and give them separate owners. Every spec here writes Lifecycle stage and nothing else, which is a funnel position shared by marketing and sales. The acceptance gate uses its own sales-owned status property, with Pending review, Accepted and Rejected values, precisely so the rep's opinion does not overwrite the funnel record. That separation is what lets you measure how often marketing and sales disagree instead of hiding it in one field.
Do I need Marketing Hub for lead scoring?
For the score itself, yes, since the scoring tool and the default score property come with Marketing Hub Professional. Fourteen of the seventeen specs sit there. Two run on Sales Hub Professional, the demotion on a lost deal and the lifecycle sync from a deal stage, and one needs Data Hub Professional for the monthly transition count, which reads property history through a custom coded action.
Read 12 complete specs before you pay.
One per category, same format as the paid ones. Email only, no card.
We email the link, then a short note when specs change. Nothing else.
Here it is. Download the pack now (.zip) The link is in your inbox too.
Browse the library