GoHighLevel snapshots: what they are and when to use one

A GoHighLevel snapshot is a reusable template that copies an account’s setup (workflows, pipelines, funnels, forms, calendars and custom fields) from one sub-account into another (checked Oct 26, 2026 on help.gohighlevel.com). It copies configuration, never contacts or data. GoHighLevel snapshots save agencies time on their own repeat builds, but a bought snapshot rarely fits a business’s real sales process.

What is a GoHighLevel snapshot?

A GoHighLevel snapshot is a saved copy of selected setup assets from one sub-account, which an agency can load into other sub-accounts. HighLevel describes snapshots as “reusable templates that capture selected configuration assets from a HighLevel sub-account.” They live at the agency level, under Account Snapshots, and can be shared with other agencies through a link.

What does a snapshot include, and what doesn’t it copy?

A snapshot can include most of the setup in a sub-account, grouped into six categories. It doesn’t copy any live data or account connections. This is HighLevel’s list as of October 26, 2026:

Not copied: contacts, appointments, conversations, messages, reputation data and account history; Stripe and other third-party connections; phone numbers assigned to Voice AI agents; LinkedIn lead gen forms; private dashboards; contact-to-contact associations; and assets the original creator protected.

Some copied assets still need work after loading. HighLevel’s help center notes that WhatsApp templates need a WhatsApp integration and Meta approval, Voice AI agents need a phone number assigned, and WordPress plugin or theme licenses may need to be re-authorized. Smart lists copy as filters only and run against the new sub-account’s contacts.

How do you create and load a GoHighLevel snapshot?

You create a snapshot from a finished sub-account in the agency view, then load it into a new or existing sub-account. These are the steps from HighLevel’s help center (checked Oct 26, 2026 on help.gohighlevel.com):

1. Create it. Go to Agency View > Account Snapshots and click + Create New Snapshot. Name it, pick the source sub-account, select the assets (or Select All) and click Create.
2. Share it (optional). Generate a share link. HighLevel offers reusable, one-time, email, agency-restricted, sub-account-restricted and Marketplace links.
3. Import a shared snapshot. Opening a share link adds the snapshot to your agency’s library. Importing doesn’t change any sub-account yet.
4. Load it. Either create a new sub-account from the snapshot, or load it into an existing sub-account. When loading into an existing one, choose the assets, review the conflicts, and override or skip each conflicting asset.
5. Keep it current. Snapshots don’t update on their own. Refresh the snapshot to capture changes from the source sub-account, then push the refreshed assets to linked sub-accounts.

Should you buy a snapshot or build from scratch?

For a business, build from scratch. A snapshot copies someone else’s sales process, and no two businesses sell the same way. Even two med spas doing the same revenue have different sales processes, different ways of working and different results. A snapshot built for one gets bent to fit the other, and the bending is where accounts break.

That’s why The GoHighLevel Experts never uses snapshots. Every account starts with a discovery call and a map of the client’s real sales process and customer journey on a Miro board, and the workflows, pipelines and integrations are built from that map. After around 200 GoHighLevel accounts set up, migrated or audited, founder Khyatt puts it plainly: “It is a big mess-up to use generalizations and standardized snapshots. Each business needs a system that is customized and tailored to its own processes, its own culture and its own way of doing things.”

Snapshots do have a fair use: an agency copying its own proven build across its own clients. If an agency has built, tested and run one system for many similar clients, a snapshot saves it from rebuilding the same assets each time. The agency knows every workflow in it, because it wrote them. Agencies that want that build done for them under their own brand can use our white label GoHighLevel service.

Why do imported snapshots break accounts?

Imported snapshots break accounts because they bring assets that don’t match how the business works, and nobody in the business knows what they all do. These are the problems the team finds most often when auditing accounts built on a snapshot:

• Unfinished imports. Workflows were loaded but never adapted: placeholder text, wrong sender names, custom values still set to the seller’s details.
• Workflows that don’t fit the sales process. Triggers fire on tags or pipeline stages the business doesn’t use, so leads get the wrong messages or none at all.
• Duplicate assets. Loading a snapshot on top of an existing build creates second copies of pipelines, fields and workflows, and two workflows end up messaging the same lead.
• Connections that never came across. Stripe, phone numbers for Voice AI and third-party integrations aren’t in the snapshot, so steps that rely on them fail quietly.
• No naming or structure. Dozens of imported workflows with the seller’s names make every problem slow to find.

If your account was built from a snapshot and things misfire, a GoHighLevel audit finds what’s broken, dead or duplicated. A GoHighLevel setup rebuilds it around your own process, and ongoing support keeps it clean. Prices are on the pricing page. If you’re comparing who to hire, read how to hire a GoHighLevel expert.

For the wider view of what GoHighLevel does well and where it trips people up, read our GoHighLevel review.

Sources

• HighLevel help center, Snapshots - Overview (checked Oct 26, 2026)