What is a GoHighLevel snapshot?
A GoHighLevel snapshot is a saved template of a sub-account’s configuration, including its workflows, pipelines, calendars, forms, funnels and email templates, that an agency can load into a new sub-account in minutes instead of rebuilding it by hand.
What is a snapshot in plain terms?
A snapshot is a copy of how a sub-account is built, without the customer data inside it. It captures the structure: which workflows exist and what they do, which pipeline stages exist, which calendars and forms exist, and which templates the messages use. Loading a snapshot into an empty sub-account reproduces that structure.
Snapshots are made at the agency level. An agency builds one sub-account properly for, say, a dental clinic, tests it for a month, then saves it as a snapshot. Every new dental client starts from that snapshot and gets a tested system on day one. The build time drops from two to four weeks to a few days of adjustment.
A snapshot is not a backup of a client’s data. Contacts, conversations, appointments and payment history are not included. It is closer to a blueprint than to a copy of a house.
What does a snapshot include and what does it leave out?
The table separates what is copied from what has to be set up again in every new sub-account.
| Item | Copied by the snapshot? | What to do in the new account |
|---|---|---|
| Workflows and their triggers | Yes | Review the time-zone window and the phone number used for sending |
| Pipelines and stages | Yes | Rename stages to the client’s wording if needed |
| Calendars | Yes, the calendar settings | Connect the client’s Google or Outlook calendar and set staff availability |
| Forms and surveys | Yes | Update the consent wording to the client’s legal name |
| Funnels and websites | Yes | Replace logo, colours, domain and copy |
| Email and SMS templates | Yes | Replace business name, address and signature merge fields |
| Custom fields and tags | Yes | None, unless the client needs extra fields |
| AI agent instructions | Partly, depending on version | Rewrite the business description and hand-off rules |
| Contacts, conversations, appointments | No | Import the client’s contact list separately |
| Phone numbers, A2P registration, domains | No | Buy the number, register A2P 10DLC, verify the sending domain |
| Integrations (Facebook, Google, WhatsApp) | No | Connect each account with the client’s own login |
When should an agency use a snapshot?
An agency should use a snapshot whenever it takes on a second client in the same industry. The first client’s build becomes the snapshot; every later client of that type starts from it. This is how a GoHighLevel agency in the United States can onboard a new HVAC contractor in days and still deliver a system that was tested on real calls.
A snapshot is also the right tool for a franchise or a multi-location business. Each location gets its own sub-account loaded from the same snapshot, so reporting compares like with like and a fix made to the snapshot can be pushed to every location.
A snapshot is the wrong tool when the client’s process is unusual. Forcing a home-services snapshot onto a private clinic produces pipelines with the wrong stages and messages with the wrong tone. In that case we build from scratch and save a new snapshot for that industry.
Are bought or free snapshots worth using?
Bought snapshots save typing but rarely save the testing. Most snapshots sold online were built for a generic business, use placeholder wording, and include workflows that fire on triggers the client does not have. Loading one without a line-by-line review usually produces messages with the wrong name and sequences that overlap.
The review takes longer than the build for a simple industry. We treat any external snapshot as a starting draft: load it into a test sub-account, run every workflow with a test contact, delete what does not apply, and only then save our own version. The snapshot we hand to a client is always one we have run ourselves.
How do you create and load a snapshot correctly?
Six steps take a tested sub-account and turn it into a repeatable onboarding.
Finish and test the source sub-account
Every workflow has run on real contacts for at least two weeks and the execution log shows no errors.
Replace client-specific values with merge fields
Business name, address, phone and signature come from the sub-account settings, not typed into templates.
Save the snapshot at the agency level
Name it by industry and date, and write a one-page note of what has to be reconnected after loading.
Create the new sub-account and load the snapshot
Load it before adding any contacts so nothing triggers on import.
Reconnect what the snapshot cannot carry
Run the test contact through every workflow
Read every message on a phone, check every booking lands on the right calendar, then import contacts and go live.
Common questions about GoHighLevel snapshots
Does a snapshot copy my contacts?
No. Snapshots carry configuration only. Contacts, conversations, appointments and payments stay in the original sub-account and must be imported separately if they are needed in the new one.
Can I update a snapshot after clients have been loaded from it?
You can save a new version of the snapshot at any time. Loading the update into an existing sub-account adds or overwrites the items it contains, so we test updates in a sandbox sub-account before pushing them to live clients.
Which plan do I need to create snapshots?
Snapshots are an agency-level feature available on both the $297 and $497 monthly plans. The $497 Agency Pro plan adds SaaS mode and AI rebilling, which most agencies that use snapshots at scale also need.
Can a snapshot be sold or shared?
Yes, a snapshot can be shared by link to another agency account. Whether it is worth selling depends on how well it is tested and documented; most bought snapshots need a full review before use.
How long does loading a snapshot take?
Loading takes minutes. Reconnecting phone numbers, registrations, domains and integrations, then testing every workflow, takes two to five working days for a typical service business.
What is related to GoHighLevel snapshots?
- GoHighLevel workflows Workflows are related to snapshots because the workflows are the most valuable thing a snapshot copies and the first thing that needs testing after loading.
- GoHighLevel SaaS mode SaaS mode is related to snapshots because SaaS mode creates new sub-accounts automatically and loads a chosen snapshot into each one.
- GoHighLevel white-label White-label is related to snapshots because an agency reselling the platform under its own brand delivers the same tested snapshot to every client.
- What GoHighLevel is What GoHighLevel is is related to snapshots because a snapshot is a copy of how the ten parts of the platform are configured in one sub-account.
- White-label service for agencies The white-label service for agencies is related to snapshots because we build and maintain the industry snapshots that agency partners load for their clients.
- Book a strategy call A strategy call is related to snapshots because we look at whether your clients share an industry and whether a snapshot would cut your onboarding time.
Want a tested snapshot for your industry instead of a blank account?
Book a free strategy call. We show you the snapshot we run for businesses like yours, what it does on day one, and what still has to be connected for your account.
Book a Free Strategy Call