What Is a GoHighLevel Snapshot? Definition, What Transfers & How to Build One

What Is a GoHighLevel Snapshot? Definition, What Transfers & How to Build One

A GoHighLevel Snapshot is a reusable template of an entire sub-account, including its pipelines, funnels, websites, calendars, workflows, forms, email/SMS templates, and custom fields, that can be deployed into a new or existing sub-account in a few clicks.

It is not a live backup and it is not a one-time account transfer: contacts, opportunities, conversations, and third-party integration connections do not travel with it. Snapshots exist so an agency can build a working system once and redeploy it across unlimited clients instead of rebuilding the same funnels and automations from scratch every time.

If you’re setting up more than one or two GoHighLevel sub-accounts, understanding Snapshots correctly, including what they deliberately leave out, is what separates a clean, repeatable onboarding process from a support headache six months in. (This piece focuses on the core definition and mechanics. For a hands-on setup walkthrough, see our Snapshots Guide; for pre-built niche examples, see GHL Niche Markets & Snapshots.)

What a Snapshot Actually Captures

A Snapshot packages the structural and creative work built inside a sub-account so it can be replicated elsewhere. That typically includes:

  • Funnels and websites (pages, layout, copy structure)
  • Pipelines and their stages
  • Workflows and automations (triggers, actions, conditions)
  • Calendars and booking configuration
  • Forms and surveys
  • Email and SMS templates, plus campaign templates
  • Custom fields and tags
  • Trigger links
  • Document and contract templates

Think of it less like a photograph of a moment in time and more like an architectural blueprint: it captures how the business is built, not who is currently inside it.

What a Snapshot Does Not Transfer, and Why That’s Deliberate

This is the single most common misunderstanding agencies run into, and it’s worth stating plainly: Snapshots do not carry live client data. Specifically, the following are excluded:

  • Contacts: names, phone numbers, email addresses, and any CRM records
  • Conversations: text threads, email history, call logs
  • Opportunities: the pipeline structure transfers, but the actual deals/leads sitting in it do not
  • Third-party integration authorizations: connections to Stripe, Facebook, Google Ads, Twilio, Mailgun, and AI tool integrations (see our Conversation AI setup guide) need to be reconnected fresh in each new sub-account
  • Infrastructure-level settings: custom domain names, dedicated phone numbers (LC Phone), and email sending domain records (DKIM/DMARC) must be configured manually per sub-account (see our Email Deliverability guide and A2P 10DLC Registration guide)

This exclusion isn’t a limitation to work around; it’s what keeps the feature safe to use. If Client A’s contacts and conversations could load directly into Client B’s account through a Snapshot, every agency using the feature would be one accidental import away from a serious data and privacy incident. Snapshots are a blueprint, not a clone of the tenant currently living inside the building.

In practice, this means every Snapshot deployment still needs a short manual checklist afterward: reconnect payment and ad integrations, verify the sending domain, assign a phone number, and confirm team member access, before the sub-account goes live for a client.

How Snapshot Sharing Works

According to HighLevel’s own support documentation, sharing a Snapshot means generating a secure link (or invite) that allows another agency or sub-account to import a curated package of your funnels, workflows, forms, and templates.

The mechanism matters because different link types control how widely, and how permanently, a Snapshot can spread once it leaves your hands:

Share OptionWhat It Does
Permanent LinkA reusable link that can be imported repeatedly, by anyone who has it
One-Time LinkA single-use link that stops working after one import
Email LinkA single-use link sent directly via email to a specific recipient
Agency-RestrictedImport limited to a specific partner agency, identified by their agency relationship number
Sub-Account RestrictedImport limited to one exact destination sub-account you select

There’s also an Assets Protected toggle available when sharing, which prevents the recipient from copying or re-sharing the protected content further. It’s worth enabling any time you’re sharing a Snapshot outside your own agency, since without it a recipient could redistribute your build.

Once a Snapshot is imported into another agency’s account, it becomes a standalone asset in their Snapshot library. It is not linked back to your original, meaning if you update your master Snapshot later, previously imported copies do not automatically update.

This is an important operational detail if you maintain versioned Snapshots: recipients need to re-import a newer version manually to receive fixes or improvements.

