HighLevel How To
GoHighLevel Snapshots Explained: What They Are, How to Build One and How Agencies Use Them
GoHighLevel snapshots explained: what a snapshot carries, how to create, load, update and sell one, the master snapshot idea and the mistakes to avoid.
Sign up through Michael's link and the CRM Pros team gets you set up in your first 7 days, with weekly calls and the community included.
HighLevel How ToCopy a working setupThe short answer
GoHighLevel snapshots are saved copies of a subaccount setup: workflows, funnels, forms, calendars, pipelines, custom fields, email templates and more, without the contacts. You build the setup once, save it as a snapshot and load it into any new subaccount in minutes. Agencies run a master snapshot and push updates to clients. Some sell niche snapshots as products.
Key takeaways
- A snapshot copies configuration, not data. Contacts, conversations, connected phone numbers and payment integrations never travel with it.
- Build one master snapshot per niche and load it into every new client. Fixing one thing in the master fixes it for every future client.
- Loading a snapshot into an existing account can overwrite assets with the same name. Read the options before you click.
- Name versions by date and keep a one line change list. Snapshots have no undo of their own.
- A snapshot is only worth selling if the buyer can load it and get results without you. Document it like a product.
Do this in your own accountEverything in this article runs inside HighLevel. Start through Michael's link and build it with the team on the weekly calls.
Start a 30 Day TrialSetup included. We build it with you.Upgrade My PlanOn HighLevel? Unlock your benefits.What GoHighLevel snapshots are
GoHighLevel snapshots are the reason an agency can onboard a new client in an afternoon instead of a month. A snapshot is a saved copy of how a subaccount is set up. Every workflow, funnel, form, calendar, pipeline, custom field, email template and tag, captured as a package you can load into another subaccount. Build the system once. Deploy it as many times as you like.
How it works
Build once, deploy many times
- Build it onceBuild and test everything in one subaccount first.
- Save a snapshotName it and pick the subaccount to copy from.
- Load itApply it when you create a new subaccount.
- Connect the accountAdd the phone number, domain, calendar and payments.
- Test one pathSubmit the form and watch the text arrive.
Think of it as the floor plan for a franchise location. The plan says where the counter goes, how the kitchen is laid out and what the signage looks like. It does not include the customers who will walk in. That is exactly the distinction with snapshots: configuration travels, data does not.
My team at CRM Pros has 2,600 agentic systems deployed on HighLevel, and every one of them started from a master snapshot. Without that, 2,600 installs would have meant 2,600 rebuilds. With it, each install is a load, a few connections and a review. This guide covers what a snapshot carries, how to create, load, update and sell one, and the habits that stop snapshots from turning into a mess. If you are new to the platform, my one day setup tutorial explains the agency and subaccount layers that snapshots sit on.
What a snapshot carries and what it leaves behind
The first question every Founder asks is whether contacts come along. They do not, and that is by design. A snapshot is a template, and a template full of someone else's customers would be a privacy problem.
| Travels with the snapshot | Stays behind |
|---|---|
| Workflows and automations | Contacts and their history |
| Funnels, websites and forms | Conversations, calls and messages |
| Calendars and their settings | Connected phone numbers and A2P registration |
| Pipelines and stages | Connected email domains |
| Custom fields and custom values | Payment integrations and products with live prices |
| Email and text templates | Users and their permissions |
| Tags, surveys and trigger links | Third party integrations and API keys |
| Conversation AI and Voice AI settings in most cases | Reporting history |
The practical consequence is that every snapshot load is followed by a short connection checklist: add the phone number, connect the domain, connect the calendar, set the custom values such as business name and booking link, connect payments. My team keeps that checklist to one page. The snapshot does the hours of work. The checklist does the minutes.
A note on custom values. These are the variables a snapshot uses so that one set of workflows can serve many businesses. A text that says the business name should pull it from a custom value, not have it typed in. Build your snapshot that way from the start and loading it into a new client becomes a matter of filling in a short form rather than editing forty messages.
How to create a snapshot
Creating a snapshot takes about a minute. The work is in the subaccount you build it from.
- Build and test the subaccount. Everything you want copied must exist and work here first. Treat it as your clean room: no test contacts, no half built funnels, no workflows named Test 2.
- Switch to the agency view and open Account Snapshots.
- Click Create New Snapshot, give it a clear name and pick the subaccount to copy from.
- Save. HighLevel builds the snapshot in the background. Large accounts with many funnels take a few minutes.

