A GoHighLevel snapshot is a saved copy of a sub-account's setup that you can load into any other sub-account. It carries the structure (workflows, funnels, forms, pipelines, calendars, templates) but not the data inside it (contacts, conversations, payments). If you onboard more than one client, snapshots are the feature that turns a multi-day build into a load-and-configure job of an hour or two.
This guide covers what a snapshot contains, what it leaves out, how to create and deploy one, and the mistakes that cause accidental texts to real leads. For the wider picture of the platform, see our GoHighLevel review.
What a snapshot actually is
Think of a snapshot as a blueprint of a building, not the tenants. You build a complete setup once inside a template sub-account: lead capture, follow-up automation, booking, pipeline, and reporting. You then save that sub-account as a snapshot in your agency view. Each new client gets a fresh sub-account, and you load the snapshot into it. The client starts with a working system instead of an empty CRM.
Snapshots live at the agency level, not inside a sub-account. You find them under Account Snapshots in the agency dashboard. That detail matters because it means a sub-account user cannot create or load them; only agency admins can.
What snapshots include
Based on current documentation and third-party guides, a snapshot generally captures these asset types:
- Workflows, including triggers, conditions, and actions.
- Pipelines and opportunity stages.
- Funnels, websites, and landing pages.
- Forms, surveys, and quizzes.
- Calendars (team, service, round robin, and class types).
- Email, SMS, and voicemail templates.
- Custom fields, custom values, tags, and trigger links.
- Products, order forms, and course or membership structure.
GoHighLevel changes what is supported over time, so treat this list as a starting point and check the load summary shown when you deploy a snapshot. It lists the asset counts that will be copied.
What snapshots do not include
This is where most first-time mistakes happen. Snapshots do not carry live data or account-specific connections:
- Contacts, conversation history, and appointment history.
- Payments, invoices, and subscriptions.
- Integration credentials such as Twilio, Mailgun, and Stripe connections.
- Domains, DNS settings, and phone numbers.
- Staff users and permissions.
The practical consequence: after loading a snapshot, a new sub-account still needs its own phone number, sending domain, calendar connections, payment processor, and compliance registration. Budget that setup time into your onboarding checklist, because the snapshot does not do it for you.
How to create a snapshot
- Build a dedicated template sub-account for one niche or offer. Never use a live client account as the source.
- Replace hard-coded business details with custom values (business name, phone, booking link) so the same assets work for every client.
- Leave workflows in draft or off. A snapshot loaded with active workflows can fire messages before you have finished configuring the account.
- In the agency dashboard, open Account Snapshots, choose Create Snapshot, select the template sub-account, and give it a versioned name such as "Dental v2.1, October 2026".
- Wait for the snapshot to finish building before loading it anywhere.
How to load a snapshot into a sub-account
Create or select the destination sub-account, then open Account Snapshots, find the snapshot, and load it to that sub-account. You will be shown the assets being copied and a choice of how to treat existing assets. Guides describe a merge option that adds assets alongside what already exists, and an override option that replaces assets of the same type. Contacts and conversations are not meant to be overwritten by a load, but test this on a throwaway account before you rely on it with a client who already has data.
After the load, work through a fixed checklist:
- Fill in the custom values (name, address, phone, logo, brand colors).
- Connect the client's calendar, phone number, sending domain, and payment processor.
- Submit messaging compliance registration where required for US texting.
- Submit a test lead through every form and funnel and confirm each workflow behaves correctly.
- Only then switch workflows on.
Sharing and importing snapshots
You can generate a share link for a snapshot so another GoHighLevel agency can import it. This is how snapshot marketplaces and agency-to-agency template sales work. Two cautions apply. First, a share link exposes your whole build, so share a clean template account, never one containing client branding or private copy. Second, treat any snapshot you import as untrusted until you have inspected it: load it into a throwaway sub-account first and read the workflows, because an inherited workflow can send messages or post data to external webhooks you did not expect.
Plans and cost
GoHighLevel's agency plans are currently listed at $97 per month for Starter (3 sub-accounts), $297 per month for Unlimited (unlimited sub-accounts), and $497 per month for Agency Pro. Annual billing is priced at roughly ten months for twelve. Snapshots are an agency-level tool, and their value scales with the number of sub-accounts you deploy into, so the Unlimited plan is where most agencies see the payoff. Confirm current snapshot access for your plan on GoHighLevel's pricing page, since plan details change.
If you plan to sell sub-accounts under your own brand, the $497 plan adds SaaS Mode, which pairs naturally with snapshots: a SaaS plan can be tied to a snapshot so each paying customer is provisioned automatically with your preconfigured setup.
Best practices that save you from rebuilds
- One template sub-account per niche. A dental snapshot and a real estate snapshot should never share a source account.
- Version your snapshots. When you improve a workflow, save a new version instead of overwriting, so you can roll back a client deployment path.
- Use custom values everywhere. Hard-coded names inside emails and funnels are the most common reason a loaded snapshot shows the wrong business name to a client's leads.
- Do not push updates blindly. Loading a newer snapshot over an account that a client has customized can replace their changes. Keep client-specific edits documented.
- Keep a post-load checklist in writing. The steps a snapshot cannot copy are the ones people forget.
A concrete example
Say you serve local dentists. Your template account contains a new-patient form, a missed-call text-back workflow, an appointment reminder sequence, a reactivation campaign, and a pipeline from inquiry to booked. Each new practice gets a sub-account and the snapshot load. You then spend your time on the parts that differ: their number, their calendar, their branding, their registration. For a vertical-specific walkthrough, see our guide to snapshots for real estate agencies.
Who benefits most from snapshots
Agencies with a repeatable offer for one or two niches get the most value, because the same build is reused many times. SaaS resellers benefit too, since automatic provisioning depends on a clean snapshot. Solo consultants with one or two bespoke clients gain less: if every setup is custom, the time spent maintaining a template may exceed the time saved.
The verdict
Snapshots are the core scaling mechanism in GoHighLevel. They copy structure, not data or connections, so plan for a short configuration pass after every load. Build from a clean template account, keep workflows off until tested, use custom values, and version everything. Do that and a new client goes live in hours instead of days. Skip those habits and snapshots become a fast way to ship the same mistake to every client.