HighLevel Research
On Windows or Linux, press Ctrl+D. On a Mac, press ⌘D.
Browsers cannot add a bookmark without that command.
GoHighLevel Snapshots: What They Are, How Agencies Use Them, Limits
Last verified: 2026-08-27
GoHighLevel snapshots are reusable templates of selected configuration from one sub-account. Agencies use them to copy workflows, funnels, calendars, forms, and CRM structure into another account. A snapshot is not a backup of client data, and it does not create a finished business by itself.
You do not build a snapshot from a blank editor. HighLevel’s Help Center is explicit: configure a source sub-account first, then capture a snapshot from that account.
What a snapshot copies
The current snapshots overview lists configuration assets, not live records. Categories include advertising campaign structures, AI/automation (workflows, triggers, Conversation AI, Voice AI Agents), calendars and services, CRM structure (custom fields, custom objects, custom values, pipelines, tags), marketing content (forms, funnels and websites, surveys, email/SMS templates), dashboards and reports, memberships, brand/design, documents, review settings, WhatsApp templates, and WordPress sites.
What actually appears in a given snapshot depends on what exists in the source sub-account, which features are enabled, and which categories you select when you create or load it. Some copied assets still need post-load work: WhatsApp templates need a connected, approved WhatsApp account; Voice AI Agents need a phone number assigned; websites may need domain, plugin, or license updates.
What does not transfer
| Criterion | Transfers |
|---|---|
| Live CRM records | No — contacts, appointments, conversations, messages, and live activity stay behind |
| Payments and integrations | No — Stripe connections and third-party account connections are not copied |
| Reputation history | No — reputation data is listed as excluded |
| Private dashboards | No |
| LinkedIn Lead Gen Forms | No — Help Center states they are not included |
| Contact-to-contact associations | No — object associations copy only when both objects are selected |
Pipeline structure can copy. The deals sitting in those stages do not. That is the usual agency surprise.
Snapshots live at the agency layer, applied to sub-accounts
Snapshots are created from Agency View → Account Snapshots. Loading happens onto a sub-account: either while creating a new one, or later via Manage Client → Load Snapshot. Importing a shared snapshot only adds it to the agency library. It does not appear inside a client account until someone loads it.
Roles matter. The load article says the Load Snapshot action is missing if snapshot access is off under agency user roles and permissions.
Load, refresh, and push are different jobs
- Load applies selected assets into an existing sub-account. HighLevel checks for conflicts. Override replaces the existing item with the snapshot version. Skip keeps the current item. Override cannot be undone.
- Refresh updates the snapshot itself from the source sub-account. Changing the source account does not update snapshots automatically.
- Push sends refreshed assets to sub-accounts that already received that snapshot, inside your own agency. External agencies that imported a share link must re-import; they cannot receive a push.
HighLevel’s current refresh-and-push Help Center article describes Push Update as sending selected refreshed assets to sub-accounts that already received that snapshot, inside your own agency. External agencies that imported a share link must re-import; they cannot receive a push. Treat overwrite versus keep-client-edits behavior as verify-in-product. An older push-specific Help Center URL now 404s, so this page does not rest overwrite-versus-keep-edits claims on that missing article.
When agencies actually use them
Official use cases are configuration reuse: a standard onboarding template, a vertical-specific setup (HighLevel names real estate among other verticals), multi-location consistency, attaching a snapshot to a SaaS Mode plan so new paid accounts arrive pre-configured, and sharing a snapshot with another agency. Plan prices stay on GoHighLevel pricing.
A snapshot does not replace DNS, phone numbers, email authentication, Stripe, ads connections, or staff logins. Those still have to be set per sub-account. It also does not replace choosing whether HighLevel is the right product — that decision belongs on the alternatives shortlist.
Real-estate snapshot searches on this site fold into this page plus the real estate CRM guide. This is the feature page, not a second CRM ranking.
Sources for snapshot facts
Pricing, white-label, and SaaS Mode research is collected on the HighLevel research hub.