Pipeline lifecycle
Create, rename, reorder, restore, archive, and choose the default pipeline. In-use stages and pipelines are protected by server dependency checks.
CRMAvailable
CRM configuration
Manage lead pipelines, stable stage references, and the shared form data-field catalog without orphaning active leads or published forms.
What you can do here
Stage outcomes
Every pipeline keeps at least one open, won, and lost stage so routing and conversion reporting remain meaningful.
Shared data fields
Create custom fields, relabel or override standards, review form usage, deactivate unused fields, and reset safe standard overrides.
Follow these steps
Change a pipeline
- Open a pipeline and review the lead count for every stage.
- Reorder or relabel stages while retaining stable codes.
- Move leads out of a stage before removing it, then save.
Manage a data field
- Search by label, key, or group and open the field.
- Review every form that uses it before changing availability.
- Deactivate only after published-form usage is cleared.
Helpful habits
- Treat stage codes and data-field keys as immutable references.
- Preview dependencies before archive, removal, or deactivation.
- Use the default pipeline only for the primary inbound lead path.
Tips
- Archived pipelines can be restored when they contain no active dependency conflict.
- Historical form submissions retain self-describing field snapshots.