Snapshots are how GoHighLevel agencies onboard clients in hours instead of days. A good snapshot turns your best client setup into a template you can load into every new account. A bad one copies the same mistakes into all of them. Here's what snapshots include, what they don't, and how I build them for agencies.
What is a GoHighLevel snapshot?
A snapshot is a saved copy of a sub-account's setup, not its data. You build a system once, save it as a snapshot, then load it into new sub-accounts or share it with other agencies. It's the foundation of offering a repeatable service, or a niche product, on GoHighLevel.
What a snapshot includes
- Workflows and automations
- Funnels, websites and landing pages
- Email and SMS templates
- Pipelines and opportunity stages
- Calendars and booking settings
- Forms and surveys
- Custom fields, custom values and tags
- Membership and course structures
What a snapshot doesn't include
This is where most onboarding goes wrong. Snapshots don't carry:
- Contacts, conversations, call logs or appointment history
- Phone numbers and A2P 10DLC registration
- Payment connections such as Stripe, and third-party API keys or integrations
- Users and team members
- Reviews, reporting and analytics data
That's deliberate: every client should get a clean workspace without another client's data. But it means every one of those items needs its own onboarding step.
How I build a snapshot agencies can rely on
1. Build it from a real, working account
Don't build a snapshot in theory. Build the system for one real client (or a realistic test account), run real leads through it, fix what breaks, and only then save it.
2. Use custom values for everything client-specific
Business name, phone number, address, booking links, review link and owner name should all be custom values, never typed into workflows and templates. Then a new client means filling in one settings page instead of editing 40 messages.
3. Name things so others can maintain them
Prefix workflows by purpose (01 Lead | Missed-call text-back, 02 Booking | Reminders), and keep tags consistent. Your team, or the next VA, should understand the system without asking you.
4. Keep triggers safe by default
Workflows that send messages should be safe the moment the snapshot loads: either published only after the client's details are in, or guarded by a tag or filter so nothing fires to the wrong people. One careless trigger can text a whole imported list.
5. Write an onboarding checklist alongside it
Because snapshots skip so much, every snapshot I build comes with a checklist:
- Load the snapshot into the new sub-account
- Fill in every custom value
- Buy or port phone numbers, and complete A2P 10DLC registration for US clients
- Connect payments, calendars, email domain and integrations
- Add users with the right permissions
- Import contacts, with consent records, and check no workflow fires on import
- Run a test lead through every main workflow, then publish
Updating clients who already use a snapshot
HighLevel lets you push snapshot updates to sub-accounts that already use it. Be selective: push only the assets you actually changed, because an update can overwrite changes a client has made in their own account. For big changes, I'd rather version the snapshot (v1, v2) and roll it out client by client.
Niche snapshots
The strongest snapshots are built for one industry, with the right pipeline stages, messages and automations for that business. My 13 case studies are effectively niche systems: speed-to-lead for HVAC, recall for dental clinics, renewal tracking for insurance agencies, and so on.
Need snapshots built or fixed?
I build and maintain snapshots for agencies, working white-label behind your brand, including the custom code for anything GoHighLevel can't do natively. See GoHighLevel for agencies and pricing, or read the 10 automations I put into most service-business snapshots.