---
title: "How to set up a HubSpot deal pipeline correctly"
description: "How to set up a HubSpot deal pipeline correctly: stages and probabilities, required stage properties, pipeline rules, access, and the limits per subscription."
url: "https://jetstack.ai/answers/set-up-hubspot-deal-pipeline/"
---

# How do I set up a deal pipeline in HubSpot correctly?

To set up a deal pipeline in HubSpot, go to Settings > Data Management > Objects > Deals > Pipelines, create the pipeline, and add one stage per buyer commitment with a deal probability, ending in Closed won and Closed lost. Then require the properties each stage needs, use pipeline rules to stop skipped or backward stages, and restrict access where teams shouldn't see each other's deals.

![](https://jetstack.ai/images/authors/aditya-kumar.webp)

By [Aditya Kumar](https://jetstack.ai/authors/aditya-kumar/) Founder, Jetstack AI

Updated October 30, 2026

On this page

## What HubSpot supports natively

| Setting                          | Where                                                    | Notes                                                                                                                  |
| -------------------------------- | -------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------- |
| **Create a pipeline**            | Settings > Data Management > Objects > Deals > Pipelines | Needs Edit property settings permissions                                                                               |
| **Stages and probability**       | Pipeline editor, + Add stage                             | Each deal stage has a probability; you must include both a Won and a Lost stage                                        |
| **Conditional stage properties** | Conditional logic rules column                           | Show properties when a deal is created in or moved to a stage; mark them required                                      |
| **Pipeline rules**               | Pipeline Rules tab                                       | Limit where deals can be created, block skipped stages, block moving backward, limit who edits deals in certain stages |
| **Deal approvals**               | Pipeline Rules tab                                       | Sales Hub Enterprise                                                                                                   |
| **Access**                       | Actions > Manage access                                  | Restricting by team needs Professional or Enterprise                                                                   |
| **Clone a pipeline**             | Actions > Clone                                          | Professional or Enterprise                                                                                             |
| **Internal stage IDs**           | Hover over a stage, internal name icon                   | Used by integrations and the API                                                                                       |

HubSpot’s default Sales Pipeline has seven stages, from *Appointment scheduled* (20%) to *Closed lost* (0%). Super Admins and users with Edit property settings permissions can bypass pipeline rules other than deal approval.

## How to set up a HubSpot deal pipeline correctly

1. **Map the buyer’s steps, not your activities.** A stage should mean the buyer committed to something: agreed a meeting, accepted a proposal, started legal review. “Called them” is an activity, not a stage.
2. **Keep it short.** Five to seven open stages is enough for most sales teams. Each stage needs a clear exit test everyone can apply.
3. **Set honest probabilities.** Start with your actual historical win rates by stage if you have them. Won is 100%, Lost is 0%.
4. **Require what the next stage needs.** For example, require *Amount* and *Close date* when a deal enters *Proposal sent*, and *Closed lost reason* on *Closed lost*. Don’t require so much that reps avoid moving deals.
5. **Add pipeline rules.** Block skipping stages if forecasting depends on every stage, and block moving backward past key stages if you report on stage conversion.
6. **Decide on more pipelines only when the process differs**: new business, renewals, partner deals.
7. **Restrict access** if teams shouldn’t see each other’s pipelines.
8. **Note the internal stage IDs** before building workflows, reports or integrations on them.

## Common mistakes

- **Stages for every internal task.** Use tasks and activities instead.
- **Deleting a stage with history.** Move the deals first, and expect stage-based reports to change.
- **One pipeline per rep.** It breaks reporting and multiplies maintenance; use owners and teams.
- **Mixing up deal stage, lifecycle stage and lead status.** They track different things and need different owners.

Once the design is settled, we recommend building it with Jetstack AI Projects rather than by hand; see [how Projects compares with manual implementation](https://jetstack.ai/compare/manual-implementation).

## Where Jetstack AI fits

To build a new pipeline, use Jetstack’s [Projects](https://jetstack.ai/build). Put the stages, probabilities, movement rules and the properties required at each stage in a brief (for example, *Amount* and *Close date* required on *Proposal sent*), approve the plan Jetty (the Projects assistant) writes, then approve deployment separately. **Projects also builds the pipeline’s movement rules:** blocking skipped stages, blocking backward moves and limiting which stages deals can be created in, for every stage or only the ones you name. It builds the properties before the stage requirements that use them, and the receipt confirms each asset, rules included, by reading it back from HubSpot. Deal approvals and pipeline access stay in HubSpot’s settings. Projects is currently in limited release; see [what Projects can build](https://jetstack.ai/docs/projects/capabilities). To standardise a pipeline you’ve already built (see [copying a pipeline to another account](https://jetstack.ai/answers/copy-hubspot-pipeline-to-another-account)), Portal reuse matches an existing pipeline by name, adds missing stages without overwriting existing stage settings, and remaps stage IDs for the workflows that use them. You can deploy the same setup to multiple destination portals, reviewing each portal’s mappings. See [how pipelines are deployed](https://jetstack.ai/docs/implementations/asset-types/pipelines).

## Sources

- [Set up and customize pipelines (HubSpot Knowledge Base)](https://knowledge.hubspot.com/object-settings/set-up-and-customize-pipelines)
- [Set up pipeline rules (HubSpot Knowledge Base)](https://knowledge.hubspot.com/object-settings/set-up-pipeline-rules)
- [Pipelines (Jetstack AI documentation)](https://jetstack.ai/docs/implementations/asset-types/pipelines)

Checked October 30, 2026. HubSpot changes its products often; tell us at <team@jetstack.ai> if something here is out of date.

![Aditya Kumar](https://jetstack.ai/images/authors/aditya-kumar.webp)

About the author

[Aditya Kumar](https://jetstack.ai/authors/aditya-kumar/)

Founder, Jetstack AI

Aditya Kumar is the founder of Jetstack AI, the AI platform HubSpot partners and RevOps teams use to audit portals, build implementations and reuse their best setups across portals. He writes about HubSpot architecture, automation and AI from the work of building it.

[More from Aditya](https://jetstack.ai/authors/aditya-kumar/) [LinkedIn](https://www.linkedin.com/in/aditya-ambrstack/)

HubSpot admin

## 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](https://jetstack.ai/build)

On this page

HubSpot admin

## Related questions.

How do I set up a deal pipeline in HubSpot correctly?

To set up a deal pipeline in HubSpot, go to Settings > Data Management > Objects > Deals > Pipelines, create the pipeline, and add one stage per buyer commitment with a deal probability, ending in Closed won and Closed lost. Then require the properties each stage needs, use pipeline rules to stop skipped or backward stages, and restrict access where teams shouldn't see each other's deals.

How many deal pipelines can I have?

On seat-based subscriptions HubSpot allows 15 custom pipelines on Starter, 100 on Professional and 350 on Enterprise, shared across objects and excluding each object's default pipeline. Free tools get none beyond the default.

Can I delete a stage that has deals in it?

Not until you move the deals and remove anything else that uses the stage. The stage's Used in column shows what's blocking deletion.

Should I create a pipeline per salesperson or region?

Usually not. Create separate pipelines only when the sales process itself differs, such as new business versus renewals. Use owners, teams and properties to split by person or region.
