What is a GoHighLevel snapshot?

A GoHighLevel snapshot is a package of a sub-account's configuration, made portable. You build a sub-account once — funnels, workflows, calendars, pipelines, forms, tags, custom values — take a snapshot of it, and then load that configuration into any other sub-account in about two minutes.

That is the whole idea. The useful detail is in the boundary: exactly what travels with a snapshot, and what stays behind. Nearly every problem people hit on a first import comes from an assumption about that boundary rather than from anything going wrong.

What is inside a snapshot

Configuration, not content. Concretely, a snapshot can carry:

• Funnels and websites — every step, every page, the layouts and the copy as built.
• Workflows and their triggers, including the branching logic and wait steps.
• Pipelines and their stages.
• Calendars, along with their settings and durations.
• Forms and surveys, including field mapping.
• Email and SMS templates.
• Custom fields, custom values and tags.
• Trigger links and campaigns.

Custom values are the quiet hero of that list. They are the placeholders — business name, phone number, offer price, calendar link, support address — that the pages and messages reference rather than hard-coding. A well-built snapshot lets you rebrand the entire system by editing a handful of custom values instead of opening forty pages. A badly built one has the business name typed directly into every email, and rebranding it is an afternoon.

What is not inside a snapshot

Everything that belongs to the account rather than to the build. This list is shorter and more important:

• Contacts and conversations. A snapshot never carries somebody else's data, which is the correct behaviour and also the answer to the most common question about them.
• Payment provider connections. Stripe, NMI or PayPal must be connected on the destination sub-account.
• Phone numbers and messaging registration. The receiving account needs its own number and its own registration.
• Email sending configuration and domain authentication.
• Calendar connections — the calendar comes across, your Google or Outlook account does not.
• Domains. The funnel arrives; pointing it at your domain is a step you do.
• Media library files, in most cases. Images referenced by pages generally need to be re-uploaded or re-linked.

Read that second list once before your first import and the twenty minutes of configuration afterwards will make sense rather than feeling like something is broken. The full configuration order is in how to import a snapshot.

What loading one does to an existing sub-account

It adds. Loading a snapshot does not delete your existing funnels, workflows or contacts. The risk is not destruction, it is collision: if your sub-account already has a workflow called "Nurture" and the snapshot brings one called "Nurture", you now have two, and in six weeks nobody will know which one is live.

Custom values are the exception worth watching, because a snapshot value with the same key as one you already use will win. If you are loading into an account that is already running, rename your own assets first, or load into a fresh sub-account and migrate deliberately.

Why snapshots exist

Two reasons, and they are different enough that they produce different snapshots.

The first is agency onboarding. An agency that signs a new client of a familiar type does not want to rebuild the same set of workflows for the fourth time. It builds them once, snapshots them, and loads them on day one of every new account. That snapshot is optimised for repeatability.

The second is distribution. Someone builds a complete system for a trade and sells it as a share link, so a business gets a week of build work for the price of a package. That snapshot is optimised for being handed to someone who did not build it — clean naming, custom values everywhere, documentation, and nothing left in a half-configured state.

The second kind is what we make. Every snapshot in our catalogue is one complete system for one trade, containing the same complete set of parts, written for that trade's day, and every price is listed on the pricing page rather than behind an enquiry form.

How a snapshot is delivered

As a share link. It looks like an ordinary GoHighLevel URL with a share parameter on the end, and opening it while logged in as the agency asks you where to load it. There is no file to download and nothing to install; the "download a GHL snapshot" phrasing you see in search results describes a thing that does not exist.

One consequence worth planning for: a snapshot cannot be cleanly un-loaded. There is no single undo. Load into a fresh sub-account the first time you try one, look at it, and only then decide where it should really live.

Snapshot, template, funnel — which is which

This distinction is the one that costs money. A funnel template is pages: attractive, and inert. The follow-up — the reply inside sixty seconds, the reminder ladder, the recovery call, the review request — is the part that produces revenue, and it only travels in a snapshot. If a listing is described as a funnel template and priced like one, assume you are buying pages and will be writing the workflows yourself.

We wrote the buying-decision version of this in the best GoHighLevel funnel templates, which covers which funnel shape a given offer needs before you go looking for anything to buy.

When a snapshot is the right call

When the system you need is a system many businesses of your type need, and the difference between yours and theirs is copy, branding and pricing rather than structure. That covers most local service businesses, most clinics, and most professional practices.

It is the wrong call when the process genuinely is unusual — a bespoke qualification flow, an integration with software specific to your industry, a compliance requirement that changes the sequence. In those cases you want a build, not a package, and the honest answer is often a snapshot as a base plus integration work on top.

Next steps

If you want to package one of your own builds, how to create a GoHighLevel snapshot covers the build-clean-export loop and the mistakes that make a snapshot unusable to anyone but its author. If you have bought one, how to import a snapshot is the checklist. And if something has already gone sideways, snapshot troubleshooting covers the eleven faults that account for nearly all of it.