Loading
By Latha Kumaresan · DirectorReviewed 23 September 2026
In short
What are multiple pipelines in a CRM?
Multiple pipelines let one CRM run separate sales processes side by side — typically new business, renewals and partner-sourced deals. In Treepie Flow each pipeline has its own stages, stage probabilities and required fields, while every pipeline reads the same companies, contacts and activity. One customer can have an expansion deal and a renewal open at the same time, and the forecast weights each by its own odds.
- Separate per pipeline
- Stages, probabilities, required fields, scoring rules, automations
- Shared across pipelines
- Companies, contacts, activity, quotes
- Forecast
- Per pipeline or combined, each weighted correctly
- Moving deals
- Between pipelines, with full history kept
Why this exists
Why one pipeline cannot serve every sales motion
A single pipeline forced to serve several motions ends up with stages that mean different things to different teams. Renewals do not have a discovery stage. Partner deals do not qualify the same way. Bending one pipeline to fit all of them is how stage names stop meaning anything.
What it does
How multiple pipelines work
Separate pipelines for separate sales motions — new business, renewals, partner-sourced — each with its own stages, probabilities and required fields, all reading the same customer records underneath.
Each pipeline defines its own stages, entry criteria and probability weighting. A customer can have deals in more than one at once — a renewal and an expansion — without either being duplicated, because both point at the same company record.
In practice
Running new business and renewals together
A company runs three: new business with a six-stage qualification path, renewals with three stages and no discovery, and partner-sourced deals that enter already qualified. Kanaka Foods has a deal in two of them at once. Both point at the same company record, so the renewal knows about the expansion and support load is visible to whoever is working either.
Specifics
ReadsDeals across every pipeline
WritesPipeline, stage set, entry criteria
PermissionsAdmin defines, reps use
What it does not do
Separate pipelines will not fix a team that disagrees about what a stage means — they will localise the disagreement, which is usually enough to resolve it. Splitting a pipeline for every product line tends to produce forecasts nobody can combine; two or three motions is the range most companies actually need.
How it connects
See the Flow journeys →How pipelines roll into one forecast
Forecasts can be read per pipeline or combined. Because the underlying customer is shared, a renewal deal knows the support load and open invoices on that account without anyone joining two reports.
Treepie LoopA won deal opens the project on the sold scope — the same lines, not a summary of them.Treepie BooksThe agreed quote becomes the invoice schedule, including the milestones nobody wants to argue about twice.Treepie DeskA ticket opens carrying the account, the contract and whatever is currently in delivery for them.Treepie GrowthThe page that sourced the deal keeps the credit, right through to closed revenue months later.
Setting it up
Flow · Moving your pipeline in takes four days.Day 1Decide the stagesBefore any import. Stage names are the one thing here that is genuinely painful to change in month three.
Day 2Import into a sandboxDeals, contacts and three years of closed history, mapped and checked before anybody logs in.
Day 3Wire the routingForms, inbox and owner rules, so a new lead lands on a person rather than in a queue nobody reads.
Day 4Let the team inSales first, then whoever reads the forecast. The old CRM stays readable for a month.
Who it is for
Built for teams that sell more than one way.
Account managersRun renewals and upsells in stages that describe them, without new-business steps in the way.“Which renewals are due in the next 90 days?”
Partner managersTrack partner-registered deals with the partner as a required field and their own stages.“Which partner sourced the most revenue this quarter?”
Sales leadersSee each motion’s pipeline on its own, and the combined number finance reads.“What is renewals coverage against target?”
RevOpsSet probabilities per pipeline so the forecast stops averaging unlike deals.“Why was last quarter’s renewal forecast so low?”
Running several sales motions, three ways.
| One pipeline for everything | A separate tool per team | Treepie Flow | |
|---|---|---|---|
| Stages | Every stage for every motion, most skipped | Right stages, different systems | Right stages per pipeline, one system |
| Probabilities | One set for all deals | Separate, but never combined | Per pipeline, combined correctly |
| Customer record | One, but cluttered | Duplicated in each tool | One record read by every pipeline |
| Forecast | Under- or over-weights renewals | Added up by hand | Weighted per pipeline, totalled automatically |
| Moving a deal | No structure to move between | Re-typed into the other tool | Moved with its history intact |
Is there a limit on pipelines?
Unlimited per account, with up to twenty stages each.
Can a deal move between pipelines?
Yes, and the move is recorded. Stage mapping is chosen at the point of the move rather than guessed.
Does each pipeline need its own forecast?
It can have one, and they roll up. Reading them separately is usually more useful because the motions convert at different rates.
How many pipelines should we have?
One per genuinely different way of selling — usually new business, renewals and, if you have them, partner deals. Splitting by team or region is better handled with filters and permissions.
Can each pipeline have its own stages?
Yes. Stage names, order, entry criteria and probabilities are all set per pipeline.
Can reps work in more than one pipeline?
Yes. A rep sees every pipeline they have access to, and can view their deals across all of them at once.
What happens to reports when we add a pipeline?
Existing reports keep working and gain a pipeline filter. Combined reports weight each pipeline by its own probabilities.
Can automations differ between pipelines?
Yes. Stage automations belong to a pipeline’s stages, so a won renewal can raise an invoice while a won new-business deal opens a project.
Do separate pipelines create duplicate companies?
No. Pipelines hold deals; companies and contacts are shared, so a company appears once however many pipelines it is in.
Can we have different required fields per pipeline?
Yes. A partner pipeline can require the partner, a renewals pipeline the contract end date, without forcing those fields on anyone else.
Are multiple pipelines a paid add-on?
No. They are part of Flow; the pricing page lists which plan includes each feature.
More in Pipeline & deals
Full feature list →Pipeline & dealsStage automationStage automation runs a defined action when a deal enters or leaves a stage: create a task, draft a quote, notify a person, open a Loop phase or raise a flag for review.Pipeline & dealsPipelines & stagesPipeline & dealsDeal recordsPipeline & dealsWeighted forecastingPipeline & dealsDeal splitsPipeline & dealsWin/loss reasons
Easier to see Multiple pipelines running on your own records than to read about it.
Fourteen days, every module, no card. Or half an hour with someone who will run it on your own records and tell you where it does not help.