Agencies that build a genuinely strong, niche-specific Snapshot also have the option to list it for sale on the GoHighLevel Marketplace, which requires approval from GoHighLevel before it goes live.

Which GoHighLevel Plan Do You Need?

Snapshot creation and deployment across multiple sub-accounts is generally associated with GoHighLevel’s Agency Unlimited plan and above, since that tier removes the sub-account cap that the entry-level Starter plan imposes.

If your goal includes selling Snapshots under your own brand through SaaS Mode, that capability sits on the top-tier Agency Pro / SaaS Pro plan; see our Scale with GHL SaaS Mode guide for how agencies structure that offer. Because GoHighLevel updates plan inclusions periodically, confirm current tier details on our GoHighLevel Pricing breakdown or GoHighLevel’s official pricing page before making a purchasing decision.

How to Build a Snapshot (Recommended Process)

  1. Build one sub-account completely first. Don’t create a Snapshot from a half-finished account; every gap you leave becomes a gap in every client account it’s deployed to. Our GoHighLevel CRM Setup Guide covers the foundational build order to follow before capturing anything.
  2. Test the build with real (or realistic dummy) data before capturing it, so you catch broken workflow logic or missing pipeline stages while it’s still one account, not fifty.
  3. Take the Snapshot from that completed sub-account through the Snapshots section of the agency console.
  4. Name it with a clear, versioned convention, for example “HVAC Lead Gen v2,” so you can track improvements as you refine it over time, and so your team knows exactly which build a client is running.
  5. Document a post-deployment checklist covering everything that doesn’t transfer: integrations, domain, phone number, sending domain verification, and team access, and actually use it every time you deploy.
  6. Re-test after major GoHighLevel platform updates. Snapshots aren’t “set and forget”; a workflow action or integration behavior GoHighLevel deprecates can silently break a Snapshot that hasn’t been opened in months.

Snapshot vs. Account Transfer: Two Different Tools

These get confused constantly, so it’s worth stating the difference directly:

  • A Snapshot is a reusable, repeatable template you can deploy into unlimited new or existing sub-accounts. It intentionally leaves out live data.
  • An Account Transfer is a one-time move of an entire, live sub-account, including its actual contacts and history, from one agency to another. It’s the right tool when a client is leaving one agency for another and needs their whole operating account to move with them, not just the structure. See our Migrate to GoHighLevel guide and platform-specific walkthroughs like HubSpot to GoHighLevel Migration if that’s your scenario.

If you’re onboarding a new client, you almost always want a Snapshot. If you’re taking over management of a client’s existing, already-populated account, you want an Account Transfer; our GoHighLevel Business Migration service handles both scenarios.

FAQ

Does a GoHighLevel Snapshot include a client’s contacts?

No. Contacts, conversations (email/SMS/call history), and the actual opportunities sitting in a pipeline are deliberately excluded from every Snapshot. Only the structure, meaning the pipeline stages themselves, the workflows, and the funnels, transfers.

If I update my Snapshot later, do previously deployed copies update automatically?

No. Once a Snapshot is imported into a sub-account, it becomes a standalone copy that isn’t linked back to the original. Updates to your master Snapshot have to be re-imported manually into any account that should receive them.

What’s the difference between a Snapshot and an Account Transfer?

A Snapshot is a reusable, repeatable template that excludes live data and can be deployed to unlimited accounts.

An Account Transfer is a one-time migration of a complete, live sub-account, including its actual contacts and history, typically used when a client’s whole account is moving between agencies.

Do I need a specific GoHighLevel plan to create and share Snapshots?

Creating and deploying Snapshots across multiple sub-accounts is generally tied to the Agency Unlimited plan or higher; selling Snapshots under your own brand via SaaS Mode requires the top-tier plan. Confirm current plan inclusions on GoHighLevel’s official pricing page, since tiers are updated periodically.

Can I stop someone I share a Snapshot with from re-sharing it?

Yes. The Assets Protected toggle, available when generating a share link, prevents the recipient from copying or redistributing the protected content further.

Similar Posts

Leave a Reply

Your email address will not be published. Required fields are marked *