GoHighLevel Snapshots: Build, Sell & Deploy Guide (2026)

By Dr Priya Jaganathan, GoHighLevel Certified Admin · HL Growth Partner, Australia · Updated 24 July 2026 · 9 min read

On this page: What snapshots include and exclude · How to create and push a snapshot · Refreshing snapshots in existing sub-accounts · Packaging and selling snapshots · The build checklist · Deployment QA steps · Common mistakes to avoid · FAQ

GoHighLevel snapshots are the closest thing agencies have to a productised delivery system: build a sub-account once, capture it, and redeploy it for every new client in minutes rather than days. Done properly, a snapshot turns your onboarding from a forty-hour build into a two-hour configuration job. Done badly, it quietly ships broken automations, dead links and someone else's Calendly URL to a paying client.

I have built and deployed HighLevel snapshots for Australian agencies across real estate, dental, allied health and trades since 2022, and the difference between the agencies that scale and the ones that drown in delivery work is almost always snapshot discipline. This guide covers what actually transfers, how linked and one-time pushes behave, how to price and sell vertical snapshots, and the QA process I run before any client ever logs in.

What snapshots include — and what they deliberately leave out

A snapshot is an account-level export of a sub-account's configuration. When you load it into another sub-account, GoHighLevel copies the structure, not the data. That distinction matters more than anything else in this guide.

Assets that transfer

A snapshot carries across Workflows (including their triggers and internal actions), funnels and websites, pipelines and their stages, custom fields and custom values, tags, email and SMS templates, forms and surveys, calendars, membership products, and trigger links. Because custom fields and tags travel with the Workflows that reference them, a well-built snapshot arrives with its plumbing intact — a "New Lead" Workflow still points at the right pipeline stage and still applies the right tags on the other side.

Assets that never transfer

Snapshots exclude contacts, conversation history, Twilio or LeadConnector phone numbers and credentials, Mailgun and other email-sending domains, connected integrations (Google, Facebook, Stripe), team members and their calendars' availability, and API keys. Media files are also unreliable: assets stored in the media library sometimes carry over and sometimes need re-uploading, so never assume images in funnels arrived intact. In practice this means every deployment has a mandatory configuration layer — phone provisioning, domain and DNS, sending domain warm-up, and for Australian clients, sender ID and compliance settings that satisfy ACMA's rules on commercial electronic messages, plus A2P registration if you message US numbers. The full inclusion list is maintained in the official HighLevel help documentation, and it does shift a little as new features land, so re-check it each quarter.

How to create and push a snapshot

Creating the snapshot

From the agency view, go to Account Snapshots, choose Create New Snapshot, name it with a version number (for example Dental Reactivation v2.3), and select the source sub-account. GoHighLevel captures the sub-account's current state at that moment. Two habits pay off here. First, always build in a dedicated, clean master sub-account — never snapshot a live client account, because you will drag their custom values, test contacts' tags and half-finished experiments along for the ride. Second, version every capture. Snapshots are point-in-time; if you fix a Workflow in the master account next week, the old snapshot does not update itself.

Pushing: linked versus one-time

When you push a snapshot to sub-accounts you choose between a one-time push and a linked push, and the choice changes your maintenance model.

A one-time push copies the assets across once. The receiving sub-account is then fully independent — future changes to the snapshot do nothing. This is right for sold licences where the buyer owns and modifies their copy.

A linked push keeps the relationship alive: when you update the snapshot, you can push a refresh to every linked sub-account. This is the backbone of a SaaS-style agency, because one Workflow fix can roll out to fifty clients in an afternoon. The trade-off is responsibility — a careless refresh can overwrite client customisations, which is why the refresh process gets its own section below.

You can also share snapshots outside your agency via a one-time link, a permanent link, or directly to another agency's relationship number. One-time links are the safest default for paid distribution because they cannot be re-shared endlessly.

Refreshing and updating snapshots in existing sub-accounts

Refreshing is where most agencies get burned, so treat it as a controlled release, not a button-press. When you push an updated snapshot to an existing sub-account, GoHighLevel shows a review screen listing which assets are new, which have changed, and which exist in both places. You choose, asset by asset, whether to skip or overwrite.

My rules for safe refreshes: only ever refresh assets you are certain the client has not customised — if a client has edited a funnel, an overwrite destroys their work; push Workflow changes in a draft state where possible and re-publish after checking trigger conditions; never refresh during business hours for sub-accounts with live lead flow; and keep a changelog per snapshot version so you can tell a client exactly what changed and when. If a client has diverged heavily from the base snapshot, stop refreshing them entirely and manage their account manually — a hybrid state is worse than either extreme.

How agencies package and sell snapshots

Vertical snapshots beat generic ones

The snapshots that sell are vertical: a complete, niche-specific system with pre-written copy, industry pipelines and calendars that match how that business actually books work. A generic "agency starter" snapshot competes with hundreds of free ones; a real estate snapshot with appraisal-request funnels, vendor nurture Workflows and open-home follow-up sequences competes with almost nothing. The same logic applies to dental snapshots built around recall, reactivation and new-patient booking flows.

