What Is a GHL Snapshot? A Plain Guide for Agency Owners

A vendor in a GHL Facebook group drops a share link and says "import this and you're set." You paste it into a new tab, HighLevel asks if you want to import, you click yes, and then nothing visible happens. No new sub-account. No new workflows in the client you had open. That moment of confusion is the reason this post exists. A GHL snapshot is one of the most used features in Go High Level and one of the least precisely understood, and the "business in a box" definitions floating around don't help when you're staring at the Imported Snapshots tab wondering what you just did.

This post owns the precise definition: what a snapshot is, what it captures and what it deliberately leaves behind, how it differs from a workflow, a template, or the sub-account clone people keep asking for, and the handful of mechanics you'll hit in your first week. The bigger picture (marketplace, build versus buy, selling your own) lives in the Go High Level snapshots guide.

A GHL snapshot in one paragraph

HighLevel's own definition is the cleanest one available. Snapshots are "reusable templates that capture selected configuration assets from a HighLevel sub-account so they can be copied into new or existing sub-accounts." Three words in that sentence do all the work. Selected: you choose what goes in, category by category or item by item, at creation time and again at load time. Configuration: it's the structure (workflows, funnels, pipelines, fields, calendars), never the records living inside that structure. Copied: a snapshot is a point-in-time file stored at the agency level, and nothing changes in any sub-account until you explicitly load it. That's why the share link did nothing. Importing puts a snapshot in your agency's library. Loading is what applies it. Two separate actions, and HighLevel's snapshots overview is worth ten minutes if you've never read it.

What a snapshot captures, and what it leaves behind

The inclusion list has grown a lot since snapshots launched. As of the current docs, a snapshot can carry:

• Workflows and triggers, plus the AI layer: Conversation AI, Voice AI agents, Agent Studio, Brand Voice
• Funnels, websites, blogs, forms, surveys, quizzes, email templates, campaigns, and Social Planner settings
• Calendars, service categories, resources, and add-ons
• Pipelines, custom fields, custom values, custom objects, and tags
• Dashboards, custom reports, and metrics
• Memberships: products, certificates, webinars
• Design kit, knowledge bases, WhatsApp templates, WordPress sites
• Google, Meta, and LinkedIn ad campaign setups

The exclusion list is shorter and matters more. Snapshots do not include contacts, appointments, conversations or message history, reputation data, live account activity, Stripe connections, integrations and third-party connections, phone numbers assigned to Voice AI agents, LinkedIn lead gen forms, or private dashboards. WordPress sites come across but need the license re-authenticated.

Read that list as an agency owner and a few things fall out of it. You can't use a snapshot to migrate a client's contact list; that's a CSV export and import, or the Copy Contact workflow action. Every sub-account connects its own Stripe, its own social profiles, its own phone number, and does its own A2P registration, no matter how complete the snapshot was. Social Planner settings can ride along, but the connected Facebook and Instagram accounts don't, because those are integrations. And custom values do transfer, carrying whatever the source sub-account had in them. Which is why "the welcome email went out signed by the wrong dentist" is the single most common snapshot mistake on a new client's first day.

The mental model: a snapshot is a blueprint of a sub-account, not a photocopy of it.

Snapshot vs workflow vs template vs cloning a sub-account

Agency owners mix these up constantly, so here's the split.

A workflow is one automation: a trigger, some actions, some conditions, inside one sub-account. HighLevel does let you copy a single workflow to another sub-account without a snapshot (the Copy to Sub-Account option), and it brings tags, custom fields, custom values, pipelines, and text templates with it. Anything else the workflow referenced gets stripped, and it lands as a draft. Fine for one automation. Not fine for a system of twelve that share forms, calendars, and a pipeline.

A template is a starting point for one asset type: an email template, a funnel template, a workflow recipe. It lives inside a sub-account and produces one thing. A snapshot is the container that can carry dozens of templates at once, plus the dependencies between them.

