Feature deep-dive
Snapshots
Snapshots are the reason an agency can onboard its tenth chiropractor in an afternoon instead of a fortnight. They clone a fully configured sub-account — workflows, funnels, pipelines, calendars, custom fields, AI agents — into a new one. Agencies who never learn them conclude GoHighLevel is slow. It is not slow; they are rebuilding the same thing from scratch every time.
What a snapshot actually is
Think of it as a template of an entire business's software setup. You configure one sub-account until it is exactly right — the intake survey, the speed-to-lead workflow, the no-show recovery sequence, the pipeline stages, the review-request automation, the booking calendar, the funnel, the AI agent's knowledge base. Then you freeze it. That frozen configuration is a snapshot, and you can push it into any new sub-account.
What comes across
HighLevel's own documentation lists the categories a snapshot carries: workflows and triggers, AI agents and brand voice, calendars, services and resources, custom fields, pipelines, tags and custom objects, funnels, forms and surveys, blogs, email templates and campaigns, dashboards and custom reports, knowledge bases and contracts, memberships, webinars, WhatsApp templates, and ad campaign configuration for Google, Meta and LinkedIn. Images used on funnel pages travel with them.
What deliberately does not
Contacts. Appointments. Conversations and message history. Reputation data. Third-party integrations and Stripe connections. Phone numbers and A2P 10DLC registration. Billing and user accounts. Domain settings. Private dashboards.
This is not a limitation — it is the correct design. A snapshot moves structure, not data. You do not want your chiropractor client receiving another chiropractor's patient list, and you certainly do not want their Stripe key. But it does mean the phrase "deploy a snapshot and you're done" is false, and anyone selling snapshots on that promise is misleading you.
How to install a snapshot
- From a shared link: log into your agency account, open the snapshot link, choose or create the destination sub-account, confirm, and let it load.
- From your own library: Agency View → Account Snapshots → select the snapshot → push it to the target sub-account.
- Then do the part the snapshot cannot: connect the client's domain; connect their Stripe; buy a phone number and complete A2P 10DLC registration; connect Google Business Profile and Meta; swap every placeholder logo, photo, phone number, address and business name; and re-point every calendar at a real team member.
- Then audit: open every workflow that came with it, and either understand it or delete it. Publish nothing you cannot explain to the client.
Realistic timings: loading takes minutes. Making it genuinely client-ready takes a half day the first time and an hour or two once you have a checklist. That is still an order of magnitude faster than building from empty.
Who it is for
Agencies with more than one client in the same vertical — which is to say, almost every successful GoHighLevel agency. Niching down is the standard advice in this ecosystem, and snapshots are the mechanical reason it pays: your fifth med-spa client costs you a fraction of the labour of your first, at the same retainer.
Snapshots vs rebuilding by hand
| Feature | Deploy a snapshot | Build from scratch |
|---|---|---|
| Time to onboard a new client | Minutes to load, hours to customise | Days to weeks of rebuilding |
| Consistency across clients | Identical by construction | Drifts immediately |
| Fixing a bug in every client build | Still manual per account | Manual per account |
| Carries contacts / history | Not included | N/A |
| Carries Stripe / integrations | Not included | You connect them anyway |
| Carries phone numbers / A2P | Not included | You register per client anyway |
| Sellable as a product | Yes — a real market exists | Not included |
Note row three: snapshots are a one-way clone, not a live template. Fixing a workflow in your master build does not fix it in the thirty clients you already deployed it to.
Where snapshots fall short
- They are a copy, not a link. This is the big one. Once a snapshot is loaded into a client account, it is theirs — it does not stay in sync with your master. Improve your master workflow and your existing thirty clients keep the old version. There is an update mechanism for pushing changes, but it is not a reliable "propagate everywhere" button and it can conflict with client-specific edits. At scale, drift is the defining operational problem of a snapshot-based agency.
- Loading can be messy. Duplicate assets, awkward naming, and orphaned items are common, particularly if you push a snapshot into an account that already had content. Deploy into a clean sub-account whenever you can.
- Bought snapshots are frequently bad. The market is full of bloated packs full of 2021-era funnels and dozens of overlapping workflows. Inheriting fifty automations you did not write and cannot debug is worse than starting empty — and when one of them texts a client's customer at 3am, it is your name on the retainer.
- They hide the learning. Agencies that deploy a purchased snapshot before ever building a workflow themselves cannot fix it when it breaks, cannot customise it when the client asks, and cannot explain it when challenged. Build your first one yourself, even if it is slower.
- The post-install checklist is where the failures are. An unconnected Stripe, an unregistered A2P campaign, a calendar pointed at a departed employee, a placeholder logo left on a live funnel. The snapshot is not the deliverable; the audited, connected, customised account is.
The honest summary
Snapshots are what turn GoHighLevel from a CRM into a business model, and they are the single feature most responsible for the platform's agency economics. Build your own, audit anything you did not write, keep a written post-install checklist, and accept that drift across deployed clients is a management problem you will have to solve with process rather than with software. Pair them with white label and SaaS Mode and you have the full agency stack.
Keep reading
Related features
-
All GoHighLevel features
The full feature hub — every module, honestly scored.
-
White label
Serve the whole platform on your own domain and logo, plus an optional branded mobile app in the App Store under your agency name.
-
Workflows & automations
The visual automation engine: triggers, conditions, waits, branches, and 60+ actions across SMS, email, calls, pipelines, and webhooks.
-
Pricing & usage costs
Snapshots need multiple sub-accounts. Here is which plan gets you those.
Frequently asked questions
- What is a GoHighLevel snapshot?
- A snapshot is a saved template of a configured sub-account. It captures the setup — workflows, funnels, forms, calendars, pipelines, custom fields, tags, email templates, AI agents, dashboards, memberships — and lets you deploy that whole configuration into a new sub-account in minutes. It is how an agency builds a client onboarding once and then ships it to every subsequent client in that vertical.
- What does a snapshot include?
- Per HighLevel's documentation, snapshots carry configuration and reusable assets: workflows and triggers, AI agents and brand voice, calendars and services, custom fields, pipelines, tags and custom objects, funnels, forms, blogs, email templates and campaigns, dashboards and custom reports, knowledge bases and contracts, memberships, webinars, WhatsApp templates, and ad-campaign configurations for Google, Meta and LinkedIn.
- What does a snapshot NOT include?
- Not the data. Contacts, appointments, conversations, message history, reputation data and live account activity do not transfer. Neither do third-party integrations and Stripe connections, phone numbers, A2P 10DLC registration, billing, user accounts, domain settings, or private dashboards. Snapshots move structure, never customer records or credentials — which is exactly what you want when you are cloning a build to a different client.
- How do I install a GoHighLevel snapshot?
- Two paths. If someone shared a snapshot link with you, open the link while logged into your agency account, choose the destination sub-account (or create a new one), and confirm — GoHighLevel loads the assets in. If it is your own snapshot, go to Agency View → Account Snapshots, select the snapshot, and push it to the target sub-account. After loading, you still have to do the client-specific work: connect the domain, connect Stripe, buy and register a phone number, and swap placeholder branding.
- Which plan do I need for snapshots?
- Snapshots are an agency feature and they matter from the $297 Unlimited plan upward, where unlimited sub-accounts make cloning worthwhile. On the $97 Starter, with three sub-accounts, the mechanic exists but the economics do not — snapshots pay off precisely because you deploy them repeatedly.
- Are paid GoHighLevel snapshots worth buying?
- Sometimes, as a starting point — never as a finished product. A good vertical snapshot saves you weeks of building. A bad one buries you in fifty overlapping workflows you did not write and cannot debug, which is a worse position than an empty account. Audit before you deploy: open every workflow, delete what you do not understand, and never hand a client a build you cannot explain.
Build one client properly, then clone it forever
Start a trial, configure a single sub-account end to end, and snapshot it. That is the agency playbook in one sentence — and it only takes one build to prove it to yourself.
Affiliate link. We earn a commission at no extra cost to you.