GoHighLevel Snapshots and Templates Explained for Agencies

What is a GoHighLevel snapshot?

HighLevel describes a snapshot as a reusable template containing selected configuration assets from a source sub-account, which can be copied into new or existing sub-accounts. You first configure the source account, then create a snapshot from it. The official snapshot overview distinguishes this configuration reuse from moving live customer records or account history.

For an agency, our suggested use is a repeatable starting setup: for example, a form, a pipeline, a booking calendar and a follow-up workflow that you intend to adapt for each client. That is an implementation proposal, not a setup we have tested or evidence of faster delivery. In this guide, “template” means that reusable starting configuration; it does not mean a fully configured client service.

What can a snapshot copy?

The overview lists these examples of supported assets. It also says availability depends on the source account’s assets, enabled features and selected categories, so treat this as a selection of documented capabilities, not a guarantee that every item appears in your snapshot.

• Pages and messages: funnels and websites, forms, surveys, email builder templates, and text and email templates.
• Process structure: workflows, calendars, pipelines, custom fields and tags.
• Other configuration: dashboards, custom reports, documents and contracts, knowledge bases, and selected AI assets.

The same overview says some copied assets still need integrations, approvals or configuration in the destination. Its examples include WhatsApp integration and template approval, phone-number assignment for Voice AI agents, and domain, plugin or license updates for some website or WordPress assets. Copying an asset does not establish that it is ready to use.

What does not transfer?

The overview excludes contacts, appointments, conversations, messages, reputation data and live account activity. It also excludes Stripe connections and other integrations or third-party account connections. Do not plan a customer-data migration around a snapshot.

Two useful distinctions from the documented exclusions: copying calendar configuration does not copy appointments, and copying a Company or Custom Object Smart List transfers its configuration rather than the records shown in it. Those lists evaluate the destination account’s records.

Our recommendation: keep a separate destination setup list for client-specific content, connected accounts, domains, staff responsibilities and any records you need to move by a separately verified method.

Create, import, load, refresh and push mean different things

1. Create: capture selected assets from the configured source sub-account.
2. Import: add a shared snapshot to the agency’s snapshot library. This is distinct from applying it to a client account.
3. Load: apply selected assets to a destination sub-account. HighLevel also documents creating a new sub-account using a snapshot.
4. Refresh: capture selected changes from the source. Editing the source account does not automatically update the snapshot.
5. Push: send selected updated assets to linked sub-accounts that previously received the snapshot.

These distinctions come from the overview and refresh guide. The latter limits pushes to accounts inside your agency; it says external agencies must re-import using a new link. Do not promise another agency automatic updates based on sharing a snapshot once.

Review conflicts and update effects before rollout

The existing-account loading guide describes choosing assets and reviewing conflicts before confirmation. Override replaces the destination item with the snapshot version; Skip preserves the current item and excludes the conflicting snapshot item. Its FAQ warns that an override cannot be undone through the snapshot load.

The refresh guide also documents a workflow effect: when a snapshot refresh removes workflow steps, contacts waiting on the deleted steps in workflows created from snapshots are removed from those steps. Review active workflow behavior before distributing changes; do not read “configuration reuse” as a promise that updates have no operational effects.

The linked-assets article says unlinking affects future pushes and does not delete assets already deployed. That article was last modified on 22 April 2025, substantially earlier than this review. Confirm the current controls and behavior in your account before relying on those instructions.

Agency reuse checklist — our recommendations

This is our proposed planning process, not HighLevel’s prescribed checklist or a hands-on result.

1. Choose one repeatable service. Write down what should be common across clients and what must remain client-specific.
2. Prepare a source setup. Review names, copy, links and dependencies. Remove client-specific content you do not intend to distribute.
3. Record the asset selection. Give the snapshot a clear name and keep a dated list of included assets and required destination configuration.
4. Pilot in a test destination. Use test data to check form submission, pipeline placement, booking and messages for your proposed process. Record what actually works.
5. Approve each client load. Check the destination, selected assets, connections and every conflict choice before confirming.
6. Own ongoing updates. Assign a maintainer, record source changes, test an update on a limited scope and review effects before wider distribution.

What to confirm in GoHighLevel before relying on a snapshot

• Does your user have snapshot access, and are all required assets available for selection? The loading guide points to agency Roles and Permissions if Load Snapshot is missing.
• Which client-specific values, connections, approvals and assignments still need work after loading?
• Which existing assets would be overridden, and what recovery process have you verified separately?
• Which accounts and assets will receive a push, and what happens to client customizations and contacts in active workflows?
• Does the plan cover your source, test and client account capacity, and what usage charges will the deployed process incur?

For that last check, the live monthly pricing cards list Starter at $97/month with three sub-accounts, Unlimited at $297/month with unlimited sub-accounts, and Agency Pro at $497/month with unlimited sub-accounts. The page also identifies usage charges for email, SMS, calling and certain AI features. These are subscription listings, not a complete rollout budget or proof that every snapshot asset is included in every tier.

For broader service planning, see our agency lead-handling guide. If your offer includes selling software subscriptions, the SaaS Mode guide addresses that separate buying decision.