How to export your contacts from GoHighLevel

GoHighLevel migrations are really several small migrations: one per sub-account. The good news is that each one is simple, and doing them client-by-client keeps every move verifiable.

What exports from GoHighLevel

Each sub-account's contacts export to CSV from its contacts view — as of August 2026 that's a select-all-and-export flow, and GHL's help docs keep the current path. The columns include standard fields, custom fields, and tags. The agency-shaped advice:

1. One client at a time. Export a client, import them into their own workspace on the destination, send one campaign, and check the numbers before touching the next client. A staged migration you can verify beats a heroic weekend cutover.
2. Bring the opt-in fields. DND status and consent-related fields matter more than any custom field — they're what keeps the first send from the new platform compliant.
3. Screenshot the automations that matter. Workflows don't export as anything importable, but a screenshot per money-making automation makes the rebuild an afternoon instead of an archaeology project.

What doesn't carry over

Funnels, websites, snapshots, and the phone system stay in GHL — they're platform infrastructure, not portable data. Plenty of agencies deliberately keep funnels where they are and point them at the new platform's keywords and forms.

Importing your list into AutoCampaign.ai

Wherever you land, the import side is the easy half here: upload the CSV or Excel file, map your columns once, and tags and custom fields become attributes you can segment on immediately. Opt-in status is recorded on every imported contact, STOP requests are honored automatically from the first send, and your first campaign shows its estimated cost before you press send.

If you're still deciding where to go, our GoHighLevel comparison is the honest version — including the cases where staying put is the right call. The pricing grid is public, so you can do the math before you create an account.