GoHighLevel Snapshots: What They Are and How to Use Them

Almost everyone who sticks with GoHighLevel meets snapshots the same way. You hear that a snapshot is a done-for-you account you can drop in with one click, you find a free one online, you load it into a fresh sub-account, and you sit back expecting a finished system. Then you open it. Workflows are firing at nobody. Custom values are empty. A funnel references a calendar that does not exist. Half the automations point at a phone number you never set up. The one-click miracle turns into an afternoon of untangling.

None of that means snapshots are bad. It means the promise most people repeat about them is wrong. A snapshot is one of the most useful things in the whole platform once you understand exactly what it copies, what it quietly leaves behind, and what it does when you push an update to an account someone has already been working in. Get those three things right and a snapshot saves you days on every new build. Get them wrong and it costs you more time than starting from scratch.

We run these systems for a living. My team has built, sold, and pushed updates to snapshots across hundreds of agency and client accounts since 2018, so this is the plain version, with the parts the sales pitch skips left in.

What a GoHighLevel snapshot actually is

A snapshot is a saved copy of how an account is built. Not what is inside it, how it is built. When you take a snapshot of a sub-account, GoHighLevel captures the configuration and the reusable assets: the workflows, the funnels and websites, the calendars, the forms, the email templates, the pipelines, the custom fields, and so on. It bundles all of that into a single package you can then load into a brand new sub-account so that account opens with a full setup instead of an empty shell.

The mental model that keeps people out of trouble is this: a snapshot is a blueprint, not a moving truck. A blueprint of a house tells you where every wall and outlet goes, and you can build the same house a hundred times from it. It does not carry the furniture, the people, or the electricity. A snapshot is the same. It carries the structure of an account. It does not carry the contacts, the conversations, the booked appointments, or the live connections that make the account actually do anything. Those get added after, per account.

This is exactly why snapshots exist for agencies. If you build one great account, say a full setup for a dental practice with the intake forms, the reminder workflows, the review-request automation, and the booking calendar, you can snapshot it once and stamp that same build into every new dental client you sign. New sub-account, load the snapshot, and 80% of the work is already there. That repeatability is the whole reason the white-label model works, and it is a big part of what we do when we run white-label fulfillment for agencies who resell HighLevel under their own brand. If you are still deciding whether the platform is right for you at all, start with our plain-English guide to what GoHighLevel is.

What a snapshot does and does not transfer

This is the single most important table in this article, because almost every snapshot disaster traces back to someone assuming the right column would come along. It will not. HighLevel's own documentation is clear on the split: a snapshot moves configuration and reusable assets, and it leaves live data and account connections behind.

Read the right column carefully, because it explains every one of those "the snapshot is broken" moments. The workflow that texts a new lead comes through fine, but the phone number it sends from does not, so until you connect a number and clear A2P registration, the automation is pointing at nothing. The checkout funnel loads perfectly, but the Stripe connection behind it does not, so no payment will process until you link an account. The custom values that the whole build reads from, business name, booking link, address, come through empty, because a value is a placeholder and the actual text was live data in the original account.

There is a reassuring flip side to all of this. Because a snapshot never touches live data, loading one into an account that already has contacts will not delete them. A snapshot only adds. The one time existing setup changes is a naming conflict, where an asset in the snapshot shares a name with one already in the account and you choose to override it during the load. Your customer data is never in that conversation. That safety is real, and it is why loading a snapshot into a working account is far less scary than it sounds, as long as you know a pushed update behaves differently, which we will get to.

Snapshot vs template vs backup

These three words get used as if they mean the same thing, and mixing them up is how people end up expecting a snapshot to do something it cannot.

• A template is usually a single reusable asset. One funnel, one email, one workflow you copy and adapt. Useful, but small.
• A snapshot is an account-level bundle of many assets at once, the workflows and funnels and calendars and pipelines and settings together, packaged so a whole account can be stamped out in one move.
• A backup implies you can restore what was there, including contacts and history. A snapshot is not a backup. It never carries live data, so it cannot bring your contacts or conversations back if something is deleted. If protecting live data is the goal, a snapshot is the wrong tool, and you want an export or a proper backup process instead.

Keep those straight and the rest of snapshots gets much simpler. You use a snapshot to replicate a build, not to move data and not to insure against losing it.

How to create a snapshot

Creating one is short, and the discipline is in what you do before you click, not the clicking itself.

