Skip to main content
Pipeline sync is stage-driven. Before Consuelo can sync HighLevel opportunities, each relevant HighLevel stage needs a matching destination stage in your CRM.

​
What gets mapped

The integration stores stage-level mappings, not just pipeline-level mappings. Each mapping includes:
  • the HighLevel pipeline id
  • the HighLevel stage id
  • the destination pipeline id
  • the destination stage id

​
How pipeline sync works

  1. load pipelines and stages from HighLevel
  2. save the stage-to-stage mappings for the workspace
  3. fetch HighLevel opportunities
  4. skip any opportunity whose HighLevel stage is not mapped
  5. create or update the local opportunity sync record for mapped stages

​
What the sync job stores

The opportunity sync table keeps track of:
  • HighLevel opportunity id
  • HighLevel pipeline id and stage id
  • mapped CRM pipeline id and stage id
  • HighLevel contact id
  • monetary value
  • opportunity status

​
Conflict detection

The pipeline sync flow can also check for stage conflicts by comparing the stored HighLevel stage against the current CRM stage for the synced opportunity. Use conflict checks when you want to review differences before a larger sync run.

​
Important limitation

Unmapped HighLevel stages are skipped by design. If a stage is not mapped, Consuelo does not guess where that opportunity belongs.