Back to Blog
GoHighLevelNovember 10, 2026

GoHighLevel Snapshots Explained: What Agencies Should Include

A GoHighLevel snapshot copies funnels, workflows, calendars and CRM setup between sub-accounts. Here is what it includes, what it leaves out, and what to add.

GoHighLevel Snapshots Explained: What Agencies Should Include

A GoHighLevel snapshot is a reusable template that copies the setup of one sub-account, such as its funnels, workflows, calendars, pipelines and custom fields, into new or existing sub-accounts. It does not copy customer records or live activity, so contacts, conversations, appointments and integrations such as Stripe stay behind. Agencies should build each snapshot around one repeatable client offer and include every asset needed to launch it, plus clear notes on what the client must connect after loading.

This guide explains what HighLevel's own help documentation says snapshots contain, what they leave out, and how sharing and updates work. It ends with a practical checklist you can use before you build your next one.

What is a GoHighLevel snapshot?

HighLevel describes snapshots as "reusable templates that capture selected configuration assets from a HighLevel sub-account so they can be copied into new or existing sub-accounts" (HighLevel Support: Snapshots Overview). In other words, it is a copy of how an account is built, not of who is inside it.

You do not build a snapshot directly. HighLevel's guide says "You don't 'build' a snapshot directly": you set up a sub-account first, then capture it from Account Snapshots in Agency View (HighLevel Support: Create Snapshots). The source sub-account is effectively your master template.

For agencies, this is what makes a niche offer repeatable. If you sell the same lead-capture and follow-up system to ten dentists or ten real estate teams, a snapshot lets you set up account number ten the same way as account number one. If you are new to the reseller model, our guide on what white label GoHighLevel is covers the basics.

What does a snapshot include?

HighLevel's overview groups the assets a snapshot can carry into categories (HighLevel Support: Snapshots Overview). The main ones are:

  • Advertising: Google, LinkedIn and Meta ad campaigns.
  • AI and automation: Agent Studio, Brand Voice, Conversation AI, Voice AI Agents, workflows and triggers.
  • Calendars and services: calendars, calendar groups, services, add-ons, categories and resources.
  • CRM structure: custom fields (including company custom fields), custom objects, custom values, pipelines, tags, trigger links and smart lists.
  • Marketing and content: blogs, campaigns, email builder templates, forms, funnels and websites, quizzes, section templates, social planner, surveys, and text and email templates.
  • Reporting: custom metrics, custom reports and dashboards.
  • Memberships: certificates, membership offers and products, and webinars.
  • Brand and documents: brand colours, design kit, documents and contracts, folders and knowledge bases.
  • Other: review settings, WhatsApp templates and WordPress sites.

When you create a snapshot, you can use Select All or expand each category and pick individual items (HighLevel Support: Create Snapshots). The same article notes that CRM object associations carry over automatically only when both objects in the relationship are selected.

What does a snapshot not include?

HighLevel states that snapshots are "designed to transfer configuration and selected reusable assets, not live account activity or customer records" (HighLevel Support: Snapshots Overview). Smart lists are a good example: the snapshot carries the list's filter setup, not the contacts it shows.

Some items are listed as not transferring at all. Others transfer but need extra setup before they work, such as WhatsApp templates that need an approved WhatsApp integration, or Voice AI Agents that need a phone number assigned.

Included vs not included: quick reference table

The table below only lists items that HighLevel's help articles mention by name.