Once saved, the snapshot sits in your agency library ready to load into a new or existing sub-account, share by link, or update later. One habit worth building early: strip anything account-specific out of the source before you snapshot it, or leave custom values blank on purpose, so the snapshot arrives clean instead of carrying one client's booking link into the next client's account.

How to load a snapshot into an account

There are two moments you will load a snapshot, and they behave a little differently.

Into a brand new sub-account. This is the clean case. When you create a new sub-account you can choose a snapshot to build it from, and the account opens already populated with the whole setup. Nothing to conflict with, nothing to overwrite. This is the path agencies use to onboard a new client in minutes instead of days.

Into an existing sub-account. This is the case that needs care. You can load a snapshot into an account that already has assets, and again it will not delete contacts or conversations. But if the snapshot contains a workflow or funnel with the same name as one already there, you will be asked how to handle the conflict, and choosing to override replaces the existing version. Rename anything you want to keep before you load, and read the conflict prompts rather than clicking through them.

After either load, the account is built but not connected. That gap between "the assets are here" and "the account actually works" is where the real setup lives, and it is the part free snapshots never do for you.

How to share a snapshot: the five link types

If you sell snapshots, or hand one to a client or partner, you share it by generating a link, and GoHighLevel gives you real control over how open that link is. Picking the wrong one is how a paid snapshot ends up imported a hundred times for free.

On top of those, HighLevel has an assets-protected option (it used to be called IP protected) that you can turn on when you generate a share link, to make the assets inside a shared snapshot harder to re-share or copy. That matters if the snapshot is your product and you do not want it passed around for free.

One thing that surprises people: updates you make to a snapshot are not pushed automatically to snapshots you already shared with outside agencies. If you improve a snapshot after selling it, distributing the new version means resharing a fresh link, not flipping a switch that updates everyone. Pushing updates automatically only applies to sub-accounts inside your own agency, which is the next section, and it comes with a catch worth understanding before you ever use it.

Pushing snapshot updates without breaking client accounts

This is the feature that turns snapshots from a nice onboarding shortcut into a real management system, and it is also the one that quietly destroys client work when people do not understand it.

Here is the mechanism. When you push a snapshot update to sub-accounts that were built from that snapshot, GoHighLevel adds any new assets and overwrites the existing snapshot-linked assets, workflows, campaigns, and the rest, with the latest version from the snapshot. That overwrite is the whole point when the account is untouched, because it lets you fix a workflow once in the master and roll the fix out to fifty accounts at once. It becomes a problem the moment a client has customized one of those linked assets, because those custom edits are lost. The pushed version wins, and the client's changes are gone.

Picture it. You sold a snapshot with a "New lead follow-up" workflow. A client spent an afternoon tuning that workflow to their own script, their timing, their offer. You push a routine update to the whole snapshot. Their tuned workflow reverts to your generic version, and the afternoon is erased. Nothing warns them until they notice their automation is sending the wrong thing.

The protection is simple once you know the rule: a duplicate is no longer tracked by the snapshot. So the safe pattern for anything a client should be free to customize is to duplicate the asset first, for example "New lead follow-up (Copy)", have the client edit the copy, and point any connected automations at the copy. When the next update pushes, the original snapshot-linked version updates and the copy stays exactly as the client left it. If you sell or manage snapshots, teach every client this one habit and you will avoid the single most common support fire in the whole model.

Free vs paid snapshots, and "snapshots for sale"

Search "GoHighLevel snapshots" and half the results are trying to sell you one, and the other half are giving them away. Both can be worth it, and both can waste your week. The price tag is not the signal that matters.

A free snapshot is best treated as a reference or a head start, not a finished product. Someone built it for their business, or to generate leads, or to show off, and then packaged it. It arrives with the same gaps every snapshot has, no connections, no data, empty custom values, plus whatever quirks fit the original builder's process and not yours. Free snapshots are a great way to see how someone else solved a problem. They are a poor way to run your business unmodified, and a free one with no support behind it usually costs more hours to fix than it saves.

A paid snapshot mostly buys you two things beyond the assets: quality and support. A good paid snapshot has been used in real accounts, the workflows are tested, and there is someone to ask when a trigger does not fire. That is worth money. What you are still not buying, at any price, is a system that is connected to your account. Every paid snapshot still needs your phone number, your A2P registration, your calendar, your integrations, and your actual offer wired in before it does a thing.

The honest way to judge any snapshot, free or paid, is against the hours it removes and the hours it adds. That is also how to think about the platform overall, which we lay out in our GoHighLevel pricing guide. And if the setup is where you keep getting stuck, that is the exact gap a GoHighLevel expert exists to close.

