GoHighLevel Snapshots: What They Are and How to Use Them
Snapshots are one of the most underused features we see in agency GoHighLevel accounts, and also one of the most valuable once agencies actually understand what they do. We use snapshots on nearly every client build because they turn a multi-day setup process into a matter of minutes.
Where Snapshots Fit Into a Broader Agency Workflow
Snapshots don't exist in isolation. They typically sit alongside your sales process (a client signs), your onboarding process (the snapshot deploys), and your ongoing management process (the client's account gets supported and refined over time). Understanding that full lifecycle helps clarify exactly what a snapshot should and shouldn't try to solve on its own, it's the fast middle step, not a replacement for either the sales conversation before it or the ongoing relationship after it.
What a GoHighLevel Snapshot Is
In plain English, a snapshot is a saved copy of a complete GHL setup, workflows, funnels, pipelines, calendars, and more, that you can deploy to any sub-account in one click. Instead of manually rebuilding the same automations and pipelines for every new client, you build it once, save it as a snapshot, and deploy that exact configuration instantly whenever you need it again.
Why Snapshots Matter for Agencies
Without snapshots, onboarding a new client means rebuilding pipelines, workflows, and calendar logic from scratch every single time, which is exactly the kind of repetitive work that eats an agency's margin. With a good snapshot library, onboarding a new client in a niche you've served before takes minutes instead of days, and it comes with the reliability of a system you've already tested on real clients.
We think of snapshots as the difference between an agency that scales and one that stays capped by its own founder's time. Without them, every new client adds roughly the same amount of manual setup work as the last one. With a solid snapshot library, that marginal setup cost drops dramatically, which is exactly what lets a small team serve a much larger client base without burning out.
What Is Included in a Snapshot
Snapshots capture workflows, automations, pipelines and pipeline stages, funnels and websites, calendars, custom fields, and tags. What typically doesn't transfer is contact data itself, along with certain account-level integrations that need to be reconnected per sub-account, like payment processors and phone numbers.
It helps to think about a snapshot as capturing the "shape" of an account rather than a full clone of it. The structure, logic, and design all transfer cleanly. Anything tied specifically to one client's identity, their actual customer records, their specific phone number, their unique payment processor login, has to be configured fresh for each new deployment, which is by design rather than a limitation.
We've found it useful to keep a simple checklist of exactly what a given snapshot includes and what it doesn't, since assumptions here are one of the most common sources of confusion for teams new to using snapshots at scale.
How to Create a Snapshot Step by Step
- Build out a complete, tested setup in one sub-account first
- Go to the Snapshots section in your agency settings
- Select the sub-account you want to capture and choose what to include
- Name it clearly, ideally by niche or use case, so it's easy to find later
- Save and review it by deploying to a test sub-account before relying on it for real clients
Snapshots vs Building From Scratch: A Real Comparison
Building a full client account from scratch, pipeline, workflows, calendar, and funnel, commonly takes an experienced builder a full day or more of focused work per client, longer for a first-time builder still learning the platform. Deploying a well-built snapshot to a new sub-account takes minutes, with maybe an hour or two of light customization afterward for anything genuinely unique to that client. Over a year of onboarding new clients, that difference compounds into weeks of reclaimed time.
How to Share a Snapshot
Snapshots can be shared with other agency users on your team, or in some cases submitted to the GHL marketplace for other agencies to use. Sharing internally is the more common use case for most agencies, keeping a library of proven setups available to anyone on the team handling client onboarding.
How to Deploy a Snapshot to a Sub-Account
Deploying takes seconds: select the snapshot, choose the destination sub-account, and confirm. After deployment, always check that phone numbers, payment integrations, and any account-specific connections are properly linked, since these typically need to be set up individually per client even when everything else transfers cleanly.
We recommend building a short post-deployment checklist your team follows every single time, phone number connected, test SMS sent, test email sent, calendar booking tested, and payment processor linked if relevant. A five-minute checklist run consistently after every deployment catches the overwhelming majority of issues before a client ever notices something's missing.
Building Niche-Specific Snapshots
The real leverage comes from building one polished snapshot per niche you serve, dental, real estate, home services, whatever your client mix looks like, rather than one generic snapshot for everyone. A niche-specific snapshot already includes the right pipeline stages, the right follow-up messaging, and the right automations for that industry's actual sales process, saving hours of customization per new client.
For example, a dental-specific snapshot might include pipeline stages built around new patient intake, appointment confirmation, and recall reminders, while a real estate snapshot's pipeline reflects buyer inquiry, showing scheduled, offer submitted, and closed. Trying to force one generic pipeline structure across both industries produces a worse result for both than two purpose-built ones.
Agencies serving three or four core niches typically find that maintaining a dedicated snapshot per niche, refined over time based on what actually works for real clients in that space, becomes one of their most valuable internal assets, arguably more valuable than any single piece of custom automation.
Common Snapshot Mistakes and How to Fix Them
The most common mistake is capturing a snapshot before the underlying setup is actually finished and tested, which means every future deployment inherits the same unfinished flaws. Fix this by treating your source sub-account as a real, live-tested build before ever saving it as a template others will rely on.
A second common mistake is never revisiting old snapshots once they're created. A snapshot built two years ago may reference outdated pricing, discontinued services, or automation logic that no longer reflects how you actually work with clients today. Set a recurring reminder to review and refresh your core snapshots at least twice a year.
Keeping a Snapshot Library Organized as You Grow
As agencies build more snapshots over time, naming and organization start to matter. A clear naming convention, niche, version number, and last-updated date, saves real time later when you're trying to remember which snapshot is the current best version versus an older draft that should be retired.
How Grow HighLevel Builds and Deploys Snapshots for Agencies
As part of our Done-For-You GHL builds, we regularly create custom, niche-specific snapshots for agencies so every new client launches from a proven foundation instead of a blank account. This is especially valuable for agencies running SaaS mode, where fast, consistent onboarding directly affects how quickly a new subscriber sees value. If you'd rather have a specialist maintain your snapshot library long-term, you can also hire a dedicated GoHighLevel expert for ongoing support.
Frequently Asked Questions
Can I update a snapshot after clients have already used it?
Yes, you can update your master snapshot at any time, though updates won't automatically apply to sub-accounts that were already deployed. You'd need to redeploy or manually update those individually.
Can I test a snapshot safely before using it on real clients?
Yes, and we strongly recommend it. Deploy to a throwaway test sub-account first, run through every automation and calendar booking as if you were a real lead, and only roll it out to actual clients once you're confident it behaves correctly end to end.
Do snapshots transfer contact data?
No, contact records typically do not transfer with a snapshot. Snapshots capture the system structure, not the client's actual customer data.
How many snapshots can an agency have?
There's no meaningful practical limit, so agencies commonly build a library of several snapshots covering different niches or service tiers.
Can snapshots be sold to other agencies?
Yes, some agencies build and sell niche-specific snapshots to other GoHighLevel users, either directly or through the marketplace.
What should I check immediately after deploying a snapshot?
Always verify phone number connections, payment integrations, and that automations are actually active, since these commonly need manual reconnection per sub-account.
How often should I update my snapshots?
A twice-yearly review is a reasonable baseline for most agencies, though any major change to your service offering or pricing structure should trigger an immediate update rather than waiting for the next scheduled review.
Do snapshots work the same way across every GoHighLevel plan tier?
Snapshot functionality is generally available across agency-level plans, though the ability to run unlimited sub-accounts to deploy them to is specifically an Unlimited and Agency Pro feature.
Should every agency use snapshots regardless of size?
Yes, even a small agency with just two or three clients benefits from the consistency and time savings snapshots provide, and the habit only becomes more valuable as client count grows.
Can a snapshot include AI Employee or Conversation AI training?
Yes, AI Employee configuration can be included in a snapshot, which is especially valuable for agencies deploying similar AI-driven follow-up across many niche-specific client accounts.
Want a proven, niche-specific snapshot built for your agency instead of starting from a blank account every time? Book a discovery call to see how Grow HighLevel can build and manage your GoHighLevel account.
Related Guides
Ready to Build This Inside Your Own Account?
We help agencies set up, automate, and scale their GoHighLevel accounts, without the trial and error. Whether you need the full build done for you or a specialist placed directly on your team, we can help.