GoHighLevel Snapshots: The Complete Guide plus the Best Snapshots by Industry

A GoHighLevel snapshot is a saved copy of a sub-account’s setup that you can load into another sub-account. Think of it as a moving box for your build: funnels, workflows, pipelines, calendars, forms and templates all go in. You load the box somewhere new, and most of the work is already done.

That is the promise. The catch is what stays behind, and what quietly breaks on the way. We build and repair snapshots for agencies, and most of the “this snapshot is broken” calls we get come from the same handful of gaps. This guide covers how snapshots work, what never makes the trip, how to push updates without hurting live clients, and what a good snapshot should hold for each industry.

Quick answer: A GoHighLevel snapshot is a template of a sub-account’s assets, like funnels, workflows, pipelines, calendars and forms, that you can load into new or existing sub-accounts. It does not copy contacts, conversations, phone setups, Stripe or other integrations. Plan to fill custom values, reconnect tools and test every workflow after loading.

What Is a GoHighLevel Snapshot?

A snapshot is a template you create from one sub-account and load into others. HighLevel’s own What is a Snapshot help article lists what can go inside: workflows and triggers, pipelines, custom fields, custom values, tags, calendars, forms, surveys, funnels and websites, email templates, dashboards, Conversation AI and Voice AI agents, knowledge bases, membership products and more.

Agencies use snapshots for three jobs:

  • Onboarding: load a niche build into every new client so you are not starting from a blank account.
  • Selling: package a build and sell or share it through a link or a marketplace.
  • Updating: fix something once in a master account, then push the fix to clients who already loaded it.

If you run a small business with one account, you may never need to create a snapshot. You may still load one that an agency or vendor gives you, so knowing the limits helps you spot a weak one.

What Does a Snapshot Not Copy?

A snapshot copies the structure of an account, not the life inside it. HighLevel lists these as items that do not transfer: contacts, appointments, conversations and message history, reputation data, Stripe connections, other integrations and third-party connections, phone numbers assigned to Voice AI agents, private dashboards and contact-to-contact associations.

In plain words, after you load a snapshot you still need to:

  1. Add or port a phone number and register A2P 10DLC before any texts go out. Our A2P 10DLC registration guide walks through it.
  2. Connect Stripe, Google, Facebook and any other apps again.
  3. Set up the email sending domain for that client.
  4. Import or sync the client’s real contacts.
  5. Fill in custom values with the client’s own details.

That last one surprises people the most, so it gets its own section.

The Custom Values Trap

Custom values hold things like the business name, phone number, booking link and review link. Good snapshots use them everywhere, so one change updates every email and text. Our older post on snapshot logic explains why.

Here is the part most guides skip. A snapshot brings over the custom value names and keys, but not the values themselves. On the HighLevel ideas board, a request to send custom value values through a snapshot has gathered about 79 votes and was still open when we checked. One user shared a workaround: build a workflow full of “update custom value” steps, then run a test contact through it. Another commenter pointed out that this breaks for merge fields, because they fill in with the test contact’s data.

Our fix is simpler. We ship every snapshot with a one-page “fill these first” sheet that lists each custom value and an example. The client or onboarding person fills them in before any workflow is turned on. Empty custom values are the top reason a new client gets a text that says “Hi, this is from .”

Trigger Links and Assigned Users Can Break

Two more things trip up agencies after a load or a push.

Trigger links. In a long-running ideas board thread about trigger links, users said the links do not update correctly when a workflow is copied into a new sub-account. The workaround shared there is to put the link in a custom value and have the client paste it in. We do the same, and we test every link in the new account.

Assigned users. A workflow step that assigns leads to a person points to a user in the source account. That user does not exist in the client account. Use the dynamic options in the Assign User action where you can, and check every assignment step after loading.

Overwrite or Skip? How to Load a Snapshot Into an Existing Account

Loading into a brand new sub-account is easy. Loading into an account that already has tags, fields and workflows is where messes start.

When there is a conflict, HighLevel asks whether to overwrite or skip. A request on the ideas board to map or merge fields and tags during import describes the pain well: you end up with near-duplicate fields and tags that take hours to clean.

Our rule of thumb:

SituationWhat we doWhy
Brand new sub-accountLoad everythingNothing to collide with
Live client, no custom workLoad only the folders you needFewer surprises
Live client with custom workflowsSkip conflicts, then rebuild by handOverwrite can wipe their edits
Client using a different field naming styleMap fields first on paperStops duplicate fields like “Phone 2”

Before any load into a live account, export the contact list and take screenshots of the key workflows. There is no undo button for a messy import.

How to Create, Load and Share a Snapshot

The steps live in Agency View under Account Snapshots. HighLevel now has an in-app onboarding guide for snapshots that shows tips the first time you open that screen, which helps new team members.

  1. Clean the source account. Delete test workflows, rename folders and replace hard-coded names, links and numbers with custom values.
  2. Create the snapshot. In Agency View, open Account Snapshots, choose Create New Snapshot and pick the source sub-account.
  3. Load it. Choose the snapshot when you create a new sub-account, or load it into an existing one and choose what to overwrite or skip.
  4. Share it if needed. Create a share link for another agency. You can protect assets so the other agency cannot copy them out.
  5. Test in a blank sub-account. Fill the form, book the calendar, reply STOP and miss a call. Fix what breaks before a client ever sees it.

One support article from a snapshot vendor notes that a load can sit on “loading” for 15 to 30 minutes. Wait, check you are in the right sub-account, then contact the seller if it still has not appeared.