Pricing models compared

The one-off licence is the simplest revenue but the weakest: you earn once and inherit support questions forever unless your documentation is airtight. Setup-plus-retainer is where most Australian agencies should start, because the deployment work (Twilio provisioning, Mailgun domain setup, calendar configuration) genuinely justifies the setup fee. The SaaS Mode bundle is the scalable end-game — the snapshot loads automatically when a customer signs up, and linked refreshes keep every account current. If that model appeals, read my SaaS Mode setup and pricing guide before you build, because SaaS Mode requires the Agency Pro plan — check current tiers on the official GoHighLevel pricing page — and your snapshot architecture should anticipate feature-gating from day one.

The snapshot build checklist

Before capturing any snapshot, work through this list in the master sub-account:

• Naming conventions: prefix every Workflow, funnel and tag consistently (e.g. DEN-01 New Patient Intake) so buyers can navigate the account.
• Custom values everywhere: replace every hard-coded business name, phone number, booking link and address with custom values, so one settings page personalises the whole account.
• Workflows published deliberately: decide which Workflows ship live and which ship as drafts; anything that sends messages should arrive in draft.
• Pipelines and stages finalised: stage names should match the Workflows that move opportunities between them.
• Placeholder copy purged: read every email and SMS template aloud — test copy has a way of surviving into production.
• Calendars templated: ship calendar shells with sensible durations and buffers, knowing availability must be reset per deployment.
• Media audited: list every image used in funnels so you can verify them post-push.
• Test data removed: delete test contacts and opportunities from the master account; they will not transfer, but the tags and fields you created for testing will.

Deployment QA: the steps before a client logs in

Every snapshot deployment gets the same QA pass, whether it is a $500 licence or a SaaS signup. Push the snapshot, then: confirm all Workflows arrived and their triggers reference existing tags, pipelines and calendars (broken references fail silently); populate every custom value and search the account for any remaining placeholder text; provision and test the LeadConnector or Twilio number with a live inbound call and SMS; configure the Mailgun sending domain, verify DNS and send a test email to an external inbox; rebuild calendar availability and run a genuine test booking end to end, confirming the confirmation and reminder messages fire; click every funnel page on desktop and mobile and check every image loaded; and finally, submit a test lead through the main form and follow it through the entire pipeline. Only when the test lead has travelled from opt-in to booked appointment without manual intervention do I hand over credentials. Whether you run this QA yourself or delegate it, document it — I have written elsewhere about using VAs versus an in-house team for GHL implementation, and snapshot QA is the first process worth systemising either way.

Common mistakes to avoid

• Snapshotting a live client account instead of a clean master build, dragging their tags, custom values and experiments into every future deployment.
• Hard-coding business names, phone numbers and booking links instead of using custom values, forcing manual edits across dozens of assets per deployment.
• Shipping messaging Workflows in a published state, so half-configured accounts start texting real people before numbers and compliance are sorted.
• Refreshing linked snapshots without reviewing the overwrite screen, wiping out client customisations with no undo.
• Assuming media files transferred — broken hero images on a client's first login are entirely avoidable.
• Selling snapshots with no versioning or changelog, making support impossible once three variants are in the wild.

If you want a proven vertical snapshot built and deployed for your agency without the trial and error, book a strategy call with the HL Growth Partner team.

Book Your Strategy Call →

Frequently asked questions

Do GoHighLevel snapshots include contacts or conversation history?

No. Snapshots copy configuration only — Workflows, funnels, pipelines, custom fields, tags, templates, forms and calendars. Contacts, conversations, phone numbers, Mailgun domains and integration credentials never transfer, which is why every deployment needs a configuration pass after the push.

What is the difference between a linked and a one-time snapshot push?

A one-time push copies assets once and leaves the receiving sub-account independent. A linked push maintains a connection, so future snapshot updates can be pushed as refreshes to every linked sub-account. Use one-time pushes for sold licences and linked pushes for accounts you manage or run under SaaS Mode.

Can I update a snapshot after clients are already using it?

Yes, if the sub-accounts are linked. Update the master build, capture a new version, then push a refresh. GoHighLevel shows a review screen where you choose per asset whether to skip or overwrite, so you can ship fixes without destroying client customisations — provided you review it carefully.

How much can you sell a GoHighLevel snapshot for?

In the Australian market, one-off vertical snapshot licences typically sell for $500 to $3,000 AUD. Agencies deploying snapshots as a service usually charge $1,500 to $5,000 setup plus a monthly retainer, while SaaS Mode operators bundle the snapshot into subscriptions of roughly $97 to $697 per month.

Do snapshots carry over Twilio, Mailgun or A2P settings?

No. Telephony and email infrastructure is account-specific: each sub-account needs its own LeadConnector or Twilio number, its own Mailgun sending domain, and its own compliance setup — A2P 10DLC registration for US messaging, and ACMA-compliant sender identification and consent practices for Australian campaigns.