GHL → Iron Migration

GoHighLevel (GHL) is the reference implementation Iron mirrors one-for-one. Migrating a client off GHL means standing up the equivalent Iron surfaces, repointing the lead flow, and only then cancelling GHL — losing nothing in the process.

The dual-write trap

A client’s funnel may dual-write to both GHL and Iron. If you repoint the funnel to Iron-only before Iron’s auto-response and lead-notification are live, leads land silently (dark leads). Stand up Iron’s notify + auto-reply path first, then repoint.

Migration checklist

1. Create the subaccount. Provision the client’s Iron org (agency-parented). See Subaccounts & X-Org-Id.
2. Import data. Import contacts (and, where applicable, opportunities). Use POST /contacts/import.
3. Provision a number. Buy and configure the client’s Telnyx DID (A2P registration, voice profile), then wire it into the tenant and lead-alert config. See Telephony.
4. Stand up notify + auto-reply. Configure the org’s lead-alert (so a new lead notifies the operator) and, if desired, the setter in suggestive mode for first-touch. See Setter.
5. Repoint the funnel. Switch the funnel to write to Iron (only after step 4).
6. Rebuild automations. Recreate the GHL workflows as Iron automation rules / workflows. See Automations.
7. Verify end-to-end. Submit a test lead and confirm the contact lands, the operator is notified, and the auto-reply / suggested draft fires.
8. Cancel GHL. Only once the client’s flow is fully live on Iron.

Parity reference

Where Iron has a GHL-parallel surface (inbox, pipelines, calendars, snapshots, custom values, the social planner), it mirrors GHL’s information architecture and interaction model. Snapshots capture a full GHL-style bundle (pipelines, stages, tags, custom fields, automations, calendars, permission sets) for reuse across subaccounts.

Draft

This guide is the operator-level playbook. Per-client specifics (number provisioning recipes, funnel repoint details) live in the internal runbooks and are summarized here.