How to Install a GoHighLevel Snapshot (Step-by-Step)

Snapshots are the reason agencies tolerate everything else about GoHighLevel.

A snapshot is a clone of a configured sub-account — workflows, funnels, pipelines, calendars, custom fields, templates — that you can stamp into a brand-new sub-account in minutes. Build your chiropractor setup once, then onboard your next eleven chiropractors by cloning it. That is the difference between an agency that scales and one that manually rebuilds the same automation forty times and burns out.

If you only learn one advanced feature in the platform, make it this one.

Step 1: Build the reference account properly

A snapshot inherits every flaw of the account it came from. If your workflows have no removal conditions, all eleven clones will have no removal conditions.

So build one sub-account you are genuinely proud of first — pipeline, calendar, speed-to-lead workflow, appointment reminders, review requests, a funnel that converts — and confirm the whole loop actually fires end to end. See build your first workflow automation if that loop is not running yet.

Then clone that.

Step 2-3: Create it, load it

Create: agency dashboard → Settings → Snapshots → Create Snapshot → pick the source sub-account → name it.

Name it with a version. Chiro Core v3 tells you something. snapshot final FINAL tells you nothing in four months, and you will have five of them.

Load: create the destination sub-account, then Settings → Snapshots → Load Snapshot → choose the snapshot and the target → confirm. Wait a few minutes.

That is a client’s entire technical setup, done. The first time you watch a three-day onboarding compress into a coffee break, the $297/month stops feeling expensive — see the pricing breakdown for how that maths works across a client base.

Step 4: Push vs. Replace — read this before you click

If the destination sub-account already contains assets, you will be asked how to merge.

• Push / Add — new assets are added alongside what is already there. Safe. Some duplication.
• Replace / Overwrite — matching assets are overwritten by the snapshot’s versions.

Replace against a live client account can destroy work. If that client had a custom workflow you built for them last month and it collides with the snapshot’s version, it is gone. Nobody enjoys learning this the way most people learn it.

Rule of thumb: Replace is for your own template accounts. Push is for anything with a paying client behind it.

Step 5: What snapshots cannot carry (the hour of real work)

This is the section nobody reads and everybody needs.

Snapshots copy configuration, not connections. A freshly cloned sub-account is a beautifully configured account that cannot send a single message. You still have to:

• Buy a phone number for the new sub-account (~$1.15/month).
• Register A2P 10DLC — brand and campaign, fresh, for this business. This is the long pole: carrier approval takes days. Start it immediately. See SMS and A2P registration.
• Connect the domain and authenticate email (SPF, DKIM, DMARC).
• Connect Stripe or your payment processor.
• Reconnect Google/Outlook calendars, Google Business Profile, and social accounts — anything OAuth-based has to be authorised by the account owner.

Contacts and conversation history do not come across either, which is correct — you would not want the previous client’s contacts landing in a new account.

Step 6: Hunt down every placeholder

The cloned account is full of the source client’s details. Walk through:

• Workflows — SMS bodies, sender names, booking links, internal notification recipients.
• Funnels and websites — business name, phone, address, logo, testimonials, images.
• Email templates — the from-name, the signature, the footer address.
• Calendars — names, durations, availability, meeting locations.
• Custom values — set these properly and much of the above updates centrally.

Use custom values aggressively in your master snapshot: put {{custom_values.business_name}} and {{custom_values.booking_link}} in your templates instead of hardcoding “Northside Dental”. Then onboarding a new client means filling in a handful of custom values rather than editing thirty templates. This one habit is what separates a five-minute onboarding from a two-hour one.

The failure mode if you skip this is memorable: a new client’s leads receive a text signed with a different practice’s name. It happens constantly, and it looks exactly as bad as it sounds.

Step 7: Test before handover

Submit the form on the cloned funnel, from your phone, with a real number.

Confirm the SMS goes out from the new account’s number, the email sends from the new domain, the opportunity lands in the right pipeline, and a calendar booking hits the right calendar. Then hand it over.

The gotcha that bites at scale: snapshots don’t auto-update

Updating your master snapshot does not update the sub-accounts already created from it.

Fix a broken workflow in Chiro Core v3, and your eleven existing chiropractors keep running the broken v2 version until you deliberately push the update to each of them. There is a push-update mechanism, but it is a decision you make, not something that happens for free — and pushing an update carries the same overwrite risk as Replace.

Plan for this before you have thirty clients. Agencies that assume snapshots behave like a shared template with live inheritance get an unpleasant surprise the first time they need to ship a fix fleet-wide.

On free snapshots from the internet

There is a large ecosystem of free snapshots, mostly offered as lead magnets by agencies and affiliates. Some are genuinely excellent and will save you a week.

Treat them like a browser extension from a stranger. You are importing someone else’s workflows, templates and trigger links into your account. Load into a throwaway sub-account first, read every workflow before it touches a client, and check for trigger links pointing at their domain rather than yours.

Where this leads

Snapshots are the foundation of the agency model on this platform: build once, deploy many, charge each client monthly. Combined with white-labeling and SaaS Mode, that is how agencies turn a $297 subscription into recurring software revenue — covered in white-label and launch your SaaS agency.

If you are still weighing the platform up, the honest review is direct about what it gets wrong as well as what it gets right.