GoHighLevel Snapshots: Features, Setup & Practical Guide

GoHighLevel Snapshots are reusable templates that copy selected configuration assets from one HighLevel sub-account so agencies can deploy the same setup to new or existing client accounts without rebuilding everything manually. A Snapshot can include assets such as workflows, funnels, calendars, forms, campaigns, custom fields, dashboards, and many other supported configurations while leaving live customer data such as contacts, conversations, and appointments behind.

For agencies, Go High Level Snapshots can turn a manually configured client account into a repeatable deployment system. Instead of recreating the same pipeline, forms, automation, calendars, funnels, and other assets for every client, the agency can build a strong source account once, create a Snapshot from it, and reuse selected assets wherever needed.

A typical GHL Snapshot process looks like Build Source Sub-Account → Create Snapshot → Select Assets → Load Into Client Account → Customize → Refresh Snapshot Later → Push Selected Updates.

The important concept is that you do not build a Snapshot directly. HighLevel requires you to build the desired configuration inside a source sub-account first and then create the Snapshot from that account.

This guide explains what GoHighLevel Snapshots contain, what they do not copy, how to create, load, import, share, refresh, and push updates, how asset conflicts work, and how agencies can use Snapshots for client onboarding, niche templates, SaaS deployment, and standardized account management.

For a dedicated resource focused on this feature, see our complete guide to GoHighLevel Snapshots.

Create workflows, funnels, calendars, forms, pipelines, and other reusable assets inside a test sub-account, then turn the configuration into a Snapshot for future deployments. HighLevel currently maintains an official promotional page offering an extended 30-day trial.

Start Your GoHighLevel 30-Day Free Trial →

GoHighLevel Snapshots are reusable collections of selected sub-account configuration assets that can be copied into other HighLevel sub-accounts.

HighLevel describes Snapshots as a way to launch new clients faster, standardize proven setups, share templates with other agencies, and maintain consistent systems across multiple locations.

For example, an agency serving dental practices might build one optimized source account containing appointment calendars, lead pipelines, missed-call workflows, consultation forms, nurture sequences, and review-request automation.

Once that configuration works reliably, the agency can create a Snapshot and use it as the starting point for future dental clients.

The same principle can apply to real estate, fitness, legal services, home services, salons, agencies, consultants, and other repeatable client types.

Go High Level Snapshots work by capturing supported assets from a source sub-account and storing them in an agency-level Snapshot library for future deployment.

The workflow is generally:

Configure Source Account → Create Snapshot → Choose Assets → Save Snapshot → Load Into Another Sub-Account

If the source account changes later, the Snapshot does not automatically update. The agency must manually refresh it to capture the new or modified configuration.

After refreshing a Snapshot, eligible updates can then be pushed to linked sub-accounts inside the same agency.

This distinction is important because a Snapshot is not a constantly synchronized clone of the source account.

It is a reusable configuration package that the agency controls deliberately.

GoHighLevel Snapshots can include many types of reusable account configuration, including workflows, funnels, forms, calendars, campaigns, custom fields, dashboards, and other supported assets.

HighLevel's current Snapshot overview also references newer supported asset types such as Documents and Contracts, Custom Objects, Voice AI Agents, WordPress sites, WhatsApp Templates, Agent Studio assets, dashboards, and certain advertising structures.

The exact asset list can evolve as HighLevel adds products.

This is one reason agencies should review the asset-selection screen whenever creating or refreshing a Snapshot instead of relying on an old checklist.

Workflows are among the most valuable Snapshot assets because automation often takes significant time to build and test.

An agency can create lead nurture, appointment reminder, missed-call, review-request, reactivation, onboarding, and internal notification workflows once and reuse them.

After loading the Snapshot, client-specific details should still be reviewed.

Phone numbers, calendars, users, email addresses, offers, custom values, and external connections may need adjustment.

Funnels and other supported site assets can be included when the agency wants to reuse page structures across client accounts.

