# Pipelines and stages (/docs/en/pipelines)

Deals can be split into several pipelines, such as new business and renewals. Each pipeline has its own stages. For the list itself, see [viewing and organizing records](/docs/en/records).

## Switch pipelines [#switch-pipelines]

When there are two or more pipelines, a **Pipeline** selector appears in the deal list header.

- The table, kanban and timeline show only deals in the selected pipeline. Kanban columns are that pipeline's stages.
- The selected pipeline is kept in the URL.
- It does not apply to the “My deals”, “Due soon” and “No next step” focus tabs.
- When you create a deal, you also choose its pipeline (the one selected in the list is the default), and pick a stage from that pipeline.

## Required fields for a stage [#required-fields-for-a-stage]

Each stage can have **Required fields** that must be filled in before a deal moves into it.

If you move a deal on the kanban, or pick a stage on the record, and a required field is empty, “Fill in before moving to …” appears. Fill in the fields and select **Save and move** to save the values together with the stage.

- Bulk updates do not show this form; they only show why the deals couldn't move.
- A deal can't move to a stage that isn't in its pipeline.

## Manage pipelines and required fields [#manage-pipelines-and-required-fields]

People who can change the object design (organization admins) edit them from **Manage attributes** on deals.

- **Pipelines:** Add, rename, reorder and delete pipelines. The first one is the default. A pipeline that still has stages, or that deals use, can't be deleted; move those deals to another pipeline first.
- **Stages:** For each stage, choose its pipeline (when there are two or more) and its **Required fields** (any fields of the same object). The stage type (Open / Won / Lost) is set here too.

A deal created without a pipeline goes into the pipeline of its stage, or the first pipeline if it has no stage.