GoHighLevel snapshot vs template: what the difference actually means for your agency
Snapshots, templates and cloned sub-accounts solve different problems in GoHighLevel. Here is what each one carries, what it leaves behind, and when to use which.
The words get used interchangeably in most GoHighLevel conversations, and the confusion causes real problems — usually at the moment someone expects a snapshot to carry something it never could.
A snapshot is an account blueprint
A snapshot captures the structure of a sub-account: workflows, pipelines, calendars, forms, surveys, custom values, custom fields, triggers, templates and funnels. You take it from one sub-account and load it into another.
What it deliberately does not carry: contacts, conversation history, opportunities with their data, connected third-party authentication, phone numbers, and most account-level settings. A snapshot is the shape of an account, not its contents.
That distinction is the source of nearly every surprise. “The snapshot didn’t bring the conversations across” is not a bug.
A template is one asset
Email templates, SMS templates, funnel templates, form templates. Single reusable pieces, not account structure. A template is something you drop into an account that already exists.
Templates are useful and narrow. If someone offers you a “template” that includes pipelines and workflows, they mean a snapshot.
Cloning is neither
Duplicating a sub-account inside the same agency copies more than a snapshot would, but it also copies things you rarely want — including, in most setups, the exact configuration mistakes you were hoping to leave behind. Cloning is convenient for a one-off and terrible as a strategy, because it produces N slightly different accounts with no source of truth.
The tell: if the answer to “which account has the good version?” is a name rather than “the master”, your agency clones.
When to use which
Snapshot — you build the same kind of account repeatedly and want a source of truth. This is the right answer for almost every agency past its third client. A custom snapshot build turns your repeatable build into exactly this.
Template — you want one good email sequence or one funnel inside an account that is otherwise fine.
Clone — you need a copy of one specific account, once, and you accept that it will drift.
The thing nobody tells you about snapshots
Snapshots are point-in-time. The moment you improve a workflow in a client account, that improvement exists in one account only. Unless you have a master sub-account that snapshots are taken from, and a habit of making improvements there first, your snapshot goes stale within a quarter.
The version discipline matters more than the snapshot. That is why every kit we ship carries a version and a changelog, and why the first thing we set up in a custom build is a master account nobody uses for client work.
Practical rule
Build in the master. Snapshot from the master. Load into clients. Never improve a client account first and hope you remember to backport it, because you will not.
Where each one leaves you
A snapshot gets you structure in a fresh account and nothing else — no numbers, no credentials, no contacts. A transfer moves the whole live account, history included, with its own set of exclusions. A clone gets you a copy of your own work inside your own agency.
Pick by what you need to survive the move:
- Need the client’s data and conversation history to come too? That is a sub-account transfer, not a snapshot.
- Need the same build in a fresh account for a new client? Snapshot, loaded into an empty sub-account — see the loading method.
- Not sure what a sub-account even contains? Start with what a GoHighLevel sub-account actually is.
This note is one stage ofthe complete guide to GoHighLevel sub-accounts — seven stages from a signed client to a live account.