GoHighLevelagencyautomationUnited States

GoHighLevel Snapshots: What They Copy and What They Miss

What a GoHighLevel snapshot includes and leaves out, how to create, share, load and refresh one, and the setup steps every new sub account still needs.

Workflow diagram on screen

A GoHighLevel snapshot is a saved copy of a sub account’s build (workflows, funnels, calendars, forms, pipelines, custom fields and more) that you can load into another sub account in minutes. Agencies use snapshots to launch every new client from a proven template instead of building from scratch. What a snapshot does not copy matters just as much: contacts, conversations, appointments, integrations, Stripe connections and phone numbers stay behind, so every new account still needs a short setup pass before it goes live.

This guide covers what is included, what is not, how to create, share and update snapshots, and the checklist we run after loading one.

What a snapshot includes

HighLevel’s snapshot creation article lists the asset types a snapshot can carry. The ones agencies rely on most:

  • Workflows and triggers, including the actions, waits and conditions inside them
  • Funnels and websites, with their pages and forms
  • Calendars and their settings
  • Forms and surveys
  • Email templates
  • Pipelines and stages
  • Custom fields and custom values
  • Tags
  • Membership content, services and webinars
  • AI assets such as Conversation AI and Voice AI configuration (phone numbers excluded, see below)
  • Custom objects with their fields and supported associations (custom objects article)

Custom values are the quiet hero here. If your workflows and funnel copy use custom values for the business name, phone number, booking link and service area, one edit per new client updates every page and message at once.

What a snapshot does not include

These stay behind, per the same HighLevel article and the related AI articles:

  • Contacts, and with them their tags, notes and history
  • Conversations and message history
  • Appointments already booked
  • Reputation data such as reviews
  • Stripe connections and other integrations (Google, Facebook, email providers)
  • Phone numbers. HighLevel notes that numbers are tied to a specific account and must be assigned after the snapshot is loaded (Voice AI snapshot article)
  • Lead gen forms from ad platforms
  • A2P 10DLC registration. Every US sub account that texts needs its own brand and campaign registration

A snapshot is a template, not a migration. If you need to move contacts, opportunities and history from another CRM, that is a migration project, and our migration checklist covers it.

How to create a snapshot

  1. Build and test the template in a dedicated sub account. Do not snapshot a live client account full of one off changes.
  2. In the agency view, open Account Snapshots and create a new snapshot from that sub account.
  3. Choose the assets to include. HighLevel lets you pick selected assets instead of everything.
  4. Name it with a version, such as “Roofing v3, Nov 2026”, so you know which build a client got.

How to load a snapshot

There are two ways:

  • When creating a sub account, choose the snapshot as the starting template (HighLevel article).
  • Into an existing sub account, load the snapshot and choose how to handle conflicts with assets that already exist. Be careful here: overwriting can replace workflows a client has edited.

Sharing and selling snapshots

You can share a snapshot with another agency by link. This is how snapshot marketplaces and “done for you” niche templates are delivered. If you buy one, treat it as a starting point: check every workflow trigger, every custom value and every message for compliance before going live. A snapshot built for one industry or country often has copy and texting habits that do not fit yours.

Updating a snapshot and pushing changes

When you improve the template, you refresh the snapshot. HighLevel’s snapshot refresh article notes that you cannot edit a snapshot’s content directly. You change the source sub account, then refresh the snapshot to pick up those changes.

You can then push updates to sub accounts that use it. Per HighLevel’s linked assets article, only enabled assets are pushed, and unlinking an asset affects future pushes only, not assets already deployed. Before you push, ask whether any client has customized the assets you are about to update. If yes, push only the assets that changed, or update those accounts by hand.

The setup pass every new account still needs

Loading a snapshot gets you 80% of the way. This is the checklist we run on every account after loading one:

  1. Fill custom values: business name, phone, address, booking link, review link, service area.
  2. Buy or port a phone number and assign it to calls, texts and any Voice AI agent.
  3. Register A2P 10DLC for US texting, or verify the toll free number. Our A2P guide walks through it, and the free A2P website checker tests the client’s site wording.
  4. Connect integrations: Google Business Profile, Facebook, Stripe, the email sending domain.
  5. Set up a dedicated email sending domain so messages do not land in spam (email deliverability service).
  6. Assign users and set calendar availability.
  7. Turn workflows on one at a time and test each from a real phone and inbox.
  8. Import contacts only after workflows are tested, so a bulk import does not trigger a flood of messages.

Step 8 is where most snapshot launches go wrong. A workflow triggered on “contact created” will fire for every imported contact unless you pause it first.

When a snapshot is worth building

A snapshot pays off once you have launched the same type of account two or three times. For agencies running SaaS mode, it is essential, because every self serve signup is created from a snapshot. If you are only setting up one business, you do not need one: build directly in the account.

We build custom snapshots for agencies and niche templates for single businesses as part of GoHighLevel setup and SaaS mode setup.

FAQ

Does a GoHighLevel snapshot copy contacts?

No. Snapshots copy the build (workflows, funnels, calendars, forms, fields and similar assets), not contacts, conversations or appointments. Moving contact data is a separate import or migration.

Do snapshots copy phone numbers or A2P registration?

No. Phone numbers must be bought or ported and assigned in each sub account, and each US sub account that texts needs its own A2P 10DLC registration or toll free verification.

Can I update clients after they load my snapshot?

Yes. Refresh the snapshot from the source account, then push the updated assets to sub accounts that use it. Push only what changed if clients have customized their accounts.

Can I sell a GoHighLevel snapshot?

Yes. Snapshots can be shared by link, and many agencies sell niche snapshots. Buyers should still review every workflow and message before going live.

What is the difference between a snapshot and a migration?

A snapshot copies a template build into a new account. A migration moves your real data (contacts, deals, history) from another CRM into GoHighLevel. Most projects need both: a snapshot or build for the system and a migration for the data.

Ready to move?

Book a 20 minute discovery call. Bring your current CRM. Leave with a fixed price and a delivery date.