Item Copied by a snapshot? Notes from HighLevel's docs
Funnels and websites Yes Listed under marketing and content
Workflows and triggers Yes Listed under AI and automation
Calendars, services, calendar groups Yes Listed under calendars and services
Pipelines, tags, custom fields, custom values Yes Listed under CRM structure
Forms, surveys, quizzes Yes Listed under marketing and content
Email and text templates Yes Listed under marketing and content
Custom reports and dashboards Yes Private dashboards are excluded
Smart lists Configuration only Records shown in the list do not transfer
Membership offers, products, webinars Yes Listed under memberships
Google, LinkedIn and Meta ad campaigns Yes LinkedIn Lead Gen Forms are excluded
WhatsApp templates Yes, with setup Need WhatsApp integration and Meta approval
Voice AI Agents Yes, with setup Assigned phone numbers do not transfer
WordPress site Yes, with setup Third-party plugin or theme licences may need re-authentication
Contacts No Customer records are not copied
Conversations and messages No Including conversation history
Appointments No Live activity is not copied
Reputation data No Review settings do copy
Stripe and third-party integrations No Must be reconnected in each sub-account
Contact-to-contact associations No Not supported
Assets protected by another creator No Held back by Assets Protection settings

Sources: Snapshots Overview and Create Snapshots.

What should agencies include in a snapshot?

The right contents depend on the offer you sell, but most client-ready snapshots share the same building blocks. Use this checklist when you build or review your master sub-account.

Snapshot checklist

Structure and data model

  • One or more pipelines with stages that match the client's sales process
  • Custom fields for every piece of data your forms and workflows collect
  • Custom values for business name, phone, address, booking links and other details that change per client
  • A clear tag naming system (for example, source tags and status tags)
  • Smart lists for the segments your team or client will check often

Lead capture

  • Funnel or website pages for the core offer
  • Forms, surveys or quizzes connected to the right custom fields
  • Trigger links for tracked calls to action in emails and texts

Follow-up and automation

  • Workflows for new lead follow-up, appointment reminders, no-show recovery and review requests
  • Email and text templates used by those workflows
  • Calendars, calendar groups and services, with sensible default availability

AI and conversations (if part of your offer)

  • Conversation AI or Voice AI Agent setup, with a note that a phone number must be assigned after loading
  • Knowledge bases the AI agents rely on
  • Brand Voice settings

Reporting and handover

  • Shared (not private) dashboards and custom reports
  • Documents and contract templates the client will send
  • Brand colours and design kit set to neutral defaults you can restyle per client

Post-load notes (kept outside the snapshot)

  • A list of integrations to reconnect: Stripe, phone numbers, WhatsApp, domains and any third-party tools
  • A list of custom values to fill in for each new client
  • Any WordPress plugin or theme licences to re-authenticate

That last group matters most in practice. Because integrations, phone numbers and customer data never travel with a snapshot, a short onboarding checklist saves your team from chasing broken automations after launch.

What should agencies leave out?

Leave out anything that belongs to one specific client. Test contacts, sample conversations and real customer data will not copy anyway, but client-specific copy, logos and offers can, and they will need cleaning up in every account that loads them.

Custom values are the main tool for keeping a snapshot generic. If your funnels, emails and workflows reference custom values instead of hard-coded names and numbers, each new client only needs those values updated. Keep the master sub-account free of one-off experiments, since anything you select goes into every account that loads the snapshot.

How do snapshot sharing links work?

HighLevel lists several share link types (HighLevel Support: How to Share Snapshots):

Link type Who can import it
Permanent link Anyone with the active URL; reusable for repeated imports
One-time link Intended for a single successful import
Email link The intended email recipient
Agency-restricted link Only agencies whose relationship numbers are specified
Sub-account restricted link Only the designated sub-account
Marketplace share link Eligible buyers through the App Marketplace listing

The recipient first imports the snapshot into their agency's snapshot library, then loads it into a sub-account as a separate step. If Assets Protection is enabled, recipients can reuse protected assets in their own sub-accounts but cannot re-share or resell them to another agency (HighLevel Support: How to Share Snapshots).

For agencies, the restricted link types are usually the safer choice when sending a snapshot to one partner or client. A permanent link works for anyone who has the URL, so it suits public or marketplace-style distribution better than private client work.

How do snapshot updates and pushes work?

Snapshots do not update themselves. HighLevel's refresh guide says "your existing snapshot does not update automatically," so after changing the source sub-account you click Refresh on the snapshot and pick the new or changed assets to include (HighLevel Support: Refresh or Update Snapshots). Each successful refresh is recorded as a new version you can review, but version management "does not include a built-in revert/restore action" (HighLevel Support: Snapshot Version Management).