A template might contain a landing page, thank-you page, lead form, and booking step.

The design can then be adapted to the client's branding and offer after loading.

Copying the structure is much faster than rebuilding every section from scratch, but client-specific copy and SEO should still be customized.

Calendars can form part of a reusable setup.

This is useful for agencies serving industries where similar appointment structures appear repeatedly.

However, staff assignment, external calendar connections, availability, locations, and other client-specific scheduling information should be checked after loading.

Forms and surveys are useful Snapshot assets when the same qualification or lead-capture structure applies across multiple accounts.

An agency could create a standard consultation form and then customize business-specific questions after deployment.

Custom fields help standardize how information is stored across accounts.

For example, a niche agency may repeatedly need fields for service type, budget range, property type, lead source, or customer category.

Including those fields in the Snapshot can make related workflows and forms easier to deploy consistently.

GoHighLevel Snapshots are intended for reusable configurations, not live customer history. Contacts, appointments, conversations, and other live account history are not transferred through a Snapshot.

This is an important safety distinction.

A Snapshot should help replicate how an account is configured without cloning one client's customers into another client's CRM.

For example, the Snapshot may include the structure of a workflow but not the contacts currently moving through that workflow.

It may include a calendar configuration but not past client appointments.

It may include a form but not historical submissions from the source account.

A Snapshot should not be treated as a full backup or database clone.

Its purpose is reusable account setup.

If the goal is disaster recovery, full data migration, or preserving every historical record, a Snapshot alone is not the appropriate tool.

Think of it as a blueprint rather than a complete copy of a live business.

That distinction becomes especially important for agencies managing customer information across many accounts.

Creating a GoHighLevel Snapshot begins in Agency View after the source sub-account has already been configured.

HighLevel's current process lets the agency select the source sub-account and choose all or only selected assets to include.

Start by creating and testing the configuration you want to reuse.

This source account should contain the workflows, calendars, forms, funnels, custom fields, dashboards, and other supported assets that make up the reusable system.

Avoid turning an untested configuration into the master Snapshot.

If the source contains broken workflows or confusing asset names, those problems will be repeated across future deployments.

From Agency View, open the Account Snapshots section.

HighLevel's newer integrated onboarding also provides guidance for agencies using Snapshots for the first time, including links to topics such as creating, importing, sharing, refreshing, and pushing updates.

Choose the option to create a new Snapshot and select the source sub-account.

HighLevel then presents the available supported assets from that account.

Choose which assets should be included.

You can include a broader setup or create a more focused Snapshot containing only specific workflows, forms, funnels, or other items.

Selective asset control can make Snapshots easier to maintain.

For example, an agency could maintain one complete niche Snapshot and several smaller specialized Snapshots for specific features.

Use a name that communicates niche, version, and purpose.

For example:

Home Services Core Setup – v3

is more useful than:

New Snapshot 7

Clear naming becomes increasingly important when an agency eventually maintains dozens of Snapshots.

Create the Snapshot and verify that the intended assets are present.

HighLevel allows users to inspect Snapshot assets before loading, sharing, refreshing, or pushing changes.

Treat this review as a deployment check rather than assuming every source-account asset should automatically be distributed.

Loading a GoHighLevel Snapshot applies its selected assets to a client sub-account.

This is different from importing a shared Snapshot.

Importing adds a Snapshot to the agency library, while loading applies its assets to a particular sub-account.

For a new client, an agency can use the Snapshot as the starting configuration instead of building an empty account.

The agency can then customize branding, users, phone numbers, domains, calendars, integrations, and client-specific settings afterward.

GHL Snapshots can also be loaded into existing sub-accounts rather than only being used when creating new accounts.

HighLevel's current loading process allows agencies to select specific assets, review conflicts, and decide whether conflicting assets should be skipped or overridden.

This is useful when an existing client needs a new system added later.

For example, an agency might already manage a client's CRM but later decide to deploy a standardized review-request workflow package.

