GoHighLevel Snapshots

Snapshot Intent

Use snapshots to reuse account configuration—not to copy live customer data

HighLevel snapshots capture reusable sub-account configuration such as workflows, funnels, calendars, forms, custom fields, custom values and many other assets.

Current HighLevel guidance makes an important distinction: contacts, appointments, conversations, reputation data, Stripe connections and integrations are not snapshot content in the same way reusable configuration is.

GoHighLevel snapshot creation owns the process of capturing the template from a source sub-account.

Selective Assets

Choose what should travel instead of assuming the whole source account belongs in every client

Current snapshot management supports selective asset creation and refresh. The organized nested asset selector preserves folder hierarchy so teams can review related assets more clearly.

We include the assets required for the product or implementation and remove experimental, obsolete or client-specific items.

GoHighLevel snapshot customization can own deeper tailoring of reusable assets for a niche or product.

Refresh

Update a snapshot manually when the source account changes

Snapshots do not update automatically when the source sub-account changes. Current HighLevel guidance requires a manual Refresh to add or remove selected updated assets.

GoHighLevel snapshot setup should document which source account and release process owns each snapshot.

We refresh only after source changes have been tested, because refreshing turns those changes into the next reusable version.

Sharing

Use the right share link and protect intellectual property where needed

HighLevel currently supports several snapshot sharing patterns, including reusable and one-time links plus restricted sharing options. Assets Protected can limit copying or re-sharing in supported sharing flows.

GoHighLevel custom snapshots may be relevant when the agency packages specialized templates for partners or customers.

Sharing is reviewed like software distribution: audience, version, included assets and support expectations should be known first.

SaaS Provisioning

Use snapshots to standardize new SaaS accounts at purchase

HighLevel SaaS plans can apply a selected snapshot during automated sub-account creation. GoHighLevel SaaS uses this to standardize client onboarding.

The snapshot should be tested independently before it becomes part of automated SaaS provisioning.

Client-specific domains, integrations and credentials remain post-provisioning tasks even when the reusable account assets load correctly.

Snapshot Portfolio Management

Organize multiple snapshots by product, vertical, owner and deployment purpose

Agencies often accumulate snapshots quickly: onboarding templates, niche packages, internal tests, client migrations and partner-shared assets. We maintain a portfolio with status such as production, testing, deprecated or external/shared. A production snapshot must have a known source, owner and recent test deployment.

GoHighLevel snapshot migration can own cross-account movement or transition use cases, while GoHighLevel custom snapshots can represent specialized products. Naming and folders should make those purposes obvious rather than leaving implementers to guess from similar titles.

Shared snapshots receive extra care because the recipient may not know the assumptions behind them. We document required custom values, domains, integrations and post-install steps. Assets Protected and restricted sharing can protect intellectual property where appropriate, but technical protection does not replace clear deployment instructions.

Deprecated snapshots are not left in the active selection list indefinitely. We mark or archive them according to the agency process so new staff do not accidentally deploy an old template simply because its name looks familiar.

Target-Account Safety

Inspect the destination before loading a snapshot into an existing client account

A snapshot can be perfectly designed and still be risky for an existing target that already contains workflows, funnels, fields and calendars. We inventory the target account before loading and identify assets that may conflict, duplicate or replace existing configuration. Selective loading is used when the target only needs part of the reusable package.

GoHighLevel snapshot customization can produce a safer variant when a common client type repeatedly needs a different set of assets. For one-time target differences, installation instructions may be enough. We avoid creating a new permanent snapshot for every minor client variation because that makes version governance harder.

After loading, we check enabled workflow state, funnel/page status, calendars, custom values and dependencies. Customer-specific domains and integrations are reconnected intentionally. If the snapshot is used for GoHighLevel SaaS automation, the same post-load checklist is converted into onboarding or internal tasks.

Target-account safety is also why Asset Viewer and version history matter. The implementer should know what the selected version contains before deployment rather than discovering the contents from the changes it makes.

We document significant target overrides so future snapshot updates do not accidentally undo intentional client-specific configuration.