To send those changes to sub-accounts that already loaded the snapshot, you use Push Updates. HighLevel's process is (HighLevel Support: Pushing & Loading Snapshot Updates):

  1. In Agency View, open Account Snapshots.
  2. Refresh the snapshot so it includes the latest changes.
  3. Click the Push Updates icon next to the snapshot and confirm.
  4. Select the sub-accounts to update.
  5. Choose which assets to push, such as workflows, funnels or forms.

Pushing has rules agencies need to know before they use it on live clients. According to the same article, snapshot-created assets are overwritten with the latest version, manual edits to those assets are reverted if included in the push, items the user duplicated are not touched, and custom values are never edited or deleted.

Two more limits are worth noting. Only sub-accounts that previously loaded the snapshot can receive pushes, and external agencies cannot receive them at all; they must import a new share link (HighLevel Support: How to Share Snapshots). Also, if a refresh removes steps from a workflow, such as a wait step, HighLevel removes the contacts waiting on that step and logs it as "Removed by - Snapshot Refresh" (HighLevel Support: Refresh or Update Snapshots).

How to protect client customisations

HighLevel's recommended approach is to duplicate an asset before the client edits it, have the client work on the copy, and point connected automations to that copy. The copy "is not tracked by the snapshot and will remain untouched during updates" (HighLevel Support: Pushing & Loading Snapshot Updates).

A simple house rule helps here: core automations stay snapshot-managed, and anything a client wants to personalise gets duplicated first.

How does this look in a real agency project?

Mutant Technologies builds GoHighLevel systems for agencies as a white label partner, with 100+ funnels built, 250+ active automations and 50+ CRM setups for agencies in 15+ countries. In one project, we delivered 8 real estate funnels and full CRM automation for an agency in 14 days, which helped the agency keep a client worth $5k per month.

Work like that is where a well-planned snapshot pays off. Once the funnels, pipelines and workflows are built and tested in one master account, the same structure can be loaded for the next client in the niche instead of being rebuilt by hand. Our white label GoHighLevel service handles this kind of build, with CRM setup in as little as 48 hours, a typical 48-72 hour turnaround on GoHighLevel tasks, and a signed NDA and non-compete.

If you are weighing whether to build this in-house, our comparison of white label GoHighLevel vs an in-house developer and our post on how white label GoHighLevel helps agencies scale cover the trade-offs.

Frequently asked questions

Does a GoHighLevel snapshot copy contacts?

No. HighLevel's overview lists contacts, appointments, conversations and messages among the items that do not transfer. Smart lists copy their filter setup only, not the records.

Do I need to reconnect Stripe and phone numbers after loading a snapshot?

Yes. Stripe connections and third-party integrations are not copied, and Voice AI Agents need a phone number assigned in the new sub-account. WhatsApp templates also need an approved WhatsApp integration before they work.

Will updating my snapshot change my clients' accounts automatically?

No. You first refresh the snapshot, then use Push Updates to send selected assets to sub-accounts that previously loaded it. External agencies need to import a new share link instead.

Will a push overwrite my client's edits?

It can. HighLevel says manual edits to snapshot-created assets are reverted if those assets are included in the push. Duplicated assets and custom values are left alone, so duplicate anything a client customises.

Can I roll back to an older snapshot version?

HighLevel's version management records each successful refresh and shows what changed, but it does not include a built-in revert or restore action.

Which share link should I use for a single client?

A sub-account restricted or agency-restricted link limits who can import the snapshot. A one-time link is another option for a single import, while a permanent link works for anyone with the URL.

Need a snapshot built for your agency?

If you want a tested, client-ready GoHighLevel snapshot for your niche offer, our team can build it under your brand. Contact us or call +91 98798 46695 to talk through what your snapshot should include.

Did you enjoy this article?

Join the Mutation

Get the latest insights on digital innovation delivered straight to your inbox. No spam, ever.

Comments (0)