GoHighLevel snapshots, explained plainly

A snapshot is a saved copy of how one sub-account is put together, which you can load into another sub-account in a few minutes instead of rebuilding it. For an agency onboarding a new client, this is the difference between a day of setup and a coffee break, and it is the main reason the three sub-accounts on the $97 plan feel more usable than the number suggests.

The mental model that keeps you out of trouble is this: a snapshot carries the machinery, never the business. Everything you built is in it. Everything that happened is not. Once that lands, the rest of the behaviour stops being surprising.

The bottom half of that table is the useful half. People assume a snapshot is a backup and discover at the worst possible moment that it is not. If a client account is deleted, the snapshot restores the funnels and the workflows and returns exactly none of the contacts, none of the conversation history and none of the booked appointments.

The flip side is that this is precisely what makes snapshots safe to sell, share and hand to a client. There is no way to accidentally ship someone else’s contact list inside one, because the format has no room for it.

This is the question the support forum gets most, and the answer is reassuring with one caveat. The load process is additive by default. Existing contacts, conversations and appointments are untouched because, as above, snapshots have no concept of them anyway.

The caveat is assets with the same name. If the incoming snapshot contains a workflow or a funnel that clashes with one already in the account, you are asked what to do, and choosing to override is genuinely destructive to that asset. Read those prompts rather than clicking through them, especially on an account a client is actively using.

There is a whole cottage industry selling prebuilt snapshots for particular niches, dentists, roofers, gyms, and the pitch is that you skip the build entirely. That is a reasonable thing to want and a risky thing to buy, for reasons the sellers do not advertise.

A snapshot you did not build is a system you cannot fix. When a workflow misfires at two in the afternoon on a client’s busiest day, you are debugging somebody else’s logic in an interface you are still learning. The learning curve is already the most complained-about thing on this platform, and buying a snapshot postpones the climb rather than removing it.

The other issue is fit. A generic niche snapshot arrives with dozens of assets you did not ask for, and pruning is slower than building. If you do buy, treat it as a reference to read rather than a system to run, and rebuild the three workflows you actually need in your own account where you understand every step.

We are not naming or ranking snapshot sellers, and we will not until there is a way to verify what is inside one before purchase. Recommending a package we cannot inspect would be exactly the kind of thing this site exists to avoid, and our method page explains where that line sits.

Snapshots do not track their source. Improve a workflow in the account you built the snapshot from, and every account you already loaded it into keeps the old version forever unless you act.

The route back is to refresh the snapshot from the source account manually, then push the refreshed version to the sub-accounts linked to it. That works, but it is a deliberate action on your calendar rather than something the platform does for you, and an agency running twenty client accounts should treat snapshot maintenance as a recurring job rather than a one-off. This is one of the practical arguments for the $297 Unlimited plan: once you are past a handful of accounts, the template discipline matters more than the seat count.