A cloned sub-account is the thing people actually want and GHL doesn't offer as a single button. The closest move is Account Snapshots, then the Create New Account (+) button beside a snapshot, which spins up a fresh sub-account with that snapshot already loaded. It's a structure clone. If you need the contacts too, it's a snapshot plus a contact export and import, and there's no shortcut.

So: a workflow is one automation, a template is one asset, a snapshot is the packaged set with its wiring intact, and a "clone" is a snapshot loaded into a new sub-account.

Where snapshots come from

There are three sources, and they all end up in the same place: Agency View, then Account Snapshots.

Ones you build. Click Create New Snapshot, give it a descriptive name, pick the source sub-account, then Select All or expand each category and tick specific items. Click Create. Most agencies keep a clean master sub-account that exists only to be snapshotted, so nothing client-specific leaks into the file.

Ones someone shares with you. Share links come in six flavors: permanent (reusable), one-time, email (single use, sent to an address), agency-restricted (tied to a partner agency's relationship number), sub-account restricted, and the marketplace share link. To import any of them, stay logged into HighLevel, open a new tab, paste the link, and click "Yes! Import Now." The snapshot lands in your Imported Snapshots tab. HighLevel's sharing guide covers the link types in detail.

Ones you buy. Marketplace listings go through the Developer Portal, can be free, freemium, or paid (one-time, monthly, or yearly), and get a 7 to 10 day review before going live. Marketplace links turn on Assets Protected by default, which means you can load and use the workflows and funnels but can't re-share them or capture them into a snapshot of your own. Worth knowing before you buy something expecting to white-label and resell it. The full landscape of paid and free options is in the GoHighLevel snapshot marketplace post, and pricing, refunds, and vendor vetting are in GHL snapshots for sale.

Loading, customizing, and pushing updates

Loading into an existing client is where the real decisions happen. From Sub-Accounts, click the three-dot menu on the client, then Manage Client, then the blue Actions button, then Load Snapshot. Pick the snapshot, choose which assets to bring (all, by category, or item by item), and proceed. HighLevel then shows you every conflict between what's already in the sub-account and what's in the snapshot. For each one you pick Override (snapshot version wins) or Skip (keep what's there). Type "confirm" and it runs. Existing contacts and data stay untouched unless you chose Override on a matching asset, which the load snapshot guide spells out.

Customizing after the load is unrestricted. Everything that came in is now a normal asset in that sub-account: edit the custom values first, then branding, then calendar assignments, then run one workflow end to end with a test contact. Budget an hour. It's still a fraction of building from scratch.

Updates work in two steps. When you improve the master sub-account, go to Account Snapshots and hit Refresh on the snapshot. That creates a new version, and the Version History panel shows what was added, removed, or synced. Then Push Update lets you pick which of your sub-accounts get it and which specific assets to send. Two limits to remember: pushes only reach sub-accounts inside your own agency (anyone you shared a link with has to re-import), and you can deselect locations you've hand-customized so a push doesn't flatten them. The refresh and update guide has the click path.

On permissions, snapshots are an agency-level feature. Sub-account users never see them, and creating a sub-account from a snapshot needs Agency Admin access. Under Settings, then Team, each agency user has Snapshot Scopes (view, create, edit, share and import, push, refresh, delete) you can toggle individually, so a team member can build and refresh snapshots without being able to push or delete.

A worked example: the Brandblast social media snapshot

Here's what the exclusion list means for one specific offer. A snapshot can carry every structural piece of a free-content lead funnel: the landing page, the funnel page, the booking calendar, and the workflows that get a prospect to book a meeting and show up. The Brandblast snapshot packages exactly that. What no snapshot can carry is the content itself, because branded posts have to be produced fresh every week for every client, and a file you built once in March can't keep doing that. That's the seam Brandblast sits on. The app installs from the GHL App Marketplace, generates months of branded images, carousels, videos, and AI avatars per sub-account from the client's own brand assets, and pushes them into the Social Planner the snapshot's workflows already point at. The agency then closes the meeting on a monthly DFY retainer, $47 to $97/mo as a foot in the door or $200 to $400/mo when social is the core offer. The funnel mechanics are in the lead generation snapshot post, and the install path is on the snapshots pillar.