How to Push Snapshot Updates Safely

Once clients have loaded your snapshot, you will want to send them fixes. HighLevel’s refresh and update guide explains the flow: refresh the snapshot from your master account, then use Push Update to send chosen assets to chosen sub-accounts. Updates only push to sub-accounts inside your own agency.

Two details in that article matter a lot:

  • If a refresh removes steps from a workflow, contacts waiting on those steps are removed from the workflow. The execution log shows “Removed by Snapshot Refresh.” A careless push can drop leads out of a live follow-up sequence.
  • If some assets fail during a refresh, the rest keep going, and you can retry only the failed ones.

HighLevel also keeps a version history after each successful refresh, showing what was added or removed. It does not have a restore button. So version history tells you what changed, but it will not roll anything back.

Our push checklist:

  • Push to one test sub-account first and run a test contact through it.
  • Never remove steps from a workflow that has contacts waiting. Build a new version, move new leads to it, and let the old one finish.
  • Push one asset type at a time, not “everything.”
  • Write a short change note for clients, so they know why a message changed.

The Best GoHighLevel Snapshots by Industry

There is no single best snapshot. The best one for you is the one that matches how your clients really sell, with honest notes about what still needs setup. One 2026 snapshot roundup lists paid options from about $97 to $997, and quality varies a lot.

Instead of naming vendors, here is what we think a strong snapshot for each industry should include, and the industry trap to check before you buy or build one.

IndustryMust-have assetsCheck before you trust it
Med spasConsult pipeline, deposit or card-on-file booking, rebooking reminders by treatment, review requestHealth details in texts. See our med spa setup
DentalNew patient follow-up, missed call text back, recall reactivation, review requestDoes not sync with practice software. See our dental setup
RoofingInspection booking, estimate follow-up, storm reactivation, review and referral asksText consent for storm lists
HVAC and plumbingMissed call text back, maintenance plan reminders, after-hours routingWho owns the schedule if you use a field service app
Real estateBuyer and seller pipelines, long-term nurture, showing remindersNurture length. Many leads take months
Coaches and consultantsApplication funnel, discovery call booking, course or community accessPayment and membership setup
Agencies (your own)Client onboarding, reporting dashboards, internal tasksOnly build after you have repeated the process a few times

A snapshot that claims to be “plug and play” for any of these should still come with a setup list. If it does not, expect to spend a day finding what is missing.

Should You Build, Buy or Hire Out a Snapshot?

Buy one if you want ideas fast and you are comfortable cleaning it up. Treat a bought snapshot like a starter home: good bones, but you will repaint.

Build your own if you have already set up the same niche three or more times. You know the real sales process, so your snapshot will fit better than a generic one.

Hire it out if your team is busy delivering and you want a tested, documented build that new staff can load. Our white-label GoHighLevel support team builds and maintains agency snapshots, and the agency guide covers how snapshots fit into a bigger growth plan. If you plan to resell the software, read our SaaS Mode guide too.

A Quick Post-Load Checklist

Print this and use it every time you load a snapshot:

  • All custom values filled with real client details
  • Phone number added, A2P registered, missed call text back tested
  • Email sending domain set up and tested to Gmail and Outlook
  • Stripe, Google and Facebook connected again
  • Every workflow trigger link and assign user step checked
  • Calendars set to the right time zone and team members
  • Test contact run through every published workflow
  • Old demo text, logos and links removed

Frequently Asked Questions

What is a snapshot in GoHighLevel?

A snapshot is a template of a sub-account’s setup, like funnels, workflows, pipelines, calendars, forms and templates. You create it from one sub-account and load it into new or existing sub-accounts, so you do not rebuild the same system for every client.

Does a GoHighLevel snapshot include contacts?

No. Snapshots do not copy contacts, appointments, conversations or message history. You import or sync contacts separately after the snapshot is loaded.

Do custom values transfer with a snapshot?

The custom value names and keys transfer, but the values do not. You need to fill in each value, like business name, phone and booking link, in the new sub-account before turning workflows on.

Can I load a snapshot into an existing sub-account?

Yes. When assets conflict, you choose to overwrite or skip. Overwriting can replace a client’s own edits, so export data and review conflicts before you load into a live account.

How do I update clients who already loaded my snapshot?

Refresh the snapshot from your master account, then use Push Update to send chosen assets to chosen sub-accounts in your agency. Test on one account first, because removing workflow steps can remove waiting contacts.

Can I undo a snapshot update?

Not with a single click. HighLevel keeps a version history that shows what was added or removed, but it does not offer a restore button. Keep backups and push carefully.

Are free GoHighLevel snapshots worth using?

They can be a good starting point for ideas. Expect to rename assets, fill custom values, fix links and test every workflow. Do not load a free snapshot into a live client account without testing it first.

How long does it take to build a custom snapshot?

A focused niche snapshot often takes one to three weeks to build and test. Bigger builds with AI agents, memberships or many workflows take longer. Most GHL Logic projects go live in 2 to 4 weeks.

The Bottom Line

Snapshots save real time, but only when you treat them as a starting point and not a finished product. Fill custom values first, reconnect what does not transfer, test like a customer, and push updates with care. Do that, and one good build can serve dozens of clients.

Want this done for you?

Our certified GoHighLevel experts can set it up for you, usually in 2 to 4 weeks with 30 days of free support. See our white-label GoHighLevel support service.

Book a Free Consultation

Similar Posts

Leave a Reply

Your email address will not be published. Required fields are marked *