Set up multiple sales pipelines
Configure separate pipelines for sales, renewals, onboarding and any other deal flow you run. Each pipeline has its own stages and per-stage probabilities, and deals can move between pipelines without losing their history.
In this guide
CRM- Steps
- 5
- Prereqs
- 3
- Pitfalls
- 3 common ones
- Related
- 3 guides
Walkthrough only — no setup wizard. The flow is exactly what you do inside YionStack today.
Before you start
- CRM module enabled on your business (Business plan and above).
- Owner or Admin role — pipeline definitions are business-wide configuration.
- A list of the stages you want for each pipeline, with a default probability for each stage.
Steps
- 1
Open the pipeline editor
Go to CRM → Settings → Pipelines. The default Sales pipeline is shown with its current stages; this is the pipeline new deals land in unless you change the default.
- 2
Add a new pipeline
Choose New pipeline. Give it a name (Renewals, Onboarding, Partner referrals) and a colour so it is visually distinct on the deal list.
- 3
Define the stages
Add the stages in order. For each stage, set the default probability (the chance a deal at that stage closes; YionStack uses this for the weighted-pipeline forecast). Set the won and lost stages explicitly — those are the only stages that move money or close the deal.
- 4
Move existing deals
On any deal, change its pipeline from the deal header. The deal moves to the matching stage on the new pipeline (or the closest match if exact names differ). The stage-history is preserved so the velocity report continues to read both pipelines side by side.
- 5
Set the default per team
On Settings → Teams, you can pick which pipeline new deals from each team land in by default — sales-team deals go to Sales, customer-success-team deals go to Renewals, partner-team deals go to Partner referrals.
Common pitfalls
Overlapping stage names
If two pipelines share a stage name (both have "Proposal"), reports group them together unless you disambiguate. Either give each stage a unique name or filter reports by pipeline.
Won/lost stages
Every pipeline needs exactly one Won stage and one Lost stage. Without them, deals on that pipeline cannot close, and the invoice does not auto-create on Won.
Probability collapse on move
When moving a deal between pipelines, the per-stage default applies on arrival — any per-deal probability override resets. If the override mattered, set it again after the move.
Need a hand with this one?
If a step is missing or unclear, tell us — every guide is a working document we improve as customers ask.