A snapshot is a starting point, not a system

The whole reason a snapshot feels like magic is also its limit. It moves the structure of an account in one click, so it moves you 80% of the way on the parts that repeat. The last 20%, the connections and the fit to your process, is both the part that never comes in the box and the part that decides whether the account actually produces anything. A perfectly stamped-out account that is not connected to a phone number, a calendar, and your real offer does exactly nothing.

The higher-value use of snapshots is not chasing a free one that does everything, it is building a snapshot worth stamping out. When you have a process that genuinely works, templatizing it is where the payoff is. We built exactly that for a multi-location law firm drowning in unqualified leads: a custom filtering and case-segregation system that auto-qualifies incoming cases and refers the disqualified ones out. It cut their manual lead qualification time by 83%, and because it was built once and structured well, the same logic can be templatized across locations rather than rebuilt by hand each time. That is what a snapshot is for: not a shortcut around building something good, but a way to reuse something good once you have it.

So here is the short version of using snapshots well. Wire up whatever you load, because the connections never come with it. Duplicate before you customize, so a pushed update cannot erase your work. Judge free and paid snapshots by the time they save, not the price. And save your real energy for building the one account worth snapshotting, because that is the asset that pays off every time you stamp it out.

Frequently asked questions

What is a GoHighLevel snapshot?

A GoHighLevel snapshot is a saved copy of an account's configuration and assets that you load into another account. It bundles things like workflows, funnels, websites, calendars, forms, email templates, pipelines, triggers, and custom fields, so a new sub-account starts with a full setup instead of an empty shell. It does not carry live data such as contacts, conversations, or booked appointments. Think of it as a template for how an account is built, not a backup of what is inside it.

What does a GoHighLevel snapshot include and not include?

It includes configuration and reusable assets: workflows, funnels, websites, calendars, forms and surveys, email templates and campaigns, triggers, pipelines, custom fields and custom values, membership courses, products, AI Studio projects, and custom objects. It does not include contacts, appointments, conversation history, reputation and review data, users, reporting data, connected integrations such as Stripe, or your phone number and A2P 10DLC registration. Those are account connections and live data, not assets, so they stay behind.

How do I create a GoHighLevel snapshot?

From your agency view, open Account Snapshots in agency settings, choose Create Snapshot, and select the sub-account you want to capture. You can take everything or select specific assets. GoHighLevel saves that snapshot to your agency, where you can load it into a new or existing sub-account, share it by link, or update it later. Build and finish a real account first, because a snapshot only captures what actually exists at the moment you create it.

Will loading a snapshot delete my existing contacts or data?

No. Loading a snapshot adds assets and does not delete contacts, conversations, or appointments, because a snapshot does not touch live data at all. The only thing that changes existing setup is a conflict, where an asset in the snapshot has the same name as one already in the account and you choose to override it. Live customer data is never part of that.

What happens when you push a snapshot update to a client account?

Pushing a snapshot update adds any new assets and overwrites the existing snapshot-linked assets, such as workflows and campaigns, with the latest version from the snapshot. Any edits a client made directly to those linked assets are lost. To protect a customization, duplicate the asset first, edit the copy, and point automations at the copy, because a duplicate is no longer tracked by the snapshot and survives the update untouched.

Are free GoHighLevel snapshots worth it?

Sometimes, as a reference or a starting point, rarely as a finished system. A free snapshot with no support behind it is a bundle of someone else's workflows that still has to be connected to your phone number, your calendar, your integrations, and your actual process. Broken triggers, orphaned custom values, and automations pointed at things that do not exist are common. The snapshot is free, the hours spent untangling it are not, so judge it by the time it saves.

What is the difference between a snapshot and a template?

People use the words loosely, but in practice a template usually means a single reusable asset, such as one funnel or one email, while a snapshot is an account-level bundle of many assets at once: workflows, funnels, calendars, pipelines, and settings together. A snapshot is also not a backup. A backup implies you can restore contacts and history, and a snapshot never carries those, so it cannot bring back live data if something is lost.

How do I share a GoHighLevel snapshot with another agency?

GoHighLevel generates a share link, and you choose how open it is. A permanent link allows unlimited imports until you revoke it, a one-time link expires after a single import, an email link works like a one-time link sent by email, an agency-restricted link only lets specific agencies import, and a sub-account-restricted link targets one account. There is also an assets-protected option to make a shared snapshot harder to re-share or copy. Updates you make later are not pushed to already-shared snapshots automatically, so you reshare a new link to distribute changes.