GoHighLevel Snapshots Explained: How to Build, Share and Update Them

GoHighLevel snapshots are reusable templates of a complete sub-account setup. Instead of rebuilding funnels, pipelines and workflows for every new client, an agency builds the system once, saves it as a snapshot and loads it into a new account in minutes. Done well, snapshots turn custom CRM work into a repeatable product. Done badly, they spread broken automations to every client at once.

What is included in a GoHighLevel snapshot?

A snapshot captures the assets of a sub-account, including:

• Funnels, websites and their pages

• Workflows and campaigns

• Pipelines and stages

• Calendars and their settings

• Forms, surveys and quizzes

• Email and SMS templates

• Custom fields, custom values and tags

• Trigger links

A snapshot does not carry over contacts, conversation history, phone numbers, connected integrations such as payment processors or Google accounts, or domain connections. Those must be set up in each new sub-account. Always check GoHighLevel's current documentation, since the included asset list evolves.

Common uses for snapshots

• Niche agencies packaging a proven setup, for example a dental or roofing lead system

• Multi-location brands giving every branch the same pipelines and reporting

• SaaS Mode resellers onboarding new customers automatically (see GoHighLevel SaaS Mode)

• Internal standardisation so every client starts with your best practices

How to build a snapshot that scales

Step 1: Build in a dedicated master sub-account

Create a clean sub-account used only for the template. Never build your snapshot from a live client account, because test contacts, client-specific text and old workflows will leak into every copy.

Step 2: Use custom values for anything client-specific

Business name, phone number, address, booking link and owner name should all be custom values, inserted with placeholders like {{custom_values.business_name}}. When the snapshot loads, the new client fills these in once and every funnel, email and text updates automatically.

Step 3: Name everything consistently

Use prefixes such as "WF | New Lead | Speed to Lead" for workflows and "PL | Sales" for pipelines. Clear naming makes support, handovers and updates far easier.

Step 4: Leave workflows in draft where needed

Workflows that send messages should be reviewed before they go live in a new account. Consider shipping them as drafts with a setup checklist.

Step 5: Write an onboarding checklist

List everything the snapshot cannot carry: connect the phone number, register A2P 10DLC, connect the domain, verify the email sending domain, connect calendars and payment providers, then fill custom values.

Mid-article CTA: Need a snapshot built for your niche? Book a free audit call and we will scope it with you.

Sharing and loading a snapshot

From the agency view you can create a share link for a snapshot and send it to another agency, or load it directly into a new or existing sub-account. When loading into an existing account, review conflicts carefully: assets with the same name can be overwritten or duplicated depending on the options you choose.

Pushing updates safely

GoHighLevel lets you push snapshot updates to sub-accounts that already use it. This is powerful and risky. Follow these rules:

1. Test every change in the master account first.

2. Push only the specific assets that changed, not the entire snapshot.

3. Warn clients if a workflow they customised might be overwritten.

4. Keep a changelog with the date, asset and reason for each update.

5. Push to one pilot account before rolling out to all accounts.

Snapshot mistakes to avoid

• Hard-coding a client's phone number or name in emails

• Including test contacts or test conversations in the master account

• Workflows that reference calendars or users that will not exist in the new account

• No documentation, so clients cannot tell what each workflow does

• Pushing an update that silently duplicates workflows and sends double messages

Frequently asked questions

Can I sell a GoHighLevel snapshot? Yes. Many agencies sell or license snapshots, and GoHighLevel has a marketplace for them. Make sure your snapshot includes setup documentation and support.

Do snapshots include contacts? No. Contacts and conversations are not transferred, which protects client data.

Can I update a snapshot after clients have installed it? Yes. You can edit the master account, refresh the snapshot and push selected changes to linked sub-accounts.

Will loading a snapshot delete existing assets? It can overwrite assets with matching names if you choose to. Review the import options and back up important workflows first.

Build snapshots your clients can rely on

Calari Solutions designs GoHighLevel snapshots with clean naming, custom values and documented workflows so they deploy in minutes and update without surprises. Schedule a free audit call to plan a snapshot for your agency or franchise.