A focused Snapshot can add the relevant assets without rebuilding them manually.

When loading assets into an existing account, HighLevel can warn about conflicts.

The user can review what may be replaced before proceeding.

This is important because an existing client may already have workflows or other assets with valuable customizations.

Do not automatically override conflicts unless you understand what the destination account currently contains.

No. HighLevel states that loading a Snapshot is designed to add selected assets and does not delete existing client contacts or live data simply because a Snapshot is loaded. Existing assets are affected only where the user intentionally chooses to override conflicting configuration.

Importing a GoHighLevel Snapshot means adding a shared Snapshot to your agency-level Snapshot library. It does not automatically apply the Snapshot to a client account.

HighLevel summarizes the process as:

Share → Import Into Agency Library → Load Into Sub-Account.

This distinction is important because "import" and "load" are sometimes used interchangeably in older tutorials.

A Snapshot owner can generate an eligible share link.

The receiving user opens that link while signed into HighLevel and imports the Snapshot into their agency library.

After processing completes, the imported Snapshot becomes available for review and later loading into a sub-account.

HighLevel also supports email-based Snapshot sharing.

The recipient follows the invitation and imports the Snapshot into their agency library.

The important point remains the same: importing stores the Snapshot; loading deploys its assets.

GoHighLevel Snapshots can be shared with other agencies or recipients using controlled share links.

HighLevel's September 2026 sharing system currently includes several link types, including Permanent Links, One-Time Links, Email Links, and Agency-Restricted sharing.

The appropriate link depends on how widely the Snapshot should be distributed.

A permanent link is suited to reusable distribution.

This can be useful when an agency repeatedly shares the same template with eligible recipients.

A one-time link is designed for a single import.

This provides more control when the Snapshot should not be openly reusable through one link.

Email delivery provides another single-use sharing option.

This is useful when sending a Snapshot directly to a specific recipient.

Agency-restricted sharing can limit access to specified agencies.

This is relevant when Snapshot assets contain proprietary workflows or configurations that should not circulate freely.

HighLevel's current Snapshot system includes Assets Protection controls that can restrict how protected Snapshot assets move between agencies.

HighLevel states that a Snapshot containing a mixture of protected and non-protected assets can still be shared externally, but protected assets that are not allowed to leave the agency are excluded automatically.

Protected status also follows eligible assets within agency boundaries.

This can be useful for agencies distributing valuable proprietary systems while retaining some control over how those assets are redistributed.

HighLevel states that protected assets cannot be reshared or resold to another agency when doing so would violate the protection boundary.

This makes asset protection relevant to agencies building commercial Snapshot products or proprietary niche systems.

However, protection controls should not replace appropriate client or licensing agreements.

Technical restrictions and contractual rights solve different problems.

A GoHighLevel Snapshot does not update automatically when the source sub-account changes. You must manually refresh the Snapshot to capture new or modified assets.

This is one of the most important concepts for maintaining a Snapshot library.

Suppose the source account contains a lead-nurture workflow. Two months later, the agency improves the workflow by adding better qualification logic.

The Snapshot still contains the older captured version until it is refreshed.

From Agency View, locate the Snapshot and use the Refresh option.

HighLevel lets you select which new or modified assets should be captured.

This selective approach helps avoid unnecessary changes to unrelated Snapshot assets.

HighLevel's current refresh system can continue processing other selected assets even if one asset fails.

Failed assets are marked and can be retried without restarting the entire Snapshot refresh.

This is particularly useful for larger Snapshots where one temporary asset problem should not block the entire update.

After refreshing a Snapshot, HighLevel can push selected updated assets to eligible linked sub-accounts inside the same agency.

The agency chooses which linked sub-accounts should receive the update and which refreshed assets should be pushed.

This is different from loading the entire Snapshot again.

A push can send targeted changes.

For example, an agency could improve one standard workflow and push only that workflow to selected clients.

