GoHighLevel Snapshots: The Feature That Makes Multi-Location Management Possible

What Are Snapshots?

A Snapshot is a complete copy of a GoHighLevel sub-account's configuration. Think of it as a system backup that you can deploy to any new sub-account. Everything you've built -- pipelines, workflows, email templates, funnel pages, custom fields, tags, calendars, forms, automations -- gets packaged into a single Snapshot that deploys in minutes.

The analogy: Snapshots are to GoHighLevel what disk images are to IT deployment. Instead of manually configuring every new computer, you build a master image once and clone it infinitely. Snapshots do the same thing for your business systems.

Availability: Snapshots are available on the Agency Unlimited plan ($297/mo) and SaaS Pro plan ($497/mo). They are not available on the Starter plan.

What Snapshots Capture

A Snapshot includes:

Component	Included	Notes
Pipelines	Yes	All stages, automations, and configurations
Workflows	Yes	Every trigger, action, and branch
Email templates	Yes	All designs and content
SMS templates	Yes	All message templates
Funnels	Yes	All pages, forms, and designs
Websites	Yes	Full site builder pages
Custom fields	Yes	Contact, opportunity, and custom object fields
Custom values	Yes	Dynamic values used in templates
Tags	Yes	All tag definitions
Calendars	Yes	All calendar configurations
Forms	Yes	All form designs and integrations
Triggers	Yes	All trigger configurations
Social planner settings	Yes	Post templates and configurations

What Snapshots do NOT include:

• Contact data (contacts are location-specific, not transferable)
• Conversation history
• Media files uploaded to the media library
• Connected integrations (Twilio, Mailgun, Stripe -- these must be configured per sub-account)
• Domain settings (sending domains, custom domains)

How to Build a Snapshot

Building a Snapshot is straightforward, but building a good Snapshot requires thinking systematically about what should be standardized across all locations.

Step 1: Build your master sub-account

Create one sub-account that represents your ideal location setup. This is your "golden" account -- the one you'll clone everywhere. Take your time here. Every pipeline stage, every workflow branch, every email template should be exactly how you want it across all locations.

Step 2: Use custom values for location-specific data

Anywhere your templates reference location-specific information (business name, address, phone number, booking link), use GHL Custom Values instead of hardcoding. When you deploy the Snapshot to a new sub-account, you update the Custom Values once and every template, email, and workflow that references them updates automatically.

Example Custom Values:

• {{custom_values.business_name}} → "SkyYield - Downtown"
• {{custom_values.business_address}} → "123 Main St, Atlanta, GA"
• {{custom_values.business_phone}} → "(404) 555-0100"
• {{custom_values.booking_link}} → "https://app.ghl.com/booking/downtown"

Step 3: Test everything in the master account

Before snapshotting, run through every workflow, every funnel, and every email template. Submit test forms, trigger test automations, send test emails. Fix anything that's broken. Once you Snapshot, that broken workflow gets cloned to every new location.

Step 4: Create the Snapshot

Navigate to Agency View → Snapshots → Create New Snapshot. Select your master sub-account. Choose which components to include (usually all of them). Name it clearly -- "SkyYield Master v3.2 - March 2026" -- with version and date so you can track iterations.

Step 5: Version control

GHL doesn't have native version control for Snapshots. I maintain my own system: every time I update my master account, I create a new Snapshot with an incremented version number and date. I keep the previous version as a rollback option. A simple spreadsheet tracks what changed in each version.

My SkyYield Snapshot: What's Inside

Here's exactly what my master Snapshot includes -- the system running across 50+ venue sub-accounts:

Pipelines (3)

• Venue Onboarding -- stages: Lead → Qualified → Proposal Sent → Signed → Equipment Ordered → Installed → Live → Active
• Support -- stages: New Ticket → In Progress → Waiting on Venue → Resolved
• Renewal -- stages: Upcoming Renewal → Contacted → Renewed → Churned

Workflows (12)

• New venue intake (triggered by Tally form via Zapier)
• Welcome email sequence (3 emails over 7 days)
• Proposal follow-up (triggered when deal moves to "Proposal Sent")
• Signed contract onboarding (8-step sequence)
• Installation scheduling (appointment booking + reminders)
• Post-installation check-in (day 3 and day 14)
• Monthly performance report email
• Review request (SMS, triggered 30 days after installation)
• Renewal reminder sequence (starts 60 days before contract end)
• Support ticket acknowledgment
• Churn prevention (triggered when deal moves to "Churned")
• Re-engagement (for inactive venues)

Email Templates (15)

Welcome email, proposal cover letter, contract confirmation, installation scheduling, pre-installation checklist, post-installation check-in (×2), monthly report template, review request, renewal reminder (×3), support acknowledgment, churn survey, and re-engagement offer.

Funnel Pages (3)

Venue intake landing page, partner referral page, and WiFi analytics demo page.

Custom Fields (8)

Venue type, square footage, number of access points, ISP provider, installation date, contract end date, monthly revenue, and partner referral source.

Total deployment time for a new venue: about 3 minutes to load the Snapshot, 5 minutes to update Custom Values with location-specific details. The entire proven system is live and running in under 10 minutes.

Deploying a Snapshot to New Locations

When a new venue signs, the deployment process is:

1. Create a new sub-account in the Agency dashboard

2. Load the master Snapshot into the new sub-account (3 minutes)

3. Update Custom Values -- business name, address, phone, booking link (5 minutes)

4. Configure integrations -- connect Twilio for SMS, set up sending domain for email (10 minutes)

5. Verify -- spot-check key workflows and templates to ensure Custom Values populated correctly (5 minutes)

Total time: ~25 minutes. Compare that to the 4-6 hours it used to take to manually build out pipelines, write emails, configure automations, and set up funnels for each new venue. At 50+ venues, Snapshots have saved me hundreds of hours.

Snapshot Best Practices

1. Use Custom Values religiously. Any text that changes between locations should be a Custom Value, not hardcoded text. This includes business name, address, phone, email, booking links, and any location-specific URLs.

2. Name your Snapshots with versions and dates. "Master v3.2 - March 2026" is useful. "Master Snapshot" is not. You'll create dozens of iterations over time.

3. Maintain a changelog. Track what changed in each Snapshot version. When something breaks in a deployed sub-account, you need to know which version it's running and what's changed since.

4. Test before deploying. Every new Snapshot version should be deployed to a test sub-account first. Run through the critical workflows before pushing to production venues.

5. Don't over-customize per location. The whole point of Snapshots is standardization. If every venue has custom workflows, you've lost the leverage. Keep 90%+ of the system identical across locations and handle exceptions with tags and conditional workflow branches.

6. Update existing locations when you improve the master. When you create a better workflow in your master account, don't just Snapshot it for new venues. Update existing venues too. This is manual in GHL (no push-to-all feature), but keeping venues in sync prevents drift.

Limitations to Know

• No push updates. You can't push Snapshot changes to existing sub-accounts. Updating 50 venues with a workflow change means updating each one manually. This is GHL's biggest Snapshot limitation.
• No partial Snapshots. You can't Snapshot just one workflow and deploy it. It's all-or-nothing (though you can choose which categories to include).
• Integration setup is manual. Each sub-account needs its own Twilio, Mailgun, and Stripe connections configured. Snapshots don't transfer these.
• No diff view. You can't compare two Snapshot versions to see what changed. Hence the changelog recommendation.
• Media not included. Images, logos, and uploaded files don't transfer. You'll need to upload venue-specific branding to each sub-account.

Why This Changes Everything for Operators

Try GoHighLevel Free for 30 Days →

Affiliate link -- we may earn a commission at no extra cost to you.