The Leads object, on Sales Hub Professional or Enterprise, gives every qualification attempt its own record, associated with a contact or a company, that moves through a lead pipeline until it is qualified into a deal or disqualified. Use it for the pre-deal work reps do, keep lifecycle stage for the funnel, and decide up front who creates leads, who owns them, and what counts as qualified.
In our CRM and RevOps work, the Leads object is a design decision we make before anyone opens settings. The HubSpot implementation guide puts the object model first for the same reason: reports can only use the records you create. This page is that decision for pre-deal work, then the setup in the order we run it, then the rules that keep the index clean.
What the Leads object is and which plans have it
A contact is a person. A company is an account. A deal is a transaction with an amount, a close date, and a stage on a deal pipeline. A lead is the qualification attempt that sits in front of that deal. HubSpot describes leads as the progress of an associated contact or company through sales qualification. A lead ends qualified or closed, and it can be associated with multiple contacts or companies, or with one deal (how objects work, checked 19 Nov 2026).
A lead needs a primary association with a contact or a company (create leads, checked 19 Nov 2026). The contact stays the person you email. The lead is the attempt: this product, this motion, this quarter. HubSpot's own example is a contact interested in more than one product line, with a separate lead record for each process.
Using leads requires Sales Hub Professional or Enterprise (create leads, how objects work). The same tier is on the lead properties page, the ownership sync page, and the lead pipeline automation page. What those tiers cost is in the HubSpot pricing guide. Below Sales Hub Professional, qualification stays on the contact. Teams moving onto this tier as part of a HubSpot migration should decide the lead model before the first import. The cutover order is in the section on moving from lead status below.
Because a lead is an attempt, one contact can carry several leads across a year, or across two motions at once. The contact record does not reset when a deal is lost. A new lead starts the next attempt with its own stage, its own owner, and its own dates.
Reps work those records from the Leads tab in the Sales Workspace. Creating a lead there needs an assigned Sales seat and Leads tab permissions. Creating from the contacts index needs a Sales seat. Creating from the leads index needs edit permissions for leads (create leads). Who holds those seats and grants is the user permissions guide.
Leads object, lifecycle stage and lead status
These three fields answer three different questions. Mixing them is how a funnel report and a rep's queue start disagreeing.
Lifecycle stage is where a contact or company sits in the marketing and sales process. HubSpot's default stages, in order, are Subscriber, Lead, Marketing Qualified Lead, Sales Qualified Lead, Opportunity, Customer, Evangelist, and Other. Default automatic updates only move the stage forward. Forms, imports, workflows, the API, and the Salesforce integration will not set an earlier value until you clear the current one (lifecycle stages, checked 19 Nov 2026).
Lead status is narrower. HubSpot describes it as the sub-stages inside the Sales Qualified Lead lifecycle stage. The default options are New, Open, In Progress, Open Deal, Unqualified, Attempted to Contact, Connected, and Bad Timing (lifecycle stages).
A lead record is the attempt itself, with its own pipeline. The default Lead pipeline has five stages: New, Attempting, Connected, Qualified, and Disqualified (pipelines, checked 19 Nov 2026).
Our recommendation: lifecycle stage stays the funnel. The lead pipeline carries rep-level qualification. If you adopt the Leads object, stop running Lead Status in parallel for the same job. Two fields that both mean "the rep is attempting" have to be kept in step by hand, and a saved view that filters on one can disagree with a view on the other. Keep Lead Status only if you are below Sales Hub Professional and have no lead records. The longer comparison of the two contact properties is the lifecycle stage and lead status guide. Once a lead is qualified, the deal pipeline takes over, which is a separate stage design in the deal stages guide.
Setting it up, in order
On Enterprise, build and test this in a standard sandbox before it reaches the portal the team uses. The sandbox guide covers what copies across and what you redo by hand. The steps below are the order we use.
1. Activate the object. A Super Admin turns leads on. In the account, go to Data Management, then Data Model. If the account shows a More menu, that is More, then Data Management, then Data Model. Click Edit Data Model. In the graph view, open leads and click Activate object. In the table view, use the three dots on leads, then Activate object, then Confirm (create leads).
2. Decide on one pipeline, knowing what a second one gives up. Managing lead pipelines requires a Professional or Enterprise subscription, and creating or editing pipelines requires Edit property settings permissions (pipelines). HubSpot's guidance on extra pipelines is narrow: separate pipelines only when the processes have unique stages. If two teams share the same stages, one pipeline plus permissions is the recommended setup.
The automation trade-off is the reason we stay on the default Lead pipeline unless the stages truly differ. Lead stage automation only progresses leads in the default pipeline. Leads in a custom pipeline are not eligible for that default automation (pipelines, lead pipeline automation, checked 19 Nov 2026).
Two progressions ship on and cannot be modified. A lead moves to Attempting when a user completes outreach by sending or logging an email or a call, or by logging a message on SMS, LinkedIn, or WhatsApp. A lead moves to Connected when the contact replies to an email, when a booked meeting has its outcome set to Completed, or when a user logs a call outcome of Connected. If someone moves that lead backward by hand, later activity will not move it forward again. HubSpot's example is a lead moved back to New: a later Connected call does not return it to Connected (lead pipeline automation).
The same article then shows switches for those two moves, under the pipeline's Automate tab, Templated Automation. Each switch asks which stage the lead moves from, which stage it moves to, and which events count. We leave both switches on for the default pipeline. On a custom pipeline, plan the stage moves yourself.
3. Set the stages, and require a reason on Disqualified. The default five are enough for most B2B motions: New, Attempting, Connected, Qualified, Disqualified. When you add a stage on a lead pipeline, you mark it Open or Closed. Deals are the object that uses probability instead (pipelines).
Conditional stage properties force a field when someone creates a record in a stage or moves a record into it. On the pipeline, hover the stage, add a rule, pick the property, tick Required, and save. A required property blocks the create or the move until it has a value. Edit property settings permissions are required. Read-only properties, such as scores, cannot be stage properties (pipelines). We require Disqualification Reason on Disqualified. Qualified is handled by the deal rule in step 8, because a dropdown on the lead is a weaker handoff than a deal record.
4. Agree Lead Type and Lead Label before the first record. Both are dropdowns you can edit in lead property settings. Lead Type is the list the automation uses when it creates a lead. Lead Label is described as the current status of the lead, and you can add labels in property settings (default lead properties, checked 19 Nov 2026). The create panel asks for both (create leads). We write the allowed values down first. A rep-invented label on day one becomes a filter nobody else can read.
5. Edit Disqualification Reason, and keep the note beside it. Disqualification Reason is a list you can edit or extend in lead property settings. Lead Disqualification Note is the free-text field next to it (default lead properties). The list is what you report on. The note is why this particular record was closed. Reasons that should come back later, such as timing, are the ones you select for the follow-up automation below.
6. Decide owner sync and activity sync. By default, lead owner is independent of the contact owner and the company owner. The person who owns the contact may not own the lead, and activities on the contact or company do not copy onto the lead until you turn sync on (sync lead ownership and activities, checked 19 Nov 2026). The properties article also says Lead Owner defaults to the owner of the primary associated contact, and if that owner is missing, to the owner of the primary associated company (default lead properties). Read both before you choose. Creation can inherit an owner. After that, the two owners stay independent unless sync is on.
The path is settings, Data Management, Objects, Leads. Super Admin or Edit property settings permissions are required. Two switches:
- Sync lead owner with contact and company owner. Turning it on asks whether to update existing open leads. Say yes only if you want that backfill. While the switch is on, a lead created from the Sales Workspace or the leads index must be tied to a contact or company you own. The create-leads article states the same limit, and it uses the switch name "Sync lead owner with contact or company owner" (create leads). If the lead is closed, later owner changes do not sync.
- Sync lead activities with lead owner. An activity associated with a company and not with a contact does not sync. Email, meeting, call, SMS, and WhatsApp activities sync only when the associated contact has an open lead, meaning the lead has not been qualified or disqualified. HubSpot checks that status at the moment the activity is associated. Activity logged after qualification or disqualification stays on the contact unless someone associates it to the lead by hand.
We turn both switches on when the same person should own the contact and the lead, and when outreach logged on the contact should appear on the open lead. We leave owner sync off when a qualifier owns the lead and someone else owns the contact. That split is a choice. Leaving the switch off by accident is how the two owners diverge.
7. Turn on automatic creation only for the stages that deserve a rep. On the pipeline's Automate tab, under Templated Automation, turn on Create a lead. Pick the Lead Type, pick the lifecycle stages that should create a lead, and save. This does not create a lead when the contact's lifecycle stage changes because of company lifecycle stage syncing (lead pipeline automation).
A second switch, Create a lead for follow-up, lives on the Leads object Setup tab, under Creating leads. Pick the Lead Type and the disqualification reasons that should spawn a new lead, then save. Use it for reasons you want worked again. Leave it off for reasons that should stay closed.
Workflows can create leads too. Add a Create record action and choose Lead. Lead records can only be created from a contact-based or a company-based workflow. The Lead option does not appear on ticket-based or deal-based workflows. The enrolled record must carry a Primary contact or Primary company association label. HubSpot recommends filling Lead Label and Lead Pipeline Stage on that action. Leads in this action require Sales Hub Professional or Enterprise (create records with workflows, checked 19 Nov 2026). The create-leads article points at the same action (create leads). How we structure the workflow itself, including enrollment and suppression, is the workflows playbook.
You can also enroll leads in a lead-based workflow. Leads are a workflow object type on Sales Hub Professional or Enterprise (workflow object types, checked 19 Nov 2026). Stage actions are configured on the pipeline: Automate tab, Create workflows from scratch, then an action on the stage. The action list includes tasks, emails, delays, branches, communications, marketing, CRM, and data actions. That setup needs an assigned Sales seat, and Super Admin or Account access permissions (lead pipeline automation). Deal-stage automation stays on the deal pipeline, covered in the deal stages guide.
8. Require a deal when the lead reaches Qualified. Pipeline rules are set per pipeline, by a Super Admin. Open the lead pipeline, then the Pipeline Rules tab, and turn on Require a deal to be created. The user must create a deal if the lead stage is Qualified. Enforcing that rule requires Sales Hub Professional or Enterprise (pipeline rules, checked 19 Nov 2026). A lead can have only one associated deal. The Associated deals property is a count HubSpot maintains, and the article states the cap of one (default lead properties).
The same rules page lists other controls that apply to lead pipelines: limit creation to specific stages, restrict skipping stages, restrict moving backward, and limit who can edit records in selected stages. For the skip and backward rules, the article says users can still move to, or reopen from, a Closed stage, and it names those lead stages Qualified or Unqualified. The default pipeline calls the closed stage Disqualified. Check the name in your portal before you rely on the exception. Rules apply on desktop, in the mobile app, and through integrations or the public APIs when a user ID is passed. With a rule on, users cannot bulk-edit pipeline or stage. Super Admins and users with Edit property settings permissions can bypass every rule except deal approval. Workflows and API edits can bypass them. If a workflow qualifies leads, create the deal in that same workflow.
Permissions, collected. Super Admin activates the object and sets pipeline rules. Edit property settings creates pipelines, conditional stage properties, and the two sync switches. A Sales seat is required to create leads from the contacts index and from the Sales Workspace. The Sales Workspace also needs Leads tab permissions. The leads index needs edit permissions for leads. Stage-based workflow actions need a Sales seat plus Super Admin or Account access. The user permissions guide is where those grants should be bundled into a role.
Rules that keep leads clean
The settings above will create a lead for every contact who hits a lifecycle stage you select. Write the rules before you turn that on. The lead management process is the place those definitions live. The object enforces them.
When a lead gets created. A hand-raiser, a booked meeting, or a contact a rep is about to work gets a lead. Hold imports, list uploads, and enrichment passes until a rep is going to work the contact. The lifecycle-stage automation is how we express that: pick Marketing Qualified Lead, or Sales Qualified Lead, or whichever stage already means "sales should touch this." Subscriber and Lead are the wrong triggers for a sales queue.
One open lead per contact per motion. HubSpot allows several leads on one contact. The product-line example on the create-leads page is the case for that. The create-leads page does not describe a block on a second open lead for the same contact and the same motion, so we set that limit ourselves. Before a workflow or an integration creates a lead, it looks for an open lead already tied to that contact for that motion. The Open leads property is HubSpot's flag for a lead that is still open: 1 when the stage category is anything other than qualified or unqualified, and 0 when the stage is qualified or unqualified (default lead properties). The duplicate check is ours to build.
Assign an owner on purpose. Routing belongs on the lead, with the contact owner following it only if you turned sync on. The patterns for who gets the record are the lead routing rules guide. Speed is a separate promise: Owner Assigned Date is the latest date an owner was set, and Time to First Touch is the time from lead creation to the first outreach activity, both maintained by HubSpot (default lead properties). How we treat that interval is the speed to lead guide. Reps who work the attempt from a sequence show up on Primary contact enrolled in sequence, which HubSpot sets to true while the primary contact is enrolled (default lead properties). The sequence design itself is the sequences guide.
Qualified means a deal. We define qualified as "a rep would open a deal on this." The pipeline rule in step 8 makes that definition physical: the stage does not stick without a deal, for anyone the rule applies to. One lead, one deal. If the same contact later starts a second motion, that is a new lead and, when it qualifies, a new deal. The deal stages guide picks up at the moment the deal exists.
Disqualification has a next step. Every disqualification uses a value from Disqualification Reason. The list is what a report can group. The note explains this one record. Reasons you intend to work again, usually timing, go on the Create a lead for follow-up switch, with a Lead Type that makes the new record obvious. Reasons that should leave sales, such as a bad fit, stay off that switch and go to a nurture path on the contact. Leave the contact's lifecycle stage where it is. The nurture workflow lives in the workflows playbook.
Leads created by integrations or enrichment. A Clay write into HubSpot, or an n8n workflow that upserts contacts, creates a lead only when the automation says so. An enriched row should match an existing contact and stop, which is the pattern in the Clay write-back guide. When an automation does create the lead, it uses the same criteria as the lifecycle-stage rule, through a contact-based workflow or through n8n on a path you have already tested. API edits can bypass pipeline rules, so put the duplicate check in the automation as well.
Reporting on leads
Report the attempt, and leave the funnel on lifecycle stage. The default properties that carry the attempt are all maintained by HubSpot (default lead properties):
- Time to First Touch, First Outreach Date, and Outreach activity count, for speed and effort.
- Call Count, Email Count, Meeting Count, and Message Thread Count, for what the effort was.
- Disqualification Reason, for why attempts closed without a deal. Lead Disqualification Note is the comment, and it will not group cleanly in a chart.
- Associated deals, Open deal amount, and Closed won deal amount, for the handoff. Associated deals never counts past one.
- Source lifecycle stage, for which funnel stage the contact was in when the lead was created.
- Owner Assigned Date, Lead Owner, and HubSpot Team, for who had the work.
- Date entered, Date exited, Latest time in, and Cumulative time in, per stage. While a lead is in a stage, Latest time and Cumulative time do not include the current stay. They update when the lead leaves.
Stage calculated properties, including those lead stage times, can be used in views, segments, workflows, and reports. The article's own example is an advanced filter in the Sales Workspace for leads that have spent more than two weeks in a stage, and it says similar triggers work in a lead-based workflow. It also says a Service Hub Professional or Enterprise subscription is required to use service and lead stage calculated properties (stage calculated properties, checked 19 Nov 2026). If the portal has Sales Hub and not Service Hub, confirm those properties are available before you build a report on them. The property definitions themselves are also on the default lead properties page.
The sales analytics suite, on Sales Hub Starter, Professional, and Enterprise, has the reports we use alongside those properties. The path is Reporting, then Reports, then Sales (sales analytics reports, checked 19 Nov 2026).
- Lead funnel tracks the time from initial contact to deal conversion. The Leads tab is for how the team is managing progress and conversion. The Lead journey tab visualizes movement through stages, and the stage picker on that tab is lifecycle stages. That tab shows the contact funnel, which is why lifecycle stage still has a job after you adopt leads.
- Team activity includes a Leads group: count of leads enrolled, open leads, average time to first touch, average time to book a meeting, and average touches per lead.
- Lead response time measures the gap between a contact being assigned to a user and that user's first interaction. It resets if the contact is reassigned. Use it as a contact-owner measure. The lead-pipeline numbers sit in Team activity and in the lead properties above.
Custom funnel reports choose contacts, companies, or deals as the data source. The standard stages are lifecycle stage or deal stage (custom funnel reports, checked 19 Nov 2026). Build the lead-to-deal view from lead properties and the sales analytics reports above. Keep the board-level funnel on lifecycle stage. How we lay the dashboard out is the HubSpot dashboard guide.
Moving from lead status to the Leads object
Cut over in this order. Do the mapping on paper before you activate anything in production.
- Map each Lead Status value you actually use onto a lead stage. A mapping we use: New and Open land on New. Attempted to Contact lands on Attempting. In Progress and Connected land on Connected. Open Deal lands on Qualified, and only where a deal already exists. Unqualified and Bad Timing land on Disqualified, with a Disqualification Reason you agree in the same sitting. This is our map. Adjust it to the values your portal actually contains.
- Decide the open Sales Qualified Leads. Create a lead for the ones a rep is actively working. Leave the dormant ones as contacts until someone picks them up. Creating a lead for every historical Sales Qualified Lead recreates the "every contact" problem on day one.
- Update the workflows, views, and reports that read Lead Status. Enrollment triggers, list filters, and dashboard cards that say "Lead status is Attempting" need a lead-stage equivalent, or they keep steering people to a field you just retired. The workflows playbook is the inventory method.
- Train reps on the Sales Workspace Leads tab: where to create a lead, which stage they are allowed to set, what Qualified requires, and where activity has to be logged so it syncs.
Migrations are the same cutover with an extra object map. Teams coming from Salesforce now have a pre-deal object to map Salesforce leads onto, on Sales Hub Professional or Enterprise. The field-level route is the Salesforce to HubSpot guide, and the project around it is HubSpot migration. Below that tier, the Salesforce lead still has to become a lifecycle stage on the contact, or a custom object. Pick that before the import.
Common Leads object mistakes
Each one is a setup choice that was left implicit.
Creating a lead for every new contact. The index becomes a second contact database, and open-lead counts stop describing work. Fix: automatic creation only from the lifecycle stages that already mean "sales should work this," plus a check for an existing open lead.
A custom pipeline, then surprise that stages do not move. Default lead stage automation does not apply to a custom pipeline. Fix: stay on the default Lead pipeline unless the stages are genuinely different, and if they are different, plan the stage moves yourself. Moving a lead backward by hand also stops later automatic updates for that record. Tell reps that before they drag a card the wrong way.
Owner sync left off by accident. The contact owner and the lead owner then diverge. Fix: decide in step 6. Turn the switch on when they should be the same person, including the prompt that updates existing open leads. Leave it off only when the split is intentional.
Free-text disqualification. A note with no Disqualification Reason cannot be grouped, and the follow-up automation has nothing to trigger on. Fix: require the reason on Disqualified, keep the list short, and put only the reasons you will rework onto Create a lead for follow-up.
Qualifying without a deal. The lead says Qualified and the pipeline has no deal to forecast. Fix: turn on Require a deal to be created, and remember that workflows and API edits can bypass it. Any automation that sets Qualified should create the deal in the same step.
Logging the activity on the company only. Company-only activities do not sync to the lead, and activity after the lead is qualified or disqualified does not sync on its own. Fix: log the email, call, meeting, SMS, or WhatsApp on the contact while the lead is open. Associate anything that misses the window by hand.
If the portal already has years of Lead Status values and the cutover is unclear, that is a reasonable thing to take to a second opinion before you activate the object in production.
FAQ
Which HubSpot plan includes the Leads object?
Sales Hub Professional or Enterprise. That requirement is on the create-leads article and on the objects article, and the same tier is stated for lead properties, ownership sync, and lead pipeline automation. Managing lead pipelines requires a Professional or Enterprise subscription. Requiring a deal when a lead is Qualified requires Sales Hub Professional or Enterprise (create leads, how objects work, pipeline rules).
What is the difference between a lead and a contact in HubSpot?
A contact is the person. A lead is one qualification attempt associated with a contact or a company, moving through a lead pipeline until it is qualified or closed. A lead cannot be saved without that primary association, and one contact can be associated with more than one lead (create leads, how objects work).
Does the Leads object replace lead status?
HubSpot still documents Lead Status as the sub-stages of the Sales Qualified Lead lifecycle stage, with its own default values. The Leads object is a separate record with its own pipeline. Our recommendation is to let the lead pipeline carry day-to-day qualification once you have it, and to stop using Lead Status for that same job. Lifecycle stage stays the funnel either way (lifecycle stages).
Can one contact have more than one lead?
Yes. HubSpot's example is one contact associated with several lead records, one per product line. Leads end qualified or closed. A later attempt is a new lead, and the closed lead stays as history (create leads, how objects work).
Can HubSpot create leads automatically?
Yes. A lifecycle-stage rule, a workflow Create record action, and a follow-up rule after selected disqualification reasons can each create a lead. Create a lead, on a pipeline's Automate tab, fires when a contact moves into a lifecycle stage you select, except when that change comes from company lifecycle stage syncing. Create record works from a contact-based or company-based workflow on Sales Hub Professional or Enterprise, and the enrolled record needs a Primary contact or Primary company label (lead pipeline automation, create records with workflows).
What happens to a lead when it is qualified?
It reaches a qualified outcome. The objects article says leads end qualified or closed. With the pipeline rule on, the user must create a deal when the stage is Qualified, and a lead can be associated with only one deal. Activity logged on the contact after that point does not sync to the lead automatically (how objects work, pipeline rules, sync lead ownership and activities).
If qualification still lives on a contact property and the team cannot point at the open attempt, the Leads object is the piece to design next.