Skip to main content
Product screenshot showing CRM properties, pipeline stages, and sync checks. Use reorder and delete controls only after checking the source CRM and downstream deal impact. Stage order affects board display and admin expectations; stage IDs, descriptions, and controls matter more for writeback and classification.

Who can use this

  • RevOps, sales operations, CRM owners, and admins with CRM permissions.

Before you start

  • Use a CRM account that can read and update the fields Ergo needs.
  • Map properties, pipelines, and stages before enabling broad CRM automation.
  • Test changes on one record before rolling them out.

Steps

  • Confirm whether your connected CRM supports direct stage edits from Ergo.
  • Reorder stages to match the source CRM process.
  • Check whether deals currently sit in a stage before deleting it.
  • Resolve CRM-side drift before making additional edits.
  • Retest board filters and a single CRM update after the change.

What to expect

  • Edit-mode changes can write directly to supported CRMs.
  • Deleting a stage can also remove or update stage references in Ergo configuration.
  • Stage display order and stage IDs are separate; both matter.
  • CRM-side stage changes may require a manual resync before Ergo’s configuration reflects them.

Common issues

  • A CRM admin already changed the stage in the source CRM.
  • A deleted stage still has deals or exit-point references.
  • Stage names were reordered but descriptions were not reviewed.
Last modified on June 8, 2026