GoHighLevel Snapshots: The Complete Guide to Creating, Deploying, and Managing Them in 2026
Quick Answer: GoHighLevel snapshots package an entire sub-account configuration — workflows, pipelines, funnels, calendars, and custom fields — into a shareable system that deploys to any sub-account in minutes. The snapshot that works across 50 client accounts is built differently from the snapshot that was never meant to leave the original sub-account. The architecture principles and the deployment checklist are in Section 2.
A GoHighLevel snapshot either saves you 20 hours per client deployment or creates 20 hours of cleanup work per deployment. The difference is in how the snapshot was built.
This guide covers snapshot creation from a build-for-deployment mindset, the version management system that keeps client accounts organized, and the testing protocol before any snapshot touches a live account.
What GoHighLevel Snapshots Include and Exclude
| Included in Snapshot | Not Included in Snapshot |
|---|---|
| Workflow automation sequences | Contacts and contact data |
| Pipeline stages and names | Calendar availability and connected email accounts |
| Custom field definitions | Third-party integration credentials (Stripe, Gmail, etc.) |
| Funnel and website pages | A2P 10DLC registration — transfers per account |
| Email and SMS templates | Billing configuration |
| Tags and smart list definitions | User accounts and permissions |
| Custom values (keys only, not values) | LC Phone numbers |
How to Create a GoHighLevel Snapshot the Right Way
- Prepare the source sub-account: Remove all real client contact data. Clear all Custom Values — set them to descriptive placeholder names like “YOUR_BUSINESS_NAME_HERE.” Remove any hardcoded phone numbers, URLs, or calendar IDs from workflow message text.
- Test the cleaned sub-account: Run a test contact through every workflow to verify merge fields resolve to placeholders, not blank or broken data.
- Create the snapshot: Agency Dashboard → Snapshots → Create Snapshot → select source sub-account → choose components → name with version number (e.g., “HVAC v4 Apr 2026”) → save.
- Document the snapshot: Create a setup document listing every Custom Value that must be filled in after import, and every third-party integration that must be reconnected.
- Test the snapshot on a fresh sandbox: Import the snapshot to a brand new sub-account and follow your own setup document. If anything is unclear or broken, fix before sharing.
Expected Error — Workflows show as Draft after import: GHL sets all imported workflows to Draft status as a safety measure. After importing a snapshot, you must manually activate every workflow. Go to Automation → Workflows → set each workflow to Active. This is intentional — GHL does not auto-activate imported workflows to prevent accidental automation sends during setup.
If you are deploying a snapshot to a client with an existing GHL account…
Import to a fresh sub-account first. Configure all Custom Values and reconnect integrations. Then manually migrate only the needed workflows and pipelines to the live client account. Never import a new snapshot directly into a live account — naming conflicts can overwrite existing pipeline stages and workflow configurations without warning.
If you are deploying the same snapshot to 10+ clients…
Create a standardized setup checklist in a Google Doc or Notion page listing every post-import configuration step. Run every new client setup from this checklist. Each step should be verifiable — “Calendar connected and test booking works” rather than “Set up calendar.” A verifiable checklist catches configuration errors before the client interacts with the system.
Critical Failure Points: Snapshot Management Mistakes
Failure Point 1 — Sharing Snapshots Without a Setup Document: A snapshot without a setup document is a puzzle without an answer key. Anyone who imports it will spend hours figuring out what needs to be configured. Write the setup document when you create the snapshot — not after someone asks for help.
Failure Point 2 — Not Maintaining a Version Registry: As you update your snapshot over time, track which version each client sub-account is running. A simple spreadsheet with client name, snapshot version, and import date prevents the situation where you are debugging a workflow issue in a client account and cannot tell if the problem is their configuration or a bug in an older snapshot version.
The Consensus Break: The GHL Snapshot Marketplace Is Not Where the Best Snapshots Live
The GHL Snapshot Marketplace is the most visible source of snapshots. It is not where the most effective snapshots are.
The best snapshots for specific industries are built by agencies who run clients in those industries. An HVAC snapshot built by an agency managing 30 HVAC clients has been refined by real-world use — actual client data, actual support tickets, actual conversion rates. A marketplace snapshot was built to look comprehensive in a preview.
Before buying a marketplace snapshot, ask the creator: How many client accounts is this running in? What is the average conversion rate on the follow-up sequence? What was the last change made and why? If they cannot answer these questions with specifics, the snapshot was not built from operational experience. See our industry-specific snapshots at AutoGenCRM and the snapshot shop.
Verified working as of April 15, 2026.
Frequently Asked Questions
How do I share a GoHighLevel snapshot with another agency?
Go to Agency Dashboard → Snapshots → select the snapshot you want to share → click Share → copy the snapshot link. Send this link to the receiving agency. They import it via Agency Dashboard → Snapshots → Import Snapshot → paste the link. You can also set snapshot access to public or restricted. Restrict access to specific people by requiring them to request access through the link.
Can a GoHighLevel snapshot include workflows?
Yes. GoHighLevel snapshots can include workflow automation sequences, including all trigger configurations, action steps, conditional branches, and wait timers. The snapshot captures the workflow structure but not the execution history or active enrollment of contacts. All workflows in an imported snapshot start as Draft status and must be manually activated after import.
How do I update a GoHighLevel snapshot after making changes?
To update a snapshot, make changes in the source sub-account, then create a new snapshot version from Agency Dashboard → Snapshots → Create New Snapshot. Name it with the new version number. The old snapshot link remains valid for anyone using the previous version — GHL does not auto-update existing snapshot links. Distribute the new snapshot link to clients or team members who need the updated version.