GoHighLevel Snapshots: What They Copy, What They Don't, and How to QA One Before It Goes Live

What is a GoHighLevel snapshot?

A template. HighLevel's snapshots overview, updated 7 May 2026, calls them "reusable templates that capture selected configuration assets from a HighLevel sub-account." The purpose is copying them "into new or existing sub-accounts." The creation guide puts it plainly: "You build a sub-account, not the snapshot itself. Then you capture that sub-account using the snapshot tool."

To create a snapshot in GoHighLevel, go to Agency View, then Account Snapshots, then Create New Snapshot. You name it, pick the source sub-account, and select assets by category or folder. The nested asset selector (1 June 2026) shows folders, sub-folders and assets in an expandable tree, and selecting a folder selects everything inside it.

Three actions matter after that. Load puts it into a new or existing sub-account. Share gives another agency a link to import. Refresh with Push Updates sends changed assets to sub-accounts that already loaded it. The rest of this post is what each one does and doesn't do.

What do GoHighLevel snapshots copy, and what do they leave out?

The overview page carries both lists. The principle sits above them: "Snapshots are designed to transfer configuration and selected reusable assets, not live account activity or customer records." The included table runs to twelve categories, merged here into seven rows.

The exclusion list from the same page names sixteen items. The wording below is HighLevel's; the grouping is ours.

Do GoHighLevel snapshots update automatically?

No. The overview FAQ answers the question directly: "You must refresh the Snapshot to capture new or changed assets from the source sub-account." The refresh guide, updated 27 August 2026, says the same and adds the boundary: "Updates only push to sub-accounts inside your own agency. External agencies must re-import using a new link."

After a refresh, a Push Update button lets you pick which sub-accounts receive the change and which assets go, "only workflows, or specific forms," in the guide's words. The guide also says "Pushed updates are selective, not destructive - existing data stays safe." When a refresh deletes workflow steps, HighLevel removes contacts waiting on the deleted step so they don't get stuck. The linked assets setting controls which assets a push can carry; unlinking an asset only affects future pushes.

Rollback and reporting both have gaps. Version Management records what changed after each successful refresh, but "does not include a built-in revert/restore action." And the push history page shows sub-accounts processed, pending and failed. HighLevel notes there, in a November 2024 entry, that asset-level status could show Completed when not every asset loaded. Check the sub-account, not just the log.

How do you share a GoHighLevel snapshot?

You create a share link for the snapshot and pick one of six link types, per the sharing guide updated 12 September 2026. Which one you pick decides whether the recipient can reuse the link, and whether your assets can leave their agency again.

The switch that matters for anyone who builds snapshots for a living is Assets Protected, formerly called IP Protected. HighLevel's FAQ: the receiving agency can reuse protected assets across its own sub-accounts and snapshots. On re-sharing or reselling, "the restriction is enforced when the protected assets would leave the receiving agency. Protected assets cannot be redistributed or resold to another agency." You don't have to strip them out of a mixed snapshot; HighLevel excludes them during external sharing.

Importing a shared link doesn't touch any client account. The import guide says "Importing does not automatically place Snapshot assets inside a client account." It lands in your Imported Snapshots list, and loading is a separate, deliberate step. If a user can't see the share option, the granular permissions for Share/Import Snapshots are the first place to look.

What happens when you load a snapshot into an existing sub-account?

A conflict check, then a choice per asset. The load guide, updated 27 August 2026, defines the two options. Override "Replaces the existing sub-account item with the snapshot version." Skip "Keeps the current version and excludes the conflicting snapshot item." You type "confirm" before it runs.

Some assets arrive switched off. Funnels and websites: the create-from-snapshot guide says they "won't be live until you connect a custom domain and publish them." And LinkedIn ad campaigns, which the load guide says "are always created in Draft status." If some assets fail while a snapshot is being created, Force Create builds it anyway, with "a summary report" listing the skipped assets.

The GoHighLevel snapshot marketplace and the free industry library

