GoHighLevel Snapshots for Agencies: How to Build, Import and Sell Them (2026)
GoHighLevel Snapshots for Agencies: How to Build, Import and Sell Them (2026)
If you run a GoHighLevel agency and you are still building every client account from scratch, you are leaving margin on the table with every onboarding. Snapshots are GHL's native mechanism for packaging an entire sub-account build — workflows, pipelines, funnels, calendars, custom fields, email templates, the lot — into a reusable template you can deploy in minutes. Done well, a snapshot turns a 20-hour implementation into a two-hour configuration job. Done poorly, it clones half-finished automations and hard-coded client details into every new account, and you spend the next quarter cleaning up the mess.
I have built and maintained snapshots for Australian agencies across trades, fitness, allied health and professional services, and the difference between a snapshot that sells and one that embarrasses you comes down to discipline: what you put in it, how you name things, how you test it, and how you keep it current. This guide covers the full lifecycle — what snapshots actually capture (and what they do not), how to build a clean master, how to import and deploy into client sub-accounts, how to push updates without breaking live accounts, and the realistic ways agencies are selling snapshots in 2026.
What a snapshot is — and what it actually captures
A snapshot is a point-in-time copy of a sub-account's configuration, created at the agency level and importable into any other sub-account under your agency. Think of it as a template of the machinery, not the data. When you load a snapshot into a fresh sub-account, you get the structure of the build without any of the client-specific content that lived in the original.
What comes across
Snapshots capture the assets that make up your delivery system: Workflows (including triggers and actions), pipelines and their stages, funnels and websites, forms and surveys, calendars, email and SMS templates, custom fields, tags, custom values, trigger links, membership/course structures and Conversation AI bot configurations (prompts and intents, though you will still need to review and re-verify AI settings in each new account). Essentially, if it is something you built, it travels.
What does not come across
This is where most first-timers get caught. Snapshots do not include contacts, conversation history, appointment data or opportunity records — no client data moves, which is exactly what you want. They also do not carry over credentials and account-level integrations: Twilio or LeadConnector phone numbers and A2P registration, Mailgun or dedicated sending domains, connected Google/Outlook calendars, Facebook and Google Ads integrations, Stripe connections, and user accounts all have to be set up fresh in each sub-account. Workflows that reference a specific phone number or user will import, but the references break until you reconnect them. Plan your onboarding checklist around this gap — the snapshot gives you the skeleton, and integrations are the wiring job that follows.
How to build a clean master snapshot
Never snapshot a live client account and call it a product. Build a dedicated master sub-account whose only job is to be the source of truth for your snapshot. Here is the discipline that separates a sellable snapshot from a liability.
Use ruthless naming conventions
Everything in your master account should be named so a stranger can navigate it. I prefix workflows by function and number them: 01 — Lead Nurture — New Enquiry, 02 — Lead Nurture — No Answer Follow-Up, 90 — Internal — Task Notifications. Pipelines get plain-English stage names. Tags follow a consistent pattern (source:facebook, status:booked). When a client's VA opens the account in six months, the naming convention is your documentation.
Custom values instead of hard-coded details
This is the single biggest quality marker. Anywhere a business name, phone number, booking link, review link, address or offer price would appear — in an email template, SMS, funnel page or workflow message — use a custom value instead. Create a standard set ({{ custom_values.business_name }}, {{ custom_values.booking_link }}, {{ custom_values.main_offer }} and so on) and reference them everywhere. Deployment then becomes a 15-minute exercise of filling in one custom values screen rather than hunting through 40 assets for a hard-coded phone number that belongs to another client. If you take one thing from this article, take this.
Test in a fresh sub-account before every release
Before you deploy to a paying client, load the snapshot into a blank test sub-account and run it end to end: submit the lead form, watch the workflow fire, check the SMS merge fields render, book through the calendar, confirm the pipeline stage moves. Snapshots occasionally import with broken workflow references (a deleted user, a missing calendar), and you want to find those in a sandbox, not in a client demo. I keep a standing test sub-account and wipe it between releases.
Importing and deploying to client sub-accounts
Deployment happens from your agency view. When creating a new sub-account, you can load your snapshot at creation time; for existing accounts, you push it from the agency snapshot manager and choose whether to overwrite or skip assets that already exist. My standard deployment runbook looks like this: create the sub-account with the snapshot, complete the custom values screen, connect Twilio/LeadConnector and start A2P registration (this takes days in some cases, so do it first), configure Mailgun or the dedicated domain, connect the client's Google calendar to the GHL calendars, add users with the right permissions, then run the same end-to-end test you run in your sandbox. If you want a full task-level version of this, my 75-task GoHighLevel implementation checklist covers the entire onboarding sequence.
Keeping snapshots updated: push updates and versioning
A snapshot is not a one-and-done artefact — it is a product with a release cycle. GHL lets you refresh a snapshot from its source sub-account and then push updates to linked sub-accounts, either selectively (specific assets) or wholesale. Two rules keep this safe.
First, version deliberately. Update your master account, refresh the snapshot, and record a changelog — even a simple spreadsheet with a version number, date and list of changed assets. When something breaks in a client account after a push, the changelog tells you exactly what moved. Some agencies keep dated snapshot copies (Tradie Engine v2.3 — 2026-07) so they can roll back by re-importing an earlier version.
Second, push with care. A push update can overwrite client-side customisations — if a client tweaked an email template you later updated, your push clobbers their tweak. Push selectively, communicate before major updates, and never blanket-push to every linked sub-account on a Friday afternoon. Test the push on one low-risk account first.
How to sell snapshots
Snapshots stop being an internal efficiency and become a revenue line when you productise them. Three models dominate in 2026.
One-off licence
You sell the snapshot as a digital product — typically AUD $300 to $3,000 depending on depth and niche — delivered via a share link, sometimes with a setup video and documentation. Low touch, but buyers churn out of your world quickly unless you attach a community or update plan.
Bundled with a SaaS Mode subscription
This is where the real leverage sits. Under SaaS Mode you resell GHL sub-accounts under your own brand, and the snapshot becomes your onboarding engine: every new subscriber gets your build loaded automatically at signup. The snapshot is not the product — it is the reason your $297–$597/month subscription delivers value on day one. I cover the economics in detail in my guide to building recurring revenue with GHL SaaS Mode.
Marketplace and affiliate channels
HighLevel's marketplace and third-party snapshot stores let you list vertical snapshots for other agencies to buy. Margins are thinner and support expectations are real, but it is genuine passive-ish income if your snapshot is well documented.
Niche down: vertical beats generic
A generic "all-purpose agency snapshot" competes with a thousand free ones. A vertical snapshot — pipelines named for the trade, workflows written in the industry's language, Conversation AI prompts that know what a strata quote or a casual gym pass is — commands real money because it collapses the buyer's time to value. My tradies and home services snapshot exists precisely because a plumber's missed-call text-back and quote follow-up sequence looks nothing like a marketing agency's. Pick one vertical you know deeply, build for it, and let the specificity do the selling.
| Pricing model | Typical price (AUD) | Effort to deliver | Revenue type | Best for |
|---|---|---|---|---|
| One-off licence | $300–$3,000 | Low (docs + share link) | One-time | Agencies with an audience of other GHL users |
| Bundled with SaaS Mode subscription | $97–$597/month per client | Medium (onboarding + support) | Recurring | Agencies productising delivery in one vertical |
| Marketplace listing | $100–$1,500 less platform fees | Low–medium (ongoing updates expected) | One-time, volume-driven | Well-documented vertical snapshots |
| Snapshot + done-for-you setup | $1,500–$7,500 project fee | High (full implementation) | One-time, high margin | Premium niches and complex builds |
Common mistakes to avoid
- Snapshotting a live client account, so real names, phone numbers and half-finished experiments ship inside your "product".
- Hard-coding business details in templates and workflows instead of using custom values, turning every deployment into a search-and-replace exercise.
- Assuming integrations travel — Twilio/LeadConnector numbers, A2P registration, Mailgun domains, calendar and payment connections must all be rebuilt per sub-account.
- Pushing snapshot updates to all linked sub-accounts at once without testing, overwriting client customisations in the process.
- Skipping the fresh sub-account test, so broken workflow references and missing calendar links surface in front of the client.
- Building one bloated generic snapshot instead of lean vertical ones — buyers pay for relevance, not asset count.
If you want a battle-tested snapshot built for your niche — or help productising your agency's delivery with snapshots and SaaS Mode — book a strategy call with the HL Growth Partner team.
Frequently asked questions
Do GoHighLevel snapshots include contacts and conversation history?
No. Snapshots copy configuration only — workflows, pipelines, funnels, calendars, custom fields, tags, custom values and templates. Contacts, conversations, appointments and opportunity records never transfer, which protects client data and means you can safely snapshot a working build without moving anyone's CRM data.
Will my Twilio and Mailgun settings carry over in a snapshot?
No. Phone numbers, A2P registration, Twilio/LeadConnector configuration, Mailgun and dedicated sending domains, connected calendars, ad accounts and payment integrations are all account-level credentials that must be set up fresh in each sub-account. Start A2P registration early in onboarding, as approval can take days.
Can I update a snapshot after clients have already imported it?
Yes. Refresh the snapshot from your master sub-account, then use push updates to send changes to linked sub-accounts, either selectively or in full. Push carefully, though — updates can overwrite customisations clients have made, so test on one account first and keep a version changelog.
How much can an agency charge for a GoHighLevel snapshot?
One-off licences typically sell for AUD $300–$3,000 depending on depth and niche. Bundled with a SaaS Mode subscription, the snapshot underpins recurring plans of roughly $97–$597 per month. Snapshot-plus-setup projects for premium verticals commonly run $1,500–$7,500.
Should I build one generic snapshot or several vertical ones?
Vertical snapshots almost always outperform generic ones commercially. A snapshot built for one industry — with pipelines, workflow copy and Conversation AI prompts in that industry's language — deploys faster, demos better and commands higher prices than an all-purpose build competing with free alternatives.