Two things to do before you click save. First, open every workflow and check that the merge fields and custom values are coming from the picker rather than hard typed. Second, delete anything you would not want a client to see. A snapshot copies the whole subaccount, including the experiments you forgot about.
My rule of thumb. Build the snapshot from a subaccount that has never had a real client in it. The moment you snapshot a live client account you copy their quirks, their abandoned funnels and their naming, and every future client inherits them.
Build it with us
Put this to work in your own HighLevel.
HighLevel is the AI powered business operating system this site is built around. Start through Michael's link and you are not on your own: the CRM Pros team and nearly 4,000 affiliates are already building the same way.
- Setup help in your first 7 days from the CRM Pros team
- One onboarding call, then three live calls every week
- The affiliate community, snapshots, templates and email swipes
- Four apps included: Prompt, Demo, A2P and Sales On Demand
Already on HighLevel? Upgrade through Michael's link for the same bonuses.
How to load a snapshot into a subaccount
There are two moments to load a snapshot. The clean one is when you create a new subaccount: the creation screen asks which snapshot to apply, you pick yours, and the new account arrives fully built. The other is loading into an existing subaccount, which is how you push updates to clients.
Loading into an existing account is where people get hurt. HighLevel asks what to do with assets that already exist under the same name: overwrite them, skip them, or in some areas keep both. Overwrite is right when you are pushing a corrected workflow and you want the old one gone. Skip is right when the client has customized that funnel and you do not want to flatten their edits. Read the screen. Pick per asset type when the option is offered. And do it outside business hours, because an overwritten workflow mid afternoon can interrupt contacts moving through it.
After any load, run the connection checklist from the earlier section, then test one real path end to end: submit the form, watch the text arrive, see the pipeline card move. I build this testing step into every deployment my team does, and it is the reason the systems keep running. More on that discipline in AI systems in production.
The master snapshot: one source of truth per niche
A master snapshot is the one you maintain. Every new client starts from it. Every improvement goes into it first. Every client account is, in effect, a copy of the master plus that client's own connections and tweaks.

