What a snapshot actually is
A GoHighLevel snapshot is a saved template of an account's configuration that you can deploy into another sub-account. Instead of rebuilding pipelines, workflows, and funnels by hand for every client, you build them once, save a snapshot, and load it into each new account — turning weeks of setup into minutes.
Snapshots typically include pipelines, workflows and automations, funnels and websites, calendars, email/SMS templates, custom fields, and trigger links — the structural scaffolding of an account.
What snapshots don't carry over
Snapshots copy structure, not data. Contacts, conversation history, and existing account data don't transfer — which is by design; you're deploying a system, not someone else's records. Some integrations and credentials also need to be reconnected per account after loading a snapshot.
How to set one up well
Build the account you want to replicate first — get the pipelines, workflows, and funnels genuinely working. Then create the snapshot from that account, name and document it clearly, and test it by loading it into a fresh sub-account before you rely on it for a client. The quality of your snapshot is the quality of every account you deploy from it, so it's worth getting the source account right.