GoHighLevel snapshots are saved copies of a sub-account's setup, such as workflows, pipelines, funnels, websites, forms, calendars, custom fields and custom values, that you can load into other sub-accounts. Agencies use them to launch every new client with the same tested build. A good snapshot is built in a clean master sub-account, uses custom values instead of hard-coded details, and is documented so whoever loads it knows exactly what to customize.
I build snapshots for agencies as part of GHL work. This guide covers what they include, how to build one well, how to load and update it, and what to look for in snapshots you buy.
What GoHighLevel snapshots include
A snapshot captures the configuration of a sub-account. Typically that includes:
- Workflows and campaigns
- Pipelines and stages
- Funnels and websites
- Forms and surveys
- Calendars
- Custom fields and custom values
- Tags
- Email and SMS templates
- Trigger links
What a snapshot generally does not carry over is the client-specific, connected or personal data: contacts and conversations, connected integrations such as the client's Facebook page or Google account, phone numbers, and payment connections. HighLevel's help docs list exactly what is and is not included, and the list changes as features are added, so check it before promising a client anything.
Why agencies use snapshots
- Speed: a new sub-account gets a full, tested build in minutes.
- Consistency: every client runs the same workflows, so support and fixes are easier.
- Productization: a niche snapshot, such as one for home services, becomes a repeatable offer.
- Updates: improvements can be pushed to sub-accounts that use the snapshot.
This is also the foundation of GoHighLevel SaaS mode, where snapshots are often loaded automatically for new signups.
How to build a GoHighLevel snapshot
Step 1: Create a master sub-account
Build in a dedicated sub-account used only for the snapshot. Never build in a live client account, because client data, names and integrations leak into the snapshot.
Step 2: Standardize the foundations
Before building workflows, set:
- Pipelines and stages that match how your clients sell
- Tags with a documented naming pattern
- Custom fields for the data your workflows need
- Custom values for business name, phone, address, review link, booking link and owner name
Custom values are the key. Every message and page should pull from them so the same build works for every client.
Step 3: Build and test the workflows
Build your core workflows: speed to lead, missed call text back, appointment reminders, no-show recovery, review requests and nurture. My starting set is in GoHighLevel workflow templates. Test each one end to end with a test contact.
Step 4: Build calendars, forms and funnels
Add the calendars, forms and funnel or website pages the workflows depend on. Link forms to the right workflows and calendars to the right reminders.
Step 5: Clean up
- Remove test contacts and test data
- Delete old workflow versions
- Check that nothing refers to a real client's name, number or email
- Confirm every message uses custom values
Step 6: Save the snapshot
From the agency view, create a snapshot from the master sub-account and give it a clear name with a version, such as "Home Services Core v4".
Step 7: Document it
Write a short setup SOP: which custom values to fill, which integrations to connect, which workflows to publish, and how to test. This document is what stops a snapshot from being loaded half-configured.
Loading a snapshot into a sub-account
You can load a snapshot when creating a new sub-account, or import it into an existing one. When importing into an existing account, you usually choose which assets to bring in and how to handle conflicts with assets that already exist. Read the import options carefully, because overwriting a live workflow can change what clients' customers receive.
After loading, do the client setup:
- Fill in custom values
- Connect the phone number, email sending domain, calendars and social or ad accounts
- Set users and permissions
- Publish the workflows you want active
- Run end-to-end tests
The full checklist is in GoHighLevel sub-account setup.
Updating snapshots
When you improve the master build, update the snapshot and push the changes to sub-accounts that use it. HighLevel supports pushing snapshot updates, with options for which assets to update.
Rules I follow:
- Version every change and keep a short changelog
- Test the update in one sub-account before pushing widely
- Avoid overwriting customized assets unless you mean to, since clients may have edited their own copies
- Tell account managers what changed and why
GoHighLevel snapshot templates: build or buy?
There is a big market of snapshot templates for niches like roofing, dental, med spas and coaches.
Buying can make sense when
- You are new to GHL and want to see how a complete build fits together
- The niche is far from your expertise
- You are prepared to rebuild parts of it
Building makes sense when
- You have a defined niche and offer
- You want workflows that match how you actually sell and deliver
- You need to support and update the build for years
How to judge the best GoHighLevel snapshots
Whether you buy or build, check:
- Custom values everywhere. No hard-coded business names or links.
- Clean naming. Workflows, tags and fields follow a clear pattern.
- Few, focused workflows. Dozens of overlapping workflows are hard to support.
- Stop conditions. Nurture sequences stop on reply, booking or opt-out.
- Compliance basics. SMS respects consent and opt-out, and you know what A2P registration the client needs.
- Documentation. A setup guide and a changelog exist.
- No mystery integrations. Webhooks pointing to unknown external URLs should be removed or replaced with yours.
That last point matters. A bought snapshot that sends contact data to someone else's webhook is a real risk. Check every webhook action before publishing.
Keeping one snapshot or several
Agencies often ask whether to keep one master snapshot or many. My rule of thumb:
- One core snapshot with the workflows every client gets: speed to lead, missed call text back, reminders, no-show recovery and review requests.
- Small add-on snapshots for optional modules, such as reactivation campaigns or a specific funnel, imported only where the client buys them.
- A separate niche snapshot only when the pipelines, fields and messaging are genuinely different, such as home services versus medical practices.
Fewer snapshots means fewer versions to maintain and fewer places for bugs to hide. When you do keep several, use the same naming pattern for workflows, tags and fields across all of them so your team can support any client without relearning the build.
Snapshots and agency operations
Snapshots handle the client-facing build inside GHL. They do not handle your agency's internal side, like creating the client in ClickUp, a Slack channel or the reporting tracker. I connect those with a won-deal or new sub-account event sent to Make, which then runs the internal onboarding. On one agency build, that internal setup went from about 40 manual steps to one form submission.
How I build this
I build and audit GHL snapshots for agencies, and connect new sub-accounts to the internal onboarding in Make through the Agency Onboarding Engine. If you have a snapshot that is causing problems across clients, Automation Rescue can untangle it. Or start with a free teardown.
FAQ
What is a GoHighLevel snapshot?
A snapshot is a saved copy of a sub-account's configuration, such as workflows, pipelines, funnels, forms, calendars and custom fields, that can be loaded into other sub-accounts.
How do I create a snapshot in GoHighLevel?
Build and test everything in a clean master sub-account, then create a snapshot from it in the agency view. Name it with a version and document what to customize after loading.
Do GoHighLevel snapshots include contacts?
Generally no. Snapshots carry configuration, not client data like contacts and conversations, and connected integrations usually need to be reconnected. Check HighLevel's help docs for the current list.
Can I update a snapshot after clients are using it?
Yes. You can update the snapshot and push changes to sub-accounts that use it, choosing which assets to update. Test in one account first.