Copy a GoHighLevel workflow to another sub-account

Inside one sub-account, workflows can be duplicated. Across sub-accounts, nothing. No export button, no copy-to-location, and the public API doesn’t return the workflow’s step-tree either.

So when you’ve built a 20-step nurture sequence for Client A and Client B needs the same thing, the platform’s answer is: start typing. And hand-rebuilding misses things. A branch filter nobody wrote down. A custom value that resolved differently than you remembered. A webhook URL pointing at the old account. Each miss is a silent breakage you find out about from the client.

Sometimes this is the right call. A three-step reminder flow? Rebuild it. Opening the source and target side by side and retyping beats setting up any tooling for that size of job.

• Triggers, with every filter condition written down
• Branch conditions, including the “else” paths
• Wait steps and their exact durations
• Email/SMS templates; copy those separately if needed
• Webhook URLs (these are per-account; never assume)
• Custom values, custom fields, tags and pipelines the workflow references
• Exit criteria and notification settings

Realistic time cost: 10 minutes for a tiny flow, 45 to 90 minutes for something with branches and waits, then testing on top. Every step you retype from memory is a chance to get it subtly wrong.

Agency plans can package an entire sub-account as a Snapshot and import it into another sub-account. Workflows come along, with funnels, pipelines, calendars, custom fields and everything else.

For copying one workflow, that’s the wrong shape. A Snapshot is all-or-nothing: you can’t select just the workflow, importing into a live account creates duplicates of assets that already exist, and you need agency-level access to do it at all. It’s also heavy. Deploying an entire account template to add one automation means cleaning up after it.

If you actually want the whole setup cloned into a fresh sub-account, a Snapshot is the right tool. We compare the two jobs properly in Snapshots vs real backups. For a single workflow into an account that already lives and breathes, read on.

GHL Workflow Backup & Audit is a free Chrome extension that reads the workflow you have open in the builder and writes its complete step-tree to your computer as structured JSON. Honest note first: there is no native one-click import into GoHighLevel via the public API today, so this doesn’t teleport the workflow. What it gives you is an exact build specification. Every trigger, branch, filter and setting is spelled out in plain names, so nothing gets guessed during the rebuild.

1. Install the extension from the Chrome Web Store. No account needed.
2. Open the source workflow in the builder.
3. Click the extension icon. The JSON lands in your Downloads folder (or optionally straight to your own Google Drive).
4. In the target sub-account, create a blank workflow. Open the JSON beside it and reproduce each node: same trigger filters, same branch conditions, same settings.
5. Publish and test the triggers before calling it done.

Because IDs are resolved to real names, you can see “Contact Tag = Appointment Booked” rather than a hex string. Wait durations, webhook payloads, notification toggles: it’s all in the file. The rebuild becomes transcription instead of archaeology, and you can tick off nodes one by one.

One more thing to check while rebuilding: the target account may not have the custom fields, pipelines or tags the workflow references. Create those first so you’re not wiring triggers to nothing. Free tier covers 5 single exports and 1 bulk export; after that it’s $14.99 once.

If the migration is really “give the new sub-account our whole automation library”, exporting one workflow at a time gets old fast. The same extension has a bulk mode: point it at a folder in the workflows list and it exports everything inside recursively in one run, subfolders included. You end up with one dated JSON file per workflow, which doubles as a record of what the source account looked like on migration day.

For a deeper look at how exports work generally, here are the three export methods compared.