Snapshots and per-workflow export solve two different problems — one stands up a whole account, the other exports individual automations into accounts that are already live. A snapshot is whole-account and all-or-nothing: it drops contacts, third-party integrations, phone numbers and A2P registration, and can silently leave workflows behind. Here is how to tell which one a job needs.
If you run a GoHighLevel agency, you have almost certainly reached for a snapshot at some point — and then hit the wall where a snapshot is the wrong tool for the job. The confusion is understandable: both snapshots and a workflow export can "copy automations from one account to another," but they work at completely different scales. Picking the wrong one is how agencies end up with duplicated pipelines, overwritten settings, or an afternoon lost to rebuilding a single automation by hand. This guide draws the line clearly.
A snapshot is a whole-account template. When you save one, GoHighLevel bundles up an entire sub-account's configuration — its workflows, pipelines, custom fields, calendars, funnels, triggers and more — into a single package. Load that package into a new sub-account and you get the whole setup at once.
That makes snapshots excellent at one specific thing: spinning up a fresh account from a known-good baseline. If you onboard clients onto a standard "agency starter" build, a snapshot drops the complete system into each new, empty sub-account in one click. Nothing is quicker when the destination is blank and you want everything.
The trouble starts the moment the destination account is already live. Because a snapshot is all-or-nothing, it carries far more than the one automation you actually wanted to move. Applying it to an account that already has its own pipelines, tags and settings can duplicate assets or clobber configuration the client is relying on. There is no "just this workflow, please" option.
A snapshot is also a poor fit when you only need to move one or a few workflows between existing accounts. You cannot cherry-pick a single workflow out of a snapshot — the template moves as a whole. And because the snapshot references assets by their internal ids, moving pieces around by hand after the fact means those ids do not line up in the destination, leaving steps pointing at pipelines, stages or custom fields that do not exist there.
A snapshot also never carries everything. It templates configuration, not data or connections, so contacts, conversations, third-party integrations, phone numbers and A2P registration do not come across — and in practice snapshots can silently drop workflows too, leaving a destination that looks complete but is quietly missing automations you assumed had moved. You often only find out when something that should have fired never does.
A per-workflow export flips the model around. Instead of a whole-account template, ExportGHL Workflows works at the level of the individual automation. You save a single workflow to a cloud library on demand, then deploy it into another sub-account whenever you need it. It is surgical where a snapshot is sweeping.
Two things make this safe for live accounts. First, every deploy lands as a new workflow in the destination — it never overwrites what is already there unless you explicitly choose to update an existing one. Second, it handles the id problem for you. With cross-account remap, the exporter rewrites the references that only exist in the source account — pipelines, stages, tags, users, custom fields and calendars — matching each one by name in the destination. Anything it cannot confidently match is left for you to resolve, and the workflow is deployed as a draft rather than published broken. (GoHighLevel's own duplicate copies a workflow only within one sub-account; its Copy Workflow to Sub-Account does reach another sub-account, but only inside your own agency, only for admins, and it lands as a draft with most references cleared.)
Short answer: if the destination is a brand-new, empty account and you want the whole build, use a snapshot. If you are exporting one or a few automations into an account that is already live, export the individual workflows instead — a snapshot is too total and risks the silent drops above. The export GoHighLevel workflows hub covers the per-workflow path end to end.
In practice, agencies use both. A snapshot sets up each new client; from then on, as you refine a nurture sequence or build a new booking flow in one account, you copy that workflow between accounts one at a time rather than re-snapshotting everything. For a full account move — front-end pages plus every automation — see the complete migration guide.
Snapshots are part of GoHighLevel itself, so there is nothing extra to buy to use them. ExportGHL Workflows runs on a free trial, pay-as-you-go credits that never expire, or a one-time Toolkit licence — no subscription. You can move your first workflow free without a card, which is usually enough to see whether per-workflow export fits your process before you commit to anything.
Move your first workflow free — no card, no subscription. Remap handles the ids for you.
Start free
ExportGHL