Imagine an agency manages 30 home-service clients using the same base Snapshot.

The agency improves its missed-call follow-up workflow.

The process becomes:

Improve Source Workflow → Refresh Snapshot → Select Updated Workflow → Push Update to Eligible Client Accounts

This can be much more efficient than manually editing 30 workflows.

No.

HighLevel's current Snapshot system uses deliberate refresh and push actions rather than silently distributing every source-account change.

This provides more control because not every source change should automatically affect every client.

Loading and pushing solve different problems.

Use Load Snapshot when adding Snapshot assets to an account, particularly for an initial deployment or new set of assets.

Use Push Update when an account already received the Snapshot and you want to send refreshed changes to linked assets.

Confusing these actions can create unnecessary duplication or conflict.

For ongoing client management, the Source → Refresh → Push model is usually more appropriate than repeatedly loading a complete Snapshot.

Build one proven client configuration, reuse it across sub-accounts, and test how Snapshot refresh and selective updates can reduce repetitive agency setup work.

Claim Your GoHighLevel 30-Day Free Trial →

External agencies do not automatically receive future updates simply because they previously imported your Snapshot.

HighLevel's current sharing documentation states that external recipients must receive and import an updated Snapshot after the source has been refreshed.

This differs from linked accounts inside your own agency, where Push Updates can be used for eligible sub-accounts.

The distinction can be summarized as:

Inside Your Agency → Refresh + Push Updates

External Agency → Refresh + Share Updated Snapshot + Recipient Imports Again

This matters for agencies selling Snapshot templates because distributing version updates requires a deliberate delivery process.

As an agency's Snapshot library grows, version control becomes important.

A useful naming approach could include the niche, main system, and version number.

For example:

Dental Lead System – v4.2

Maintain notes about what changed between versions.

This reduces confusion when employees need to decide which Snapshot should be loaded for a new client.

Version control becomes especially useful when external agencies or customers are receiving Snapshot updates manually.

GoHighLevel Snapshots can significantly shorten agency client onboarding when multiple customers use similar CRM and automation systems.

Without a Snapshot, onboarding may require manually recreating pipelines, workflows, custom fields, forms, calendars, and funnels.

With a Snapshot, the agency begins with a tested base configuration.

The remaining work becomes customization rather than reconstruction.

A typical onboarding process can look like:

Create Client Sub-Account → Load Niche Snapshot → Connect Client Integrations → Configure Users → Customize Branding → Adjust Calendars → Verify Phone/Email → Test Workflows → Launch

This creates a repeatable internal process.

GHL Snapshots are particularly valuable for niche agencies because clients in the same industry often share similar processes.

A roofing agency may repeatedly need lead intake forms, estimate pipelines, appointment reminders, missed-call automation, review requests, and reactivation workflows.

A dental agency may require consultation calendars, patient inquiry workflows, lead pipelines, and review automation.

A real-estate agency may use different lead-routing and appointment structures.

Instead of forcing every client into one generic agency Snapshot, create configurations around the actual customer journey of each niche.

Multi-location organizations can also benefit from Snapshots.

Suppose a franchise has 25 locations that need a consistent CRM foundation.

A Snapshot can standardize workflows, forms, calendars, custom fields, dashboards, and other supported assets across those locations.

Individual locations can then customize their local users, contact details, schedules, phone numbers, and other unique settings.

This provides a balance between central standardization and local configuration.

Go High Level Snapshots can support SaaS Mode by providing preconfigured account templates for newly provisioned SaaS customers.

HighLevel specifically identifies SaaS offers as a Snapshot use case.

Instead of giving every SaaS customer an empty CRM, the agency can provide a configured starting system.

For example, a roofing-focused SaaS product might provision a new customer account with lead pipelines, forms, calendars, workflows, and other relevant assets already prepared.

This can reduce time-to-value for the customer.

