GoHighLevel Create Snapshot: Step-by-Step Guide

Every GoHighLevel agency reaches a point where rebuilding the same funnels, workflows and forms for a new sub-account feels like wasted time. Snapshots solve that specific problem, and the GoHighLevel create snapshot workflow is more mechanical than most agencies expect once you know where the pieces live.

A snapshot isn't a backup of an account. It's a template pulled from one sub-account's build, and it copies configuration only: workflows, funnels, calendars, forms, emails, triggers, custom fields, custom values, membership content, services, webinars and AI Studio projects.

Contacts, appointments and conversations never travel with it. Neither do integrations, Stripe connections, WordPress licenses or phone numbers assigned to Voice AI agents.

HighLevel's snapshot overview documentation is specific about that boundary. Live customer data and third-party credentials belong to the account that holds them, not to a template meant for reuse anywhere.

The GoHighLevel Create Snapshot Process, Step by Step

You don't build a snapshot from scratch. The sub-account comes first, built and checked over, and only then does it turn into a template.

1. Open Account Snapshots from Agency View and click Create New Snapshot.
2. Name the snapshot and choose the sub-account you're capturing it from.
3. Select all assets, or expand each category and handpick the ones you want, then click Create.

Naming matters more than it looks like it should. "Spa Funnel Setup" tells you something six months later; "Snapshot 3" doesn't.

HighLevel's own walkthrough on creating new snapshots gets specific about custom fields too: URL, date and time, rich text, user fields, and image-enabled checkboxes or radio buttons all carry across, not just plain text and number fields.

Associations between CRM objects transfer automatically, but only if both linked objects are part of the selection. Contact-to-contact associations aren't supported either way, no matter what you select.

If an asset fails to load partway through the capture, a retry option picks up where it stopped instead of forcing you to start over.

Sharing the Snapshot You Just Built

A snapshot sitting in your account is only useful once someone else can load it. HighLevel offers six ways to share one, and they aren't interchangeable.

To generate one, open Account Snapshots, go to My Snapshots, select the one you want and open its action menu.

HighLevel's share snapshot documentation lets you turn on Assets Protection before you click Get Link. That setting stops whoever receives it from repackaging the contents and passing them along further.

You can't edit a snapshot directly once it exists, either. Build the improvement in a master sub-account instead, then refresh the existing snapshot or create a new version from that account. Loading a snapshot won't overwrite a client's existing data unless you explicitly choose to override conflicting assets.

That discipline matters most for agencies running a white-label operation across dozens of client accounts, where white-label support work often starts with exactly this kind of snapshot audit.

Agencies packaging a template for a SaaS rollout rather than a single client carry the same approach into a SaaS CRM launch. Anyone planning to charge for a finished snapshot through the marketplace share link should read our piece on the GoHighLevel Snapshot Marketplace before listing it.

None of this fixes a weak source account. A snapshot only ever copies what's actually configured well, and agencies that snapshot a half-finished build end up deploying the same gaps to every new client.

That's usually the moment they bring in GHL setup and configuration help to fix the source account before it gets copied any further.

Cover photo by Caleb Oquendo on Pexels