Loading tutorials…
Loading tutorials…
Snapshots are how agencies scale GHL from 1 client to 50. Built right, you onboard a new client in 90 min instead of 8 hours. Built wrong, you overwrite a paying client's workflows and spend a Saturday restoring backups.
Who this is forAgencies running 3+ GHL sub-accounts who keep manually rebuilding the same workflows, funnels, and calendar configs each time. If you have spent 40+ hours total on repetitive sub-account setup, the snapshot system pays for itself in week one.
What you'll need
Step 1
Snapshots inherit everything from a source sub-account. If the source has junk, every cloned sub-account has the same junk. Build a dedicated "Master Template" sub-account.
In Agency View → Sub-Accounts → Create Sub-Account. Name it "AGENCY MASTER TEMPLATE — DO NOT DELETE." This sub-account exists only to be the source of snapshots — no real client data.
Configure it cleanly: 3-5 workflows representing your highest-value automations, 1-2 funnels, calendar group, email templates, SMS templates, custom fields, custom values, pipelines, tags.
Do NOT add contacts, opportunities, calendar appointments, or conversations. These are client-specific and will leak into every sub-account you deploy the snapshot to.
Test the source sub-account end-to-end — submit a form, fire a workflow, confirm everything works. If it is broken here, it will be broken everywhere.
Step 2
In Agency View → Snapshots → Create Snapshot. Select your MASTER TEMPLATE sub-account as the source. Name with a clear version (e.g., "Agency Master v1.0").
Click "Create New Snapshot." Choose the source: select MASTER TEMPLATE sub-account.
Name it with the format "[Agency Name] Master v[X.Y]" — e.g., "Acme Agency Master v1.0." Versioning matters as you iterate.
Select which assets to include: Workflows, Funnels, Websites, Email Templates, SMS Templates, Custom Fields, Custom Values, Pipelines, Tags, Calendars, Forms, Surveys. Default to including all of these.
EXCLUDE: Contacts (always), Opportunities (always), Conversations (always), Appointments (always). These are client data, not template data.
Click "Create." Snapshot generation takes 2-10 min depending on asset count.
Step 3
When creating a new sub-account, select your snapshot in the "Load Snapshot" dropdown. All template assets get cloned automatically.
Agency View → Sub-Accounts → Create Sub-Account. Fill in client name, timezone, etc.
Scroll to "Load Snapshot" dropdown. Select "Acme Agency Master v1.0."
Click "Create." GHL deploys the snapshot — typically 2-5 min for asset cloning.
Open the new sub-account. Verify workflows, funnels, templates all loaded. Check workflow trigger conditions — they sometimes need re-pointing at the new sub-account's forms or calendars.
Update sub-account-specific elements: business name in email signatures, calendar timezone, custom value defaults. Snapshots clone the structure; you fine-tune the client specifics.
Step 4
In the sub-account → Settings → Snapshots → Load Snapshot. Select your new version (v1.1). Critically: choose "Append" not "Overwrite."
When you release Master v1.1 with new workflows, you can push it to existing client sub-accounts.
Open the client sub-account → Settings → Snapshots → Load Snapshot.
Select the new version. GHL gives you two options: Append (adds new assets, leaves existing alone) or Overwrite (replaces same-named assets with new versions).
For 95% of cases use Append. Overwrite will wipe out any client-specific customizations made to that workflow or template.
After loading, manually review and remove duplicate workflows if Append created any (it sometimes does for similarly-named assets).
Step 5
Every snapshot revision gets a new version number (v1.1, v1.2, v2.0). Keep old versions for 90 days — gives you rollback if a new version breaks things.
Naming convention: v1.0 = initial release. v1.1 = bug fix or small addition. v2.0 = major restructure (new core workflows, new pipeline stages).
In Agency View → Snapshots, you can see all your snapshots. Don't delete old versions immediately — keep at least the last 3 versions live.
When deploying v1.2, document what changed vs v1.1 in a Notion doc or Google Sheet: "v1.2 — added abandoned-cart workflow, fixed timezone bug in appointment reminder."
If v1.2 causes problems in a new sub-account, you can detach and re-deploy v1.1 within minutes instead of debugging.
Step 6
If you serve multiple industries (dental, fitness, legal), build a master snapshot per vertical. Saves rebuilding the same vertical-specific workflows from scratch.
Create a sub-account per vertical: MASTER — DENTAL, MASTER — FITNESS, MASTER — LEGAL.
Each gets vertical-specific workflows: dental has "appointment reminder 24h before," fitness has "missed-session check-in," legal has "consultation follow-up."
Create separate snapshots per vertical: "Dental Master v1.0," "Fitness Master v1.0," "Legal Master v1.0."
When onboarding a new dental client, deploy Dental Master. Saves the 4-6 hours of re-creating dental workflows from a generic snapshot.
Caveat: only worth it if you have 5+ clients in that vertical. Below that, generic snapshot + 30 min customization is faster.
Common mistakes
Using a live client sub-account as the snapshot source
What goes wrong: Every new sub-account inherits the source client's custom fields, pipelines, contact tags, and any business-specific workflow logic. Client data leaks across sub-accounts in form of orphan tags and fields. Cleanup takes 30-60 min per affected sub-account. Across 10 sub-accounts, that's 5-10 hours.
How to avoid: Always build a dedicated MASTER TEMPLATE sub-account with no real client data. Use it as the only snapshot source.
Including contacts or opportunities in the snapshot
What goes wrong: Source-client contacts (their leads, their customers) get cloned into every new sub-account. Massive privacy issue and a data leak that could violate GDPR / CCPA. Plus the new client sees junk contacts they have no context for.
How to avoid: When creating snapshots, explicitly exclude Contacts, Opportunities, Conversations, and Appointments. Only include template assets (workflows, funnels, templates, fields, pipelines, tags, calendars, forms).
Using Overwrite mode when loading new snapshot versions
What goes wrong: Any client-side customization to workflows or templates gets silently replaced. Client comes back next week asking why their custom email template was deleted. You don't know because GHL doesn't log the overwrite. Trust damage.
How to avoid: Always use Append mode. Overwrite only if you have written client permission to discard their customizations.
Not versioning snapshots
What goes wrong: You make changes to the master template, recreate the snapshot, and now have no record of what changed. New deployments behave differently than old deployments and you cannot tell why. Debug time per affected sub-account: 1-2 hours.
How to avoid: Use semantic versioning (v1.0, v1.1, v2.0). Keep last 3 versions live. Document changes in a Notion / Google Sheet changelog.
Deploying snapshots without testing in a sandbox sub-account first
What goes wrong: New snapshot version has a broken workflow trigger. You deploy it to 5 client sub-accounts before noticing. Now 5 clients have a silently-failing automation. Discovered when client asks why their leads are not getting follow-up.
How to avoid: Maintain a SANDBOX sub-account. Deploy every new snapshot version there first. Run a full test cycle (form submit → workflow fire → email send) before deploying to client sub-accounts.
Treating snapshots as one-and-done instead of a versioned product
What goes wrong: Master template stays at v1.0 forever. Every new client onboarding still requires 5-10 manual fixes because the template is stale. Cumulative time loss over a year: 60-100 hours.
How to avoid: Schedule a quarterly snapshot review. Update master template with learnings from the past 90 days of client work. Release v1.1 / v1.2 / v2.0 on cadence.
Recap
Done — what's next
How to set up your GoHighLevel agency account the right way
Read the next tutorial
Hand it off
A well-built snapshot saves 5-7 hours per new client onboarding. Over 10 sub-accounts that's 50-70 hours recovered. A GoHighLevel specialist can build your first master snapshot + train your team on the version workflow in $400-800 of talent time — recovers itself by sub-account #3.
See specialist rates
Yes — Agency View → Snapshots → Share via Link. You get a public link the receiving agency can import in their own Agency View. Useful if you bought a snapshot from a marketplace (e.g., HighLevel Marketplace) or are sharing with a partner agency.
Nothing automatic — snapshots are pull, not push. Existing sub-accounts keep their current state. To update them, you have to manually load the new snapshot version into each sub-account (Settings → Snapshots → Load).
No — GHL does not auto-version. Every time you click "Update Snapshot" on the same snapshot, the old version is replaced. To version manually, create a new snapshot with v1.1 / v2.0 in the name instead of updating the existing one.
Typically 2-5 minutes for a snapshot with 5-10 workflows + 2 funnels + standard templates. Larger snapshots (20+ workflows) can take 10-15 min. The sub-account is usable during loading but new assets appear progressively.
Technically yes — GHL allows you to share snapshots. Whether you give it to them is a business decision. Many agencies build snapshot export into the offboarding contract. Standard rate for export: $500-1,500 one-time depending on snapshot complexity.
GoHighLevel
Most agencies pay $297-497/mo for GHL for 3 months before a single client uses it. The blocker is almost never the platform — it's an unstructured agency setup that snowballs into rework. This is the setup path specialists use day one.
GoHighLevel
GHL's Workflow Builder is the most powerful piece of the platform — and the easiest to misconfigure into expensive silence. This is the structural setup: triggers that don't fire-and-forget, actions that don't double-send, and the guardrails that catch problems before clients do.
GoHighLevel
GHL's funnel builder is fast enough to launch a campaign by Friday. It's also slow enough to tank your conversion rate if you don't structure pages, tracking, and upsells the way performance specialists do.
GoHighLevel
Most agencies pay $297-497/mo for GHL and use 25% of it. The platform is too deep to learn casually. This is the honest framework: when the cost of self-managing exceeds the cost of hiring, and how to tell which side you're on.