GoHighLevel Snapshots: What They Copy and How to Build One
What a GoHighLevel snapshot is, what it copies and what it leaves behind, how to create, load and refresh one, and what a snapshot built and tested for an agency costs.
By Talha Abid8 min read
A GoHighLevel snapshot is a saved copy of a sub-account’s setup that you can load into another sub-account in minutes. For an agency it is the difference between onboarding a client in an afternoon and rebuilding the same pipelines, calendars and workflows by hand every time. For a single business it is the thing a developer hands over so the setup can be reproduced if the account is ever rebuilt.
Snapshots are also where most agency accounts go wrong, because a snapshot copies structure and nothing else. Contacts, phone numbers, integrations and payment connections stay behind, and a snapshot that was never tested spreads its faults to every account it touches. This guide covers what HighLevel’s help center says a snapshot includes, checked against its snapshots overview on 3 November 2026, and the way I build them for agencies.
Key takeaways
- A snapshot copies configuration: pipelines, custom fields, custom values, tags, calendars, forms, funnels and websites, workflows, email templates, campaigns, dashboards and more. It does not copy contacts, conversations, appointments, Stripe or other integrations, reputation data or assigned phone numbers.
- Snapshots are created from a working sub-account in Agency View under Account Snapshots. You cannot write one from scratch; you build the account first, then save it.
- A new sub-account can be created from a snapshot during setup, and an existing sub-account can load one with a review of conflicts. Snapshots do not update by themselves; you refresh them from the source account.
- A bought snapshot saves you the layout and costs you the testing. Every workflow still has to be run with a fake lead before a paying client meets it.
- Each snapshot needs a per-client checklist for the steps it cannot carry: phone number, A2P registration, email sending domain, domain, users, calendar connections and payments.
What a snapshot is
HighLevel describes snapshots as "reusable templates that capture selected configuration assets from a HighLevel sub-account", in the overview article last updated on 9 October 2026. The key word is configuration. Everything that defines how the account behaves can be captured; everything that happened inside the account, and everything tied to a specific business or a specific connection, cannot.
That split is deliberate. A snapshot is meant to be loaded into accounts belonging to different businesses, so it carries the shape of the system and leaves the identity of the business to be filled in. The agency accounts that run smoothly treat it that way: the snapshot is the product, and a short checklist turns the product into a live account for one client.
What a snapshot copies, and what it leaves behind
The overview lists the asset categories you can select when creating a snapshot. On the copied side: pipelines, tags, custom fields including company fields, custom objects and custom values; calendars with their groups, service categories and add-ons; forms, surveys, quizzes, funnels and websites, blogs, email builder templates and campaigns; workflows, triggers, Conversation AI, Voice AI agents, Agent Studio agents and brand voice; dashboards, custom metrics and custom reports; documents and contracts, folders and knowledge bases; ad campaigns for Google, Meta and LinkedIn; and a WordPress site.
On the other side, the article lists what does not transfer, and the list is worth reading twice before you promise a client a two-hour onboarding:
| Not copied by a snapshot | What it means for a new account |
|---|---|
| Contacts, appointments, conversations and messages | The new account starts empty; import contacts separately |
| Reputation data and live account activity | Reviews and activity belong to the original business |
| Stripe connections | Payments must be reconnected in the new account |
| Integrations and third-party account connections | Google, Facebook, Zoom, QuickBooks and the rest are reconnected per account |
| Assigned phone numbers for Voice AI agents | A number is bought or ported for each client and reassigned |
| Lead Gen Forms for LinkedIn ad campaigns | Rebuilt in the client’s own ad account |
| Private dashboards and contact-to-contact associations | Shared dashboards copy; private ones and relationships do not |
Two practical consequences follow. Funnels and websites arrive without a domain, so they need the client’s domain connected and the pages published before anything is live. And any workflow that sends from a phone number or an email address is pointing at nothing until the per-client setup is done, which is why a snapshot load is the start of onboarding rather than the end.
How to create a snapshot
Snapshots are made from a sub-account that already works. The overview puts the path in Agency View under Account Snapshots, where "+ Create New Snapshot" lets you pick the source sub-account and the asset categories to include, either everything or a selection. The quality of the snapshot is therefore the quality of the source account, and the source account should be a master built for the purpose rather than a live client whose years of tests, duplicate workflows and unused tags come along for the ride.
My master accounts follow three rules. Every business detail lives in a custom value, so the business name, phone number, booking link and review link change in one place after a load. Every workflow is named for what it does and documented in one list. And the account is run with fake leads through every path, the web form, the missed call, the booked appointment, the no-show, until each workflow fires once and only once. Only then is it saved.
How to load a snapshot
There are two routes. When you create a new sub-account, you can choose a snapshot during setup and it is applied as the account is made. For an account that already exists, you load the snapshot from Agency View, choose which assets to import, and review the conflicts where an asset with the same name exists already, deciding whether to override or skip each one. That review is how you add a second snapshot to an account, or push a new workflow into a client account without touching what is already there.
After the load comes the checklist, which no snapshot can carry: buy or port the phone number and file the A2P 10DLC registration; set up the email sending domain; connect the client’s domain and publish the funnels or site; add the users and connect their calendars; reconnect Stripe and any integrations; replace the custom values with the client’s details; and send one test lead through every path again, because a workflow that worked in the master can still point at a calendar that does not exist in the new account.
Keeping snapshots current
Snapshots are static. The overview is explicit: "You must refresh the Snapshot to capture new or changed assets from the source sub-account." Refreshing "updates the Snapshot with selected changes from the source sub-account", which means improvements go into the master first and are then captured, not edited inside the snapshot. When a client account should receive the improvement, the refreshed snapshot is loaded into it with the conflict review set to override the changed assets and skip everything else.
That rhythm, master, refresh, selective load, is how an agency improves twenty accounts in an afternoon. Without it, each client account drifts into its own version and the next hire inherits twenty different systems.
Buying a snapshot versus building one
Snapshots for most niches are sold online, often for under a hundred dollars, and HighLevel’s own marketplace and templates give you starting points for free. A bought snapshot is worth having for its layout: the pipeline stages, the page structure and the list of workflows someone thought a dental practice or a roofing company needs. What it does not come with is proof that any of it fires correctly in your account, in your time zone, with your phone setup, and the generic copy will still need writing for your clients.
HighLevel also offers assets-protected snapshots, which it previously called IP protected, so an agency selling its own snapshot can share it without exposing how the workflows are built. If you are selling snapshots, that is the format to use; if you are buying one, expect that you cannot see inside it before it is loaded.
What it costs to have a snapshot built
A snapshot built for a niche, tested with fake leads and documented with its per-client checklist takes me two to three weeks, and I quote it after a 30-minute call because the scope depends on how many funnels, calendars and automations the niche needs. Loading it into a client account and doing the per-client steps is the GoHighLevel sub-account setup on my pricing page, at $497 per account. Agencies that want the snapshot, the SaaS plans and the white-label domains together should start with the white-label GoHighLevel page.
Frequently asked questions
Do GoHighLevel snapshots copy contacts?
No. HighLevel’s overview lists contacts, appointments, conversations and messages among the items that do not transfer. Contacts are imported into the new account from a CSV, with their tags, after the snapshot is loaded.
Can I load more than one snapshot into a sub-account?
Yes. A new sub-account takes one snapshot during setup, and further snapshots are loaded into the existing account afterwards, with a review of conflicts where an asset of the same name already exists. Override replaces it; skip keeps the version in the account.
Will my funnels and websites work straight after a load?
They copy, but the domain does not. Each funnel and website needs the client’s domain connected and the pages published in the new account before they are live. Custom code inside the pages copies with them.
How do I update twenty client accounts with one change?
Make the change in the master sub-account, refresh the snapshot so it captures the changed asset, and load the refreshed snapshot into each client account with override selected for that asset and skip for everything else.
Can I sell a snapshot I built?
Yes. HighLevel’s assets-protected snapshots let you share a snapshot without exposing the contents of its workflows and pages, which is the format most paid snapshots use. The buyer still has to do the per-client setup and the testing in their own account.