The Snapshot should still be designed carefully. A large number of irrelevant assets can make the SaaS product harder to understand.

Agencies can also build Snapshot-based products for other HighLevel users.

A Snapshot package might contain niche workflows, funnels, custom fields, calendars, and forms.

HighLevel's sharing system provides controlled ways to distribute such Snapshots.

Protected Assets can also help control certain redistribution behavior.

A commercial Snapshot should include clear installation instructions because importing the Snapshot does not automatically configure external integrations, credentials, phone numbers, domains, or client-specific data.

Snapshots should not be assumed to reproduce every authenticated external connection automatically.

An asset may depend on client-specific systems such as Google accounts, payment providers, phone numbers, email services, domains, Marketplace applications, or other third-party integrations.

After loading a Snapshot, review every integration-dependent asset.

For example, a workflow copied correctly may still depend on a calendar that needs a client-specific user assigned.

A funnel may copy successfully but still need the client's domain.

An invoice process may need the client's own payment provider.

This post-load configuration should be part of the agency onboarding checklist.

Before considering a Snapshot deployment complete, review the account as though you were the customer.

Check client branding, users, contact information, custom values, calendars, workflows, phone numbers, email sending, domains, forms, links, pipelines, payment settings, and integrations.

Submit test leads.

Book test appointments.

Run workflows using test contacts.

Check internal notifications.

Review emails and SMS messages for source-account information that should have been replaced.

A Snapshot saves setup time, but it does not eliminate quality assurance.

The most common GoHighLevel Snapshot mistakes come from using an untested source account, assuming Snapshots update automatically, confusing import with load, overriding client assets without review, and failing to customize integration-dependent settings.

One mistake is building the Snapshot too early.

If the underlying system has not been proven, the Snapshot simply distributes unfinished work faster.

Another mistake is assuming source-account improvements automatically appear inside the Snapshot. HighLevel requires a manual refresh.

Agencies can also confuse importing with loading. Importing adds a shared Snapshot to the agency library; loading applies its selected assets to a sub-account.

Conflict handling deserves attention when loading into existing accounts. Do not override customized client assets automatically.

Finally, test every new deployment because client-specific integrations and configuration still require manual review.

A well-organized Snapshot library becomes increasingly important as the agency grows.

Use clear names and avoid keeping several nearly identical Snapshots without documentation.

You might organize Snapshots by niche:

Home Services

Dental

Real Estate

Agency

and then maintain versions within those systems.

Alternatively, maintain modular Snapshots:

Core CRM

Review Automation

Appointment System

Reactivation Package

Sales Funnel Package

Modular Snapshots can be useful when clients need different combinations of functionality.

The right structure depends on how standardized the agency's service offering is.

A full Snapshot contains a broader client setup, while modular Snapshots contain smaller systems that can be deployed independently.

A full niche Snapshot is efficient when most clients receive nearly identical configurations.

Modular Snapshots provide more flexibility.

For example, an agency could maintain one core CRM Snapshot and separate modules for reviews, AI, reactivation, and advanced booking.

This reduces unnecessary assets for customers who do not purchase every service.

Many agencies may benefit from using both approaches.

Snapshot maintenance should be treated as an ongoing operational process rather than a one-time setup task.

When the agency improves the source account, determine whether the change belongs in the reusable template.

If it does, refresh the Snapshot.

Review the refreshed assets.

Push selected updates to appropriate linked accounts.

For external recipients, distribute the updated Snapshot separately.

Document major version changes.

Retire obsolete Snapshots so employees do not accidentally deploy an outdated configuration.

This creates a controlled template-management process instead of a collection of forgotten account copies.

HighLevel's August 2026 refresh system also handles a specific workflow situation.

If a Snapshot refresh removes a workflow step that existed in Snapshot-created workflows, HighLevel automatically removes contacts that were waiting on that deleted step so they do not remain stuck indefinitely.

HighLevel records this in Execution Logs as a Snapshot-related removal.