Two official sources, and a lot of unofficial ones. HighLevel maintains a free industry snapshots library with fifteen templates, from marketing agency and dentist to plumbing and travel agency. The marketing agency snapshot page describes it as "a foundational template for establishing sub-accounts" with "a website, forms, calendars, workflows, email campaigns, online ads, and social posts." Most of those pages were last updated in 2024, one dates from 2020, and only Hair Salon was revised in September 2026. Treat most of them as a starting skeleton, not a current build.

The App Marketplace is the official GoHighLevel snapshot marketplace, where agencies sell snapshots inside the platform. HighLevel's selling guide (25 March 2026) lists three pricing models: "Free," "Freemium," and "Paid: Charge a one-time fee, monthly, or yearly subscription." Distribution is a second choice: charge agencies directly, or charge sub-accounts each time the snapshot is pushed. Listings are reviewed "for white-label compatibility within 7-10 days," and IP protection means "Buyers CANNOT repackage or resell your Snapshot assets." The page doesn't mention a listing fee or revenue share, so ask HighLevel before you list.

Most other snapshots you'll find by searching "GoHighLevel snapshots" or "GHL snapshots" come from third-party GHL vendors or resellers. The Asset Viewer is how you see what's inside one before you load it. It lists every funnel, workflow, template, calendar, form, product and AI project the snapshot contains. That's the first step of our QA.

How we QA a snapshot before it goes live

Ten checks. Steps 1 to 4 happen before the client load, in the Asset Viewer and a throwaway sub-account. Steps 5 to 10 run in the client's sub-account right after the load, before anything goes live. A snapshot that looks complete in the Asset Viewer can still land with its plumbing disconnected. The exclusion list is exactly the plumbing: integrations, numbers, Stripe, licenses. Status is the other surprise: when we loaded a snapshot into our demo account, 21 calendars came across and most showed as Inactive.

1. 01Open it in the Asset Viewer and count. Funnels, workflows, templates, calendars, forms, products, AI projects. If the seller's list and the viewer's list differ, stop.
2. 02Load it into a test sub-account, never a client's, and ask the seller whether it was force-created.
3. 03Open every workflow and check its publish state, the same check we run on our 12 client automations after every load. HighLevel's workflow walkthrough says "Draft mode means the workflow will not trigger and take actions for real; Publish mode means it will." Whatever the snapshot did, this is where you find out.
4. 04List every custom value the workflows and templates reference. After the client load, fill the empty ones in the client's sub-account before anything sends.
5. 05Connect a domain and publish the funnels and websites; they arrive as drafts. Check each calendar's status too; in our demo load, most showed as Inactive.
6. 06Reconnect what the exclusion list dropped: Stripe, Google, Facebook, calendar connections, and any third-party account.
7. 07Assign phone numbers to Voice AI agents and to any workflow that sends from a specific number. Texting also waits on the sub-account's own A2P registration.
8. 08Open each dashboard. The dashboards article says widgets error when the custom values or pipelines they depend on weren't included; edit and save each flagged widget.
9. 09Re-authenticate WordPress licenses and wait for Meta approval before counting on WhatsApp, per the exclusion list.
10. 10Send one live lead through the front door and watch it hit the pipeline, the text, the calendar and the notification. Only then tell the client it's live.

How we use snapshots for clients

One master per vertical, refreshed on purpose, pushed selectively. Each master lives in its own source sub-account that never belongs to a client, so a refresh captures only what we changed. After a refresh we push workflows and templates, not calendars or pipelines, because those are the assets a client has usually customized. Assets Protected is on for anything we've built ourselves.

The snapshot is day one of the client onboarding checklist; the reconnection work above is most of week one. On Agency Pro, SaaS mode can load it for you: the SaaS Configurator says "The configured snapshot is applied when a snapshot is attached to the SaaS plan." The complete setup guide walks the build the snapshot is meant to shortcut. If an account was set up from a bought snapshot by someone else, the 12-point audit finds what the load left unplugged.