GoHighLevel Snapshots: How to Use, Import & Fix Them

Key takeaways

A GoHighLevel snapshot copies an account's setup (funnels, workflows, pipelines, calendars, forms, templates, custom values) but not contacts, phone numbers, connected accounts, domains or A2P registration.
Build snapshots from a clean master sub-account and use custom values for every business-specific detail. This decides how reusable the snapshot is.
After importing, fill in custom values, connect domains and calendars, reconnect integrations, and test every workflow before going live.
Most broken snapshots come down to missing custom values, duplicate workflows, old hard-coded links, calendars with no staff assigned, or triggers pointing at missing tags.

What is a GoHighLevel snapshot?

GoHighLevel snapshots are saved copies of a sub-account's setup: the funnels, automations, pipelines, calendars and templates that make an account work. You build something once and then load it into any other sub-account.

Agencies use snapshots for three things:

Onboarding new clients quickly. Every new dentist, roofer or med spa starts from a working system instead of a blank account.
Keeping things consistent. Every client gets the same tested lead flow, so your team supports one system instead of twenty slightly different ones.
Packaging an offer. If you run GoHighLevel SaaS mode, a snapshot is usually what a new customer gets when they sign up.

A snapshot copies your setup, not the business itself. Knowing where that line falls prevents most problems.

