GHL → Local Lead Legend Migration

GoHighLevel (GHL) is the reference implementation Local Lead Legend mirrors one-for-one. Migrating a client off GHL means standing up the equivalent Local Lead Legend 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 Local Lead Legend. If you repoint the funnel to Local Lead Legend-only before Local Lead Legend’s auto-response and lead-notification are live, leads land silently (dark leads). Stand up Local Lead Legend’s notify + auto-reply path first, then repoint.

Migration checklist

1. Create the subaccount. Provision the client’s Local Lead Legend 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 Local Lead Legend (only after step 4).
6. Rebuild automations. Recreate the GHL workflows as Local Lead Legend 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 Local Lead Legend.

Parity reference

Where Local Lead Legend 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.