This is a useful example of why Snapshot updates should still be reviewed carefully.

Changing workflow structure can affect live automation behavior in destination accounts.

HighLevel lets agencies refresh and push selected assets instead of requiring a complete Snapshot replacement.

This is valuable for production accounts.

If only one workflow changed, the agency does not necessarily need to push every funnel, form, calendar, and dashboard again.

Selective updates reduce unnecessary risk and make change management easier.

The agency should still know which destination accounts have client-specific customization before pushing a standard asset over them.

GoHighLevel Snapshots are reusable templates that capture selected configuration assets from a source sub-account so those assets can be copied into other sub-accounts. They can include workflows, funnels, calendars, forms, campaigns, custom fields, dashboards, and other supported assets.

No. Snapshots are designed for configuration assets and do not copy contacts, conversations, appointments, or live account history.

Yes. HighLevel lets agencies load selected Snapshot assets into existing sub-accounts and review conflicts before choosing whether to skip or override affected assets.

No. You must manually refresh the Snapshot to capture new or modified source-account assets.

Yes. After refreshing a Snapshot, HighLevel allows selected changes to be pushed to eligible linked sub-accounts inside your own agency.

Importing adds a shared Snapshot to your agency-level library. Loading applies selected assets from that Snapshot to a particular sub-account.

Yes. HighLevel currently supports several sharing options including Permanent, One-Time, Email, and Agency-Restricted Snapshot links.

No. HighLevel states that external agencies do not automatically receive later Snapshot updates. The owner must refresh and share the updated Snapshot, and the receiving agency must import the new version.

Yes. HighLevel states that a Snapshot can be reused across multiple sub-accounts.

Yes. HighLevel identifies prebuilt SaaS account templates as one of the main use cases for Snapshots.

Yes. HighLevel provides selective asset control when creating and refreshing Snapshots. Agencies can include all eligible assets or choose only specific workflows, funnels, forms, and other items.

HighLevel's Assets Protection system can prevent protected assets from being redistributed outside the permitted agency boundary. Mixed Snapshots can still share eligible non-protected assets.

HighLevel states that loading a Snapshot does not automatically delete existing contacts or client data. When configuration assets conflict, users can review the conflict and decide whether an existing asset should be skipped or overridden.

Yes. HighLevel currently maintains an official promotional landing page offering an extended 30-day free trial. It states that no charge is processed when the trial begins and billing starts after 30 days unless the user cancels before the trial ends.

GoHighLevel Snapshots help agencies turn successful account configurations into reusable templates that can be deployed across new or existing sub-accounts. Instead of rebuilding workflows, funnels, calendars, forms, custom fields, dashboards, and other supported assets for every client, an agency can create a standardized source account and reuse selected components.

The best Snapshot starts with a clean and thoroughly tested source sub-account. Build the system first, verify that the workflows and assets perform correctly, then capture only the components that should become reusable.

For Go High Level Snapshots, it is also important to understand the difference between creating, importing, loading, refreshing, and pushing. Importing stores a shared Snapshot in the agency library, loading deploys assets to a sub-account, refreshing captures changes from the source, and Push Updates sends selected refreshed assets to eligible linked accounts.

Do not treat Snapshots as automatic synchronization. Changes in the source account do not automatically update the Snapshot, and changes in the Snapshot do not automatically propagate to every client. This deliberate model gives agencies more control over when standardized updates affect production accounts.

As an agency grows, GHL Snapshots can support faster onboarding, niche-specific account templates, multi-location standardization, SaaS provisioning, commercial template distribution, and ongoing client-system maintenance.

The real advantage is not simply copying assets faster. It is creating a repeatable operating system where proven configurations can be deployed consistently while still allowing each client account to receive the customization it genuinely needs.

Create a reusable source account, test your workflows and assets, build a Snapshot, and experiment with loading and updating it across your own test sub-accounts.

Start Your GoHighLevel 30-Day Free Trial →