What a snapshot includes (and what it doesn't)

HighLevel adds new asset types to snapshots from time to time, so check the asset list when you create one. As a general rule, a GHL snapshot carries the building blocks of the account and leaves out anything tied to a real person, phone line or outside login.

Usually included	Usually not included (redo in each account)
Funnels and websites (pages, steps, settings)	Contacts, conversations and message history
Workflows and their triggers and actions	Phone numbers and their call/SMS routing
Pipelines and stages	Opportunity records tied to real contacts
Calendars and their settings	Connected accounts (Google, Facebook, Stripe, etc.)
Forms, surveys and quizzes	A2P 10DLC brand and campaign registration
Custom fields and custom values	Custom domains and DNS settings
Email and SMS templates	Users, team members and their logins
Tags, trigger links and many settings	Payment history and anything tied to billing

The right-hand column is your post-import to-do list. A snapshot can include a calendar, but nobody gets booked until a team member is assigned and their calendar is connected. Text-message workflows come over too, but texts won't reliably go out until the new account has a number and an approved A2P registration. Our A2P 10DLC registration guide walks through that part.

How to create a snapshot

Snapshots are created at the agency level, not inside a sub-account. The general flow:

Build and test in a template sub-account. Keep one clean "master" account per niche or offer. Don't snapshot a live client account full of one-off edits and test contacts.
Swap hard-coded details for custom values. The business name, phone, address, booking link and review link should be custom values like {{custom_values.business_name}}, not typed into every page and email. This is the biggest factor in how reusable a snapshot is.
Clean up. Delete draft workflows, unused funnels, test forms and old tags. Anything left in the master account ends up in every client account.
Create the snapshot. In the agency view, open the snapshots area, create a new snapshot, give it a clear versioned name (for example "Med Spa Core v1.3") and pick the source sub-account.
Document it. Write a short internal note listing the custom values, required integrations and the workflows that need publishing after import.

Naming and versioning

Put a version number in every snapshot name and keep a simple changelog. You'll thank yourself when you need to know which clients are on which version.

Snapshot share links

To give a snapshot to another agency, or to sell one, you generate a snapshot share link from the agency view. The person receiving it opens the link while logged into their own agency account and the snapshot is added to their library. Depending on the options HighLevel offers when you create the link, you can control how it's shared. Treat the link like a product key: anyone with it may be able to import your work.

How to import a snapshot into a sub-account

There are two common ways in:

When creating a new sub-account, you can choose a snapshot to load as the starting point. This is the cleanest option.
Into an existing sub-account, you can load a snapshot from the agency's snapshot area. You'll usually be asked how to handle assets that already exist. Read that screen carefully: overwriting can replace a client's edits, and skipping can leave you with a half-updated account.

Pushing updates

When you improve your master account, you can refresh the snapshot and push selected changes to sub-accounts that already use it. This is handy but should be done with care. Push to one test account first, check the results, then roll out more widely.

What to do after importing a snapshot

Importing is only half the job. Here's the checklist our team runs on every new sub-account:

Fill in every custom value. Go through the custom values list and replace each placeholder with the client's real business name, phone, address, hours and links.
Connect domains. Add the client's domain or subdomain, point DNS and assign it to the right funnels and websites. Set up a dedicated sending domain for email too.
Set up calendars. Assign team members, connect their external calendars, and check availability, time zone and confirmation messages.
Reconnect integrations. Facebook and Instagram, Google Business Profile, payment processors and any other connected apps all need to be authorised in the new account.
Buy a number and register A2P. Until that's done, SMS steps in workflows may fail or be blocked.
Review and publish workflows. Imported workflows can arrive as drafts. Open each one, check triggers, filters, wait steps and internal notification recipients, then publish only what this client needs.
Test the full journey. Submit every form with a test contact, book a test appointment, and check that tags, pipeline moves, emails, texts and staff alerts all fire as expected.

If you want the reasoning behind good automation design, our post on GoHighLevel workflow automations every business needs covers the flows most snapshots should include.

Buying vs building a niche snapshot

Search for "best GoHighLevel snapshots" and you'll find hundreds of niche packs for roofers, gyms, chiropractors, real estate and more. Some are excellent. Many are a nice-looking funnel attached to automations that don't really work.

When buying makes sense

You're entering a new niche and want a starting point for copy and page layouts.
You have the in-house skills to audit and fix what you buy.

When building makes sense

The snapshot is your product, such as a SaaS offer or a signature client program.
You need it to match how your team actually delivers, with your follow-up timing, your offer and your reporting.
You plan to keep improving it and push updates to many accounts.

How to judge a snapshot's quality

Before you buy, or before you roll out your own, check these:

Custom values used throughout. Ask for the list. If the seller doesn't have one, expect to edit dozens of pages by hand.
Clear documentation. A setup guide, a list of required integrations and a description of what each workflow does.
Sensible workflow logic. Stop conditions when a lead replies or books, no endless loops, and clear names like "01 – New Lead – Speed to Lead".
Compliance basics. Opt-in language on forms, an easy way to opt out of texts, and messaging that's likely to pass carrier review.
Support and updates. Find out whether the seller pushes fixes and how they let buyers know about them.

Common snapshot problems and how to fix them

Most "broken snapshot" tickets we see come down to the same five problems.

1. Missing or blank custom values

Symptom: pages or messages show empty spaces, or the raw placeholder text, where the business name or phone should be.
Fix: open custom values in the sub-account and fill every one. If a value doesn't exist at all, it was referenced in the master account but not created there. Create it with the exact same key, then refresh the snapshot so future imports include it.

2. Duplicate workflows after re-importing

Symptom: two copies of the same workflow, and leads get double texts.
Fix: work out which copy is active, compare the two, and keep one. Pause or delete the other. To prevent it, use the push-update method for existing accounts rather than re-importing the full snapshot, and pay attention to the overwrite and skip options when you do import.

3. Links pointing to the old domain or old forms

Symptom: buttons, emails or texts send people to the template account's domain, or to a form or calendar that belongs to another account.
Fix: search emails, SMS templates and funnel buttons for hard-coded URLs and swap them for custom values or the new account's own assets. Re-select forms and calendars inside workflow triggers and actions so they point to the copies in this sub-account.

4. Calendars with no team members

Symptom: the booking widget shows no available times, or bookings aren't assigned to anyone.
Fix: users don't travel with snapshots. Add the client's staff as users, assign them to each calendar, connect their external calendars to avoid double-booking, and check the availability and time zone settings.

5. Triggers that reference missing tags or fields

Symptom: a workflow never fires, or a filter step quietly skips everyone.
Fix: open the trigger and filter settings and look for empty or invalid selections. Recreate the missing tag or custom field with the exact name and re-select it. Then run a test contact through the workflow and check the execution log.

If your account has a pile of these problems and you'd rather not fix them one by one, our GoHighLevel setup and snapshot services include a full snapshot audit and repair.

Frequently asked questions

Does a snapshot include contacts?

No. Snapshots copy an account's setup, such as funnels, workflows, pipelines, calendars, forms, templates and custom values. Contacts, conversations and message history stay in the original account. If you need to move contacts, export and import them separately.

How do I import a snapshot into an existing sub-account?

From the agency view, open the snapshots area and load the snapshot into the sub-account. You will usually be asked how to handle assets that already exist. Choose carefully, because overwriting can replace a client's edits. Afterwards, fill in custom values, connect domains and calendars, reconnect integrations and test every workflow.

What is a snapshot share link?

A snapshot share link lets another HighLevel agency add your snapshot to their own account. The recipient opens the link while logged into their agency account and the snapshot appears in their library. Treat share links like product keys and only send them to people you intend to give access to.

Why are my custom values blank after importing a snapshot?

Custom values come over as placeholders, so each one has to be filled in with the client's real details in the new sub-account. If a value is missing completely, it was referenced in the master account but never created there. Create it with the exact same key, then refresh the snapshot so future imports include it.

Will updating a snapshot change accounts that already use it?

Not automatically. Refreshing a snapshot updates the saved version, and you then choose whether to push selected changes to sub-accounts that use it. We recommend pushing to a single test account first and checking the results before rolling out more widely.

Should I buy a niche snapshot or build my own?

Buying is a good shortcut for page layouts and copy when you can audit and fix what you buy. Building makes more sense when the snapshot is your core product or needs to match how your team delivers. Either way, check for custom values, documentation, sensible workflow logic and compliance basics.

Build once, launch clean every time

A good snapshot is one of the most valuable things a GoHighLevel agency owns. It speeds up onboarding, keeps quality consistent and makes your offer something you can scale. Remember the basics: build in a clean master account, use custom values everywhere, document what has to be reconnected, and test every import before a client sees it.

New to the platform? Start with what GoHighLevel is and how it works. If you'd like a niche snapshot built properly, or an existing one repaired, book a free GoHighLevel consultation and we'll look at your setup together.