This is how CRM Pros works. We keep a master snapshot with a mandatory workflow list: each workflow has a name and one sentence describing what it does, and that list is the specification. When a client reports a problem, we fix it in the master, test it, then push the fix out. When HighLevel ships a feature worth adopting, such as a new Workflow AI action, it goes into the master, not into one client account. The list of what the master must contain is deliberately short, because every item on it is something we have promised to maintain forever.
If you serve more than one niche, keep one master per niche rather than one giant master with everything switched off. A dental practice and a roofing company need different pipelines, different calendars and different language. A master that tries to serve both ends up serving neither. The snapshots share a common core, the five workflows every business needs from my workflows guide, and differ in the niche layer on top.
The master snapshot is also what makes a white label business possible. When you sell your own branded software on HighLevel, the master is the product. I cover that model in my white label guide.
Version control for snapshots
HighLevel keeps snapshots as separate saved objects, so version control is a habit rather than a feature. The habit is simple.
- Name every saved snapshot with the niche and the date, such as Dental Master 2026 11 02.
- Keep a change list beside it: one line per change, newest at the top. What changed, why, and what to check after loading.
- Never overwrite the previous version. Create a new snapshot each time and keep the last three.
- Before pushing to clients, load the new version into a fresh test subaccount and run the full test path.
- Push to one client, wait a day, then push to the rest.
Inside workflows, HighLevel does give you version history. Set a workflow to Draft, open the version history from the toolbar and restore an earlier version if an edit went wrong. That protects individual workflows. The dated snapshot list protects the whole system.
Updating the master without a change list is how agencies end up unable to explain why client A has a review workflow that client B does not. Write the line. It takes ten seconds.
Selling snapshots and the mistakes that get people burned
Snapshots can be shared by link, by email to a specific agency, or as a permanent link anyone can import. That makes them a product. Agencies sell niche snapshots to other agencies, bundle them with onboarding calls, or include them in a community. A snapshot is worth paying for when it carries a tested set of workflows, funnels and templates that would take a buyer weeks to build and that work without the seller standing beside them.
If you plan to sell, treat it like software. Document every custom value the buyer must fill in. Record a short walkthrough. State which plan and which add ons are needed, because a snapshot that depends on Conversation AI will not run on an account without it. And keep a changelog so buyers know what changed between versions. Pricing is yours to set, and I would steer you away from any promise about what the buyer will earn with it.
Mistakes I see most often
- Snapshotting a live client account and shipping their test data and abandoned funnels to everyone.
- Hard typing the business name, phone number and booking link into messages instead of using custom values.
- Loading a snapshot into a client account with overwrite on and flattening the client's custom work.
- Assuming contacts, phone numbers or payment settings came across, then wondering why nothing sends.
- No dated versions and no change list, so nobody knows which client has which build.
- Importing a free snapshot from an unknown source without reading every workflow first. A snapshot can contain webhooks pointing anywhere.
Used with discipline, snapshots are the single biggest lever an agency has on HighLevel. They turn a service business into something closer to a product business, where the work compounds instead of repeating. If you want to see how the pieces fit, start at my HighLevel hub, check plans and pricing, browse the how to library, or See what Founders get and build your first master this week.
For a one paragraph definition, see the snapshot glossary entry, and for the clicks, follow how to create a snapshot in HighLevel. If you are still judging the platform, the HighLevel review is an honest look from a daily user, and the 30 day trial page explains how the trial through my link works.
For page designs on their own, read about GoHighLevel website templates.
Agencies and resellers should also read the Founder Plan page, which covers HighLevel's top plan. What a Founder is and who the plan fits is on the GoHighLevel Founder Plan hub.
Questions Founders ask
Frequently asked questions.
What are GoHighLevel snapshots?
GoHighLevel snapshots are saved copies of a subaccount setup: workflows, funnels, forms, calendars, pipelines, custom fields, templates and tags. You create one from a built subaccount and load it into other subaccounts so you never rebuild the same system twice.
Do GoHighLevel snapshots include contacts?
No. Snapshots copy configuration, not data. Contacts, conversations, connected phone numbers, email domains, users and payment integrations stay behind and must be connected in each new subaccount after the load. After any load, run through those connections, then test one real path from form to text to pipeline.
How do I create a snapshot in GoHighLevel?
Build and test a clean subaccount, switch to the agency view, open Account Snapshots, click Create New Snapshot, give it a clear name and choose the subaccount to copy from. HighLevel builds the snapshot in the background. Then load it into a fresh subaccount to check it before any client gets it.
Can I update a snapshot after clients are using it?
Yes. Make the change in your master subaccount, save a new dated snapshot, test it in a fresh subaccount, then load it into client accounts. Choose overwrite or skip per asset type so you do not flatten client customizations.
Can you sell GoHighLevel snapshots?
Yes. Snapshots can be shared by link or permanent link and many agencies sell niche snapshots to other agencies. Document the custom values, required plan and add ons, and keep a changelog so buyers can load it and get results without you.
What is a master snapshot?
A master snapshot is the one maintained version your agency starts every new client from, one source of truth per niche. Fixes and new features go into the master first, get tested, then get pushed to clients, which keeps every account consistent.
How do I import a snapshot?
There are two ways. When you create a new subaccount, the creation screen asks which snapshot to apply, and the account arrives fully built. To load into an existing subaccount, choose overwrite or skip for assets that already exist, and do it outside business hours so live workflows are not interrupted.
Are snapshots plug and play, or do they need customization?
They need some setup. A snapshot carries the configuration, but phone numbers, email domains, users and payment integrations must be connected in each new subaccount, and the custom values have to be filled in with the client's details. Then test one real path end to end before the account goes live.
Sources
Keep reading



