Skip to content

HighLevel pipeline stages

This article describes working with HighLevel pipeline stages (statuses) in LightLead.

Loading stages

HighLevel pipeline stages contain an identifier, name, and order. Stages are loaded as part of the pipeline during discovery. Changing the stage order in HighLevel requires running discovery again.

Stage structure

Each stage contains:

  • Identifier — a unique stage ID

  • Name — the display name of the stage

  • Order number — the stage's position in the pipeline

  • Pipeline binding — the parent pipeline's ID

Use in reports

Stages are used in LightLead reports to:

  • Analyze the pipeline: track the number of deals/orders/leads at each stage

  • Conversion: calculate conversion between stages

  • Forecasting: estimate potential revenue by stage

  • Grouping: group data by pipeline stage

Working with historical data

Important specifics of working with stages:

  • State snapshot: the current stage is captured at sync time, not the history of transitions

  • Change history: full history of stage transitions may not be available — it depends on the CRM API

  • Deleted stages: deals at deleted stages are preserved in reports, but the stage is marked as unknown

Updating stages

When stages change in the CRM (added, renamed, reordered):

  1. New stages become available after discovery is run again

  2. Renamed stages are updated automatically (matching by ID)

  3. Deleted stages are marked as inactive

Maintained by the LightLead Documentation Team · Last verified: 2026-07-25