I have built and loaded a lot of GoHighLevel snapshots. Done well, a snapshot turns a job that used to take days into an afternoon; done badly, you inherit someone else’s mess and spend a week untangling it. Here is what a GoHighLevel snapshot actually is, what it copies, what it quietly leaves behind, and how to decide whether to build one, buy one, or start from a free template.
Affiliate Disclosure: Some of the links on this page are affiliate links, which means I may earn a commission if you click through and start a paid plan, at no additional cost to you. I only recommend tools I use myself, and GoHighLevel has been in my stack for years. I follow the FTC’s endorsement guidance so you always know where I stand.
TL;DR
- ●A GoHighLevel snapshot is a reusable template that copies a sub-account’s setup, including workflows, funnels, calendars, forms, pipelines, and dashboards, into another sub-account.
- ●Snapshots carry structure and settings. Live data like contacts, conversations, and appointments stays behind, so you reconnect the moving parts after loading.
- ●You can build your own, buy a niche template, or start from a free one, and the quality varies a lot.
- ●No snapshot makes you compliant in a regulated niche like telemedicine. You still own how patient data is handled.
What a GoHighLevel Snapshot Actually Is
Think of a snapshot as the blueprint for a GoHighLevel sub-account. When you create one, GoHighLevel captures the assets you select from a source sub-account: the workflows, funnels, websites, calendars, forms, pipelines, tags, custom fields, dashboards, and templates, then packages them so you can drop the whole setup into another account. The mental model I keep in my head is simple: the snapshot holds the structure, and the sub-account holds the data.
You do not build a snapshot from a blank screen. First you set up one sub-account the way you want it, then you create a snapshot from that account. GoHighLevel’s own documentation lays out what each snapshot can carry, and the list is long.
What Transfers in a Snapshot and What Stays Behind
The reason snapshots save so much time is that they carry the parts that take the longest to build. On the structure side, you get workflows, funnels and websites, email and text templates, calendars, forms and surveys, pipelines, tags, custom fields, custom values, trigger links, dashboards, and more recently AI agents and ad campaign structures.
Here is the part most sales pages skip. A snapshot leaves your live account activity behind. Contacts, conversations, message history, appointments, reputation data, Stripe connections, third-party integrations, and assigned phone numbers do not travel with it.
| Carried in the snapshot (structure) | Left behind (live data) |
|---|---|
| Workflows, funnels, and websites | Contacts and conversations |
| Email and text templates | Message history |
| Calendars, forms, and surveys | Appointments and reputation data |
| Pipelines, tags, custom fields and values | Stripe connection and integrations |
| Trigger links, dashboards, AI agents, ad structures | Assigned phone numbers |
So when you load a snapshot into a client account, you still reconnect the domain, the calendar, the payment processor, and any integrations before the account is ready to run. Budget an hour or two for that cleanup on a real client build.
I treat that as a feature. You would not want a template dragging another business’s contacts into your client’s account. The snapshot gives you the machine, and you supply the fuel.
How to Create a Snapshot in GoHighLevel
Creating a snapshot takes a few minutes once the source account is set up the way you want. Start from your agency account, since snapshots live at the agency level and not inside a single client sub-account. If GoHighLevel is brand new to you, my introduction to GoHighLevel covers the basics first.
Set Up a Clean Source Sub-Account
Build one sub-account with the workflows, funnels, calendars, and templates you want to reuse. A tidy source account makes a tidy snapshot, so clear out test contacts and half-finished automations first.
Open Account Snapshots in Agency View
Go to Agency View, then Account Snapshots, and click Create New Snapshot. Give it a name that describes the use case, something like Dental Intake or Med Spa Launch, so future you knows what is inside.
Choose the Assets to Include
Select the whole account or expand each category and hand-pick items. I usually include the workflows, funnels, forms, calendars, and pipelines, and leave out anything specific to the source client.
Save and Test the Snapshot
Click Create to save it. Load the snapshot into a throwaway sub-account and walk through the funnels and workflows before you ever put it in front of a client.
How to Load, Share, and Refresh a Snapshot
Once a snapshot exists, GoHighLevel gives you a handful of actions, and knowing the difference keeps you out of trouble. Loading applies the snapshot’s assets into a new or existing sub-account. Sharing generates a link so another agency can import your snapshot into their own account.
Refreshing is the one people forget. A snapshot does not update itself when you improve the source account, so you refresh the snapshot to capture the changes, then push those updates to the sub-accounts you have linked to it. That is how you fix a broken workflow once and roll it out to fifty clients instead of editing fifty accounts by hand.
Loading into an account that already has data is safe by default. GoHighLevel adds the new assets and overwrites something only when you choose to override a conflict during the load.
When to Build, Buy, or Use a Free Snapshot
You have three ways to get a snapshot, and I have used all of them. Building your own gives you total control and a setup you understand top to bottom, which matters when a client asks why something works the way it does. The cost is time, and a solid niche snapshot can take many hours to build and test.
Buying a niche snapshot from a marketplace saves that time. A good paid template drops in a proven funnel and workflow set for a specific vertical, and the better sellers keep them updated. Prices often run into the hundreds of dollars for a single niche, so vet the seller before you spend.
Free snapshots are everywhere, and some are genuinely useful. Plenty are thin, outdated, or stuffed with the seller’s own branding and trigger links, so treat a free snapshot as a starting point you will clean up rather than a finished product. If you plan to resell snapshot-based accounts under your own brand, that is where white-label pricing starts to matter.
How to Vet a Snapshot Before You Load It
A bad snapshot costs more than building from scratch, because you spend days undoing decisions you did not make. Before I load anyone else’s snapshot into a client account, I run through a short checklist.
Load the file into an empty test sub-account first and open every funnel and workflow. Look for broken links, placeholder text, and the seller’s own trigger links or branding hiding inside emails. Check that the automations use current GoHighLevel workflows and steer clear of the deprecated campaigns and triggers that older templates still carry.
Ask the seller how often the snapshot is updated and what support looks like when something breaks. A snapshot is a living setup, and one that has not been touched in two years will show its age.
Snapshots for Telemedicine and Regulated Niches
Snapshots are a shortcut for structure, and structure is where regulated niches get people in trouble. In telemedicine, the data flowing through those forms and workflows is protected health information, and a template does nothing to change your obligations around it.
I am an operator rather than your attorney, so treat this as practical guidance and take any compliance decision to qualified counsel or the primary authority. The point stands: in a regulated vertical, the snapshot is the easy part, and the responsibility is still yours.
Which GoHighLevel Plan Includes Snapshots
Good news here: snapshots come with every GoHighLevel agency plan, so you can create, load, and share them even on the entry Starter tier. The higher tiers change what you can do around snapshots rather than whether you get them.
White-label becomes available on the middle Unlimited plan, which matters once you want clients logging into your brand instead of the HighLevel name. SaaS features on the top plan let you sell snapshot-based sub-accounts as your own software product with automated signup and billing. Plans and prices change, so check the current numbers on the GoHighLevel pricing page, and if you are weighing tiers, I walk through picking the right GoHighLevel plan in a separate guide.
Frequently Asked Questions
Where Snapshots Fit in a Real Workflow
A GoHighLevel snapshot is the fastest way I know to turn a proven setup into something you can deploy again and again. The skill is not in loading one; the skill is knowing what belongs in it, what to strip out, and what to reconnect on the other side. Get that right, and you launch clients in an afternoon instead of a week.
If you want a snapshot built around your vertical, especially in telemedicine where the setup has to respect how patient data moves, that is work I do. Start a conversation and tell me what you are trying to launch, and we can map it out together.
