Agiled Docs

Pipelines define the sales processes your team uses for deals.

Use separate pipelines only when the sales process is meaningfully different. Too many pipelines make reporting and stage management harder.

Create A Pipeline

Open Settings.
Go to Pipelines or CRM Pipelines.
Select Create Pipeline.
Enter a pipeline name.
Add a description if helpful.
Add at least one stage.
Save the pipeline.

Before adding the pipeline, decide who owns it, what qualifies a deal to enter it, and what counts as won or lost. A pipeline should model a real sales process, not a reporting label that users must guess about.

Create a pipeline only when deals need a different set of stages, probabilities, owners, or reporting rules. If the process is the same but the customer segment is different, use fields, tags, saved views, or reports instead.

Design the Stages First

Write the stages in order before creating the pipeline. Each stage should answer one question: what must be true for a deal to be here?

Good stages are action-based, such as Qualified, Proposal sent, Negotiating, and Won. Avoid vague stages such as Important or Follow up because they do not describe where the deal is in the sales process.

Decide the default probability for each stage if your reports use forecast value.

Add clear won and lost outcomes before the pipeline goes live. Without consistent end states, sales reports cannot separate active opportunities from closed history.

Set A Default Pipeline

Use Set as Default on the pipeline that should be selected first when users create deals.

The default pipeline affects new deal creation. It does not automatically move existing deals from other pipelines.

Review the default pipeline before onboarding new sales users or importing deals. A wrong default can send new opportunities into the wrong process before anyone notices.

Delete A Pipeline

You cannot delete the default pipeline. Set another pipeline as default before deleting. If a pipeline is in use, confirm where its deals should move before removing it.

Review workflows, saved views, reports, imports, and team instructions before renaming or deleting a pipeline. Existing automation may depend on pipeline or stage names.

Migrate Deals Between Pipelines

When changing pipeline structure, move a small set of deals first and confirm they land in the expected stages. Then move the remaining deals in batches.

After migration, review saved views, deal reports, workflow conditions, and sales team instructions. A renamed stage can break a process even when the deals themselves still exist.

If the old and new pipelines have different meanings, add a note to affected deals or sales handoff docs so future reviewers understand why the deal moved.

Review Pipeline Health

Periodically review stage names, probabilities, automation rules, and reports. If users keep creating workaround stages or ignoring a pipeline, simplify the pipeline before adding more automation.

Healthy pipelines have clear stages, realistic probabilities, and active deals with next steps. If many deals stay in one stage for too long, review whether the stage is too broad or whether owners need a follow-up routine.

Before Renaming

Before renaming a pipeline:

check open deals
check saved views and reports
check imports that map to pipeline names
check workflows that reference the pipeline
tell the sales team what changed and when to use the new name

Manage CRM Pipelines