Anis Mahmud Anik

GoHighLevel Snapshots: Copy a Finished Setup to a New Sub-Account

A finished account setup copied into a new sub-account, representing GoHighLevel snapshots.

Short answer

A snapshot is a reusable template that captures selected configuration from a finished sub-account so it can be copied into a new or existing sub-account. You do not build a snapshot from scratch. First configure the source sub-account with the assets you want to reuse, then create the snapshot from that account. Workflows, funnels, calendars, forms, pipelines, and more copy across. Contacts, appointments, conversations, and history do not. A snapshot does not update on its own; refresh it to capture changes from the source.

In this post

  • What a snapshot is, and what it is not
  • How to create a snapshot in five steps
  • What copies, and what does not
  • How to load a snapshot into a sub-account
  • How to share a snapshot with another agency
  • Snapshot or build from scratch: how to decide
  • How to keep a snapshot current
  • What it cannot do
  • FAQ
  • Sources

What a snapshot is, and what it is not

HighLevel’s Help Center defines 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.” The key word is configuration. A snapshot copies how the account is set up. It does not copy what happened in the account.

That distinction is the whole point. A snapshot is how a proven setup gets reused: one finished build becomes the starting point for the next client, instead of rebuilding the same workflows, funnels, and pipelines by hand each time.

A snapshot is not a backup. It does not carry contacts, appointments, conversations, or history. If you load a snapshot expecting the old account’s data to come with it, you will be disappointed. Load it expecting the old account’s setup, and it does what it says.

How to create a snapshot in five steps

  1. Configure the source sub-account first, with the assets and settings you want to reuse. A snapshot captures what is there, so finish the build before you capture it.
  2. Go to Agency View, then Account Snapshots.
  3. Select Create New Snapshot.
  4. Name the snapshot and select the source sub-account.
  5. Choose the assets to include, either Select All or per category, then select Create. Company custom fields can be included.

Name the snapshot for what it is, not for the client it came from. Onboarding template - service business tells the next user what it contains. A client name tells the next user nothing.

What copies, and what does not

What copies, per the Help Center article: workflows, funnels, calendars, forms, pipelines, custom fields, custom objects, custom values, tags, smart lists, dashboards, email templates, blogs, surveys, WhatsApp templates, Voice AI agents, Brand Voice, documents, memberships, and more. The full list is on the Help Center page.

Smart Lists copy as configurations, not as the contacts they show.

Some copied assets need post-load setup. WhatsApp templates need approval. Voice AI agents need a phone number assigned. Domains, plugins, and licenses may need updating for the new account. Budget time for that after the load, or the new account will look finished and behave half-finished.

What does not transfer: contacts, appointments, conversations and history, messages, reputation data, live account activity, Stripe connections, integrations, LinkedIn Lead Gen Forms, assigned phone numbers for Voice AI, private dashboards, contact-to-contact associations, and assets protected by another creator. Plan for each one that matters. A Stripe connection, for example, must be set up fresh in the new account; it will not arrive with the snapshot.

How to load a snapshot into a sub-account

Loading applies a snapshot to a sub-account. Choose the assets to load, and for each conflicting asset choose whether to override it or skip it. Loading does not delete contacts or existing data unless you choose to override a conflicting asset. Overriding is the one choice that changes existing data, so read it before you click it.

There are three ways a snapshot reaches an account:

  • Load it into an existing sub-account, choosing assets and handling conflicts as above.
  • Create a new sub-account from a snapshot, which applies the selected snapshot during setup.
  • Import a shared snapshot into the agency library, then load it from there.

Before you load into an existing account, check what is already there. An existing workflow with the same name is a conflict waiting to happen. Override it only if you are sure the snapshot version is the one to keep. When in doubt, skip it and compare the two versions by hand.

How to share a snapshot with another agency

Sharing, importing, and loading are three different actions. To share, go to Agency View, then Account Snapshots, then My Snapshots, open the actions menu on the snapshot, and select Share Snapshot. You need the Share/Import Snapshots permission. HighLevel offers six link types: Permanent, One-Time, Email, Agency-Restricted, Sub-Account Restricted, and Marketplace. A Permanent link can be reused for repeated imports. A One-Time link covers a single successful import, so generate a new one for each recipient.

If you turn on Assets Protected, the assets stay protected after import. The recipient can reuse them within their agency but cannot redistribute or resell them. External agencies do not receive snapshot updates automatically. Refresh the snapshot, then generate a new share.

Snapshot or build from scratch: how to decide

Use a snapshot when the setup is proven and the next account needs most of it. A standard client onboarding template, a vertical-specific template, or a SaaS offer with a prebuilt template are the cases the Help Center article lists. If most of the build is the same as the last one, a snapshot saves most of the work and leaves the differences to adjust.

Build from scratch when the setup is new, unproven, or mostly different. Capturing a half-finished account into a snapshot freezes its mistakes and spreads them to every account that loads it. A snapshot is only as good as its source account, so the source account has to be finished, tested, and worth copying first.

How to keep a snapshot current

Snapshots do not update automatically. When the source sub-account changes, the snapshot still holds the old version until you refresh it. Refresh updates the snapshot from the source, and you can push updates to linked sub-accounts.

That makes refresh a routine, not a one-off. After any change to the source build, refresh the snapshot, then check which linked accounts need the push. A snapshot that is three months behind its source is worse than no snapshot: it looks like the current setup and is not.

What it cannot do

  • It cannot copy contacts, appointments, conversations, history, messages, or reputation data. Those stay in the source account.
  • It cannot copy Stripe connections or integrations. Set those up in the new account.
  • It cannot update itself. Refresh it, or it goes stale.
  • It cannot protect you from a bad source account. A snapshot of a broken build is a broken build, copied faster.
  • Loading does not change existing data unless you choose to override a conflicting asset. The article does not say whether an override can be undone, so test a load on a copy before you override anything that matters.

FAQ

What is a GoHighLevel snapshot?
A reusable template that captures selected configuration assets from a sub-account so they can be copied into new or existing sub-accounts.

Do I build a snapshot from scratch?
No. First configure the source sub-account with the assets you want to reuse, then create the snapshot from that account.

What copies in a snapshot?
Workflows, funnels, calendars, forms, pipelines, custom fields and objects, tags, smart lists, dashboards, email templates, blogs, surveys, WhatsApp templates, Voice AI agents, Brand Voice, documents, memberships, and more. Some need post-load setup, such as WhatsApp approval and phone number assignment for Voice AI.

What does not copy?
Contacts, appointments, conversations and history, messages, reputation data, live account activity, Stripe connections, integrations, LinkedIn Lead Gen Forms, assigned phone numbers for Voice AI, private dashboards, contact-to-contact associations, and assets protected by another creator.

Does loading a snapshot delete data in the target account?
No, unless you choose to override a conflicting asset. Loading does not delete contacts or existing data on its own.

Do snapshots update automatically?
No. Refresh the snapshot to capture changes from the source, and push updates to linked sub-accounts when they need them.

Do other agencies get updates to a shared snapshot automatically?
No. External agencies do not receive snapshot updates automatically. Refresh the snapshot and generate a new share.

Can I reuse one snapshot across sub-accounts?
Yes. A snapshot can be reused across sub-accounts, which is the point: one proven setup, loaded wherever it fits.

Need a finished setup you can reuse for every client?

If every new client means rebuilding the same workflows, funnels, and pipelines from zero, book a free 30-minute call. The first step is looking at which parts of your build are worth capturing as a snapshot.

Sources

Checked 2026-11-12. All GHL behaviour in this post comes from these sources, not from memory.

  • HighLevel Help Center, “HighLevel Snapshots Overview: Copy Account Assets Fast” (modified 9 Oct 2026). https://help.gohighlevel.com/support/solutions/articles/48000982511
  • HighLevel Help Center, “How to Share Snapshots” (modified 12 Sep 2026). https://help.gohighlevel.com/support/solutions/articles/48000982513-how-to-share-snapshots

Related reading