Open your contacts, filter to lifecycle stage Marketing Qualified Lead and sort by the date they entered that stage. The records at the bottom have been waiting for a salesperson longer than your sales cycle, and nobody on either team thinks they are the one who dropped them.
That list is what a broken HubSpot MQL to SQL handoff looks like from the inside. The portal did its job: it recorded that marketing called the lead qualified. What it cannot record is a rule nobody wrote down, which is when marketing stops owning the lead and sales starts.
Why the MQL to SQL handoff breaks
In most portals we audit, the handoff is not missing because of a setting. The two teams never agreed on three things: what makes a lead a marketing qualified lead, who gets it, and how fast sales acts on it. Lifecycle stage and lead status fill up with values anyway. They only record what each person decided on the day.
Marketing reports a healthy MQL number. Sales says the leads are poor. Both are partly right, and neither can prove it. We covered how the two properties differ in lifecycle stage vs lead status; this post is about the rule that should sit between them.
What HubSpot records at each marketing qualified lead handoff
HubSpot gives you enough to see the handoff, as long as you know which properties to read. Its lifecycle stages documentation lists a date entered and a date exited property for each stage. A contact has Date entered Marketing Qualified Lead and Date entered Sales Qualified Lead. Professional and Enterprise portals also get latest time and cumulative time properties per stage. If your team already uses time in stage for deals, this is the same idea applied to contacts.
Stage dates alone do not show whether anyone acted. Read them next to the owner and the last activity on each record, and you can see how long a lead waited for an owner and then for a first real touch.
Who this matters for
- Heads of sales who hear “marketing sent you plenty of leads” and cannot say how many were ever called.
- Heads of marketing judged on MQL volume while the pipeline number belongs to someone else.
- Founders paying for campaigns whose leads may sit untouched for weeks.
The stage dates are available on all plans. The time-in-stage properties need a Professional or Enterprise subscription, so on Starter you calculate waiting time from the dates yourself.
What to check in your portal this week
- Look at how the stage is set up. Go to Settings, then Objects under Data Management, choose Contacts and open the Lifecycle Stage tab, as described in HubSpot’s guide to customizing lifecycle stages. Editing stages needs Super Admin permissions, so agree changes with your admin.
- Build a contacts view filtered to lifecycle stage Marketing Qualified Lead and add columns for the date each contact entered that stage, the contact owner, the date the owner was assigned and the last contacted date. Sort by the date entered, oldest first.
- Count three groups: MQLs with no owner, MQLs with an owner but no
Last contacteddate, and MQLs whose last contact came long after they entered the stage. Each group points to a different gap: routing, follow-up or speed. - Pick ten contacts that reached Sales Qualified Lead and ask the sales rep who moved them why. If the answers differ, your SQL definition exists only in people’s heads.
Our take: write the rule before you touch the workflow
This is a process problem, not a tool problem. A new scoring model or routing workflow will automate whatever confusion is already there. The fix starts on paper.
We would write one page with four lines: the criteria that make a contact a marketing qualified lead, who owns it once it crosses that line, the time sales has to make first contact, and what happens if sales rejects it. The response time is a number your team writes down and both leaders sign, not something copied from a benchmark. Then name one owner for the rule itself, usually a RevOps lead or the admin, who reviews the MQL view every week.
Only after that is it worth building the workflow that assigns owners and moves stages. Setting up the view takes an hour. The conversation between sales and marketing takes longer, and it is the part that actually fixes the handoff. If nobody can own that weekly review, keep the process manual until someone can.
Process first
Your HubSpot mirrors your process
If stages, handoffs or reports keep breaking, the fix starts with the process.
FAQ
How do I see how long MQLs wait in HubSpot?
Filter contacts by lifecycle stage Marketing Qualified Lead and sort by Date entered Marketing Qualified Lead. Add Owner assigned date and Last contacted to see whether each lead got an owner and a first touch. On Professional or Enterprise, the time in stage properties give you the waiting time directly.
Who owns lead status definitions, marketing or sales?
Sales should own lead status values, because they describe what sales is doing with a lead. Marketing and sales should jointly own the MQL and SQL definitions. One person, often the RevOps lead or HubSpot admin, should own the written rule and keep the portal in line with it.
What is a good MQL to SQL handoff process in HubSpot?
A written definition of a marketing qualified lead, a clear owner at handoff, a response time both teams agree on, and a path for rejected leads. HubSpot then records the result in lifecycle stage, contact owner and the stage dates. The tool follows the rule; it does not replace it.
This week, build the MQL view and count the three groups. Take the numbers to one meeting with your heads of sales and marketing and leave with a written handoff rule and a named owner. The workflows can wait until that page exists.
Related reading
Alignify
On this page
Get the audit checklist
All 25 checks as a spreadsheet with auto-scoring.
Talk to Alignify
45 minutes, your portal on screen, no slides. We show what we would fix first.