GoHighLevel Snapshot Updates: Push Changes (2026)

By Dr Priya Jaganathan, GoHighLevel Certified Admin · HL Growth Partner, Australia · Updated 18 September 2026 · 10 min read

Some links below are affiliate links — if you sign up through them, HL Growth Partner may earn a commission at no extra cost to you. It never changes what we recommend. Full disclosure.

GoHighLevel snapshot updates are how agencies push a change from a master template out to client sub-accounts that are already live — and the most misunderstood button in the agency view.

Most agency owners assume a push behaves like a software update: one click, every account current, no side effects. It doesn't. A push is a selective copy with no undo, and the gap between a clean rollout and a week of cleanup is entirely in the process you wrap around it.

What a HighLevel snapshot update actually changes in a live account

Refresh first, push second

Changes in the source sub-account don't flow into the snapshot on their own. You refresh it, select the new or modified assets, and only then does Push Update mean anything.

Edit a workflow in your master account this morning and push without refreshing, and you just shipped last month's version. The refresh is resilient: failed assets are marked while the rest continue, and you can retry just those.

What a push will not touch

Snapshots move configuration, not activity. Per HighLevel's snapshots overview (May 2026), none of this transfers:

• Contacts, appointments, conversations and message history, plus reputation data and live activity
• Stripe connections and third-party integration authorisations
• Voice AI phone number assignments and private dashboards

So a snapshot update cannot delete a client's contact database. What it can do is quietly replace the automation that database runs through — harder to spot, and worse.

Load versus push: two buttons, two very different outcomes

A load is additive by design — HighLevel confirms data is only replaced if you explicitly choose Override. Load the same snapshot twice without overriding and you own two copies of everything.

Asset-by-asset: what a snapshot update does to each type

Why snapshot updates create duplicates instead of replacing

Three causes explain almost every duplicate-asset complaint.

• You loaded instead of pushed. Skipping conflicts leaves the original and the incoming copy both sitting there
• The link was broken. If a client deleted and rebuilt a workflow, it's a different asset — the push has nothing to match, so it creates a new one alongside
• The asset was never linked. Manage Linked Assets lets you toggle assets on or off in Edit Snapshot; disabled ones are excluded from future pushes, and unlinking never removes what's already deployed

Auditing linked assets before a fleet push is the highest-value ten minutes in the process — and the reason workflow folder and naming conventions are worth enforcing from day one.

Not on HighLevel yet? Start with a free 30-day trial here — long enough to build everything in this guide before you pay a cent.

How to target a subset of sub-accounts, not the whole fleet

You're never forced into all-or-nothing: Push Update lets you pick which linked sub-accounts receive the update, and which assets go with it.

The Load modal in My Account Snapshots gives you All, Linked and Available tabs, so you can see which accounts are already on it. Under More Actions → Edit Snapshot you can enable or disable individual locations — that's how you permanently exempt a customised account.

Treat those toggles as a standing "do not push" list rather than trusting someone to untick a box at 5pm Friday. Visibility of these controls depends on your role setup, so tighten sub-account permissions and user roles before handing snapshot access to a junior admin.

Naming and versioning discipline that makes pushes safe

HighLevel records a version after every successful refresh, summarising what was Added, Removed and Synced. Failed refreshes create nothing. That's an audit trail, not a safety net — so layer your own conventions on top:

• Name for vertical and release, not build date: Tradie Core v4.2, never Tradie Snapshot Final
• Prefix snapshot-owned assets consistently ([CORE]) so client-owned ones are visually obvious
• Read the Added / Removed / Synced delta before every push and check it against your change log
• Log the version pushed per client — version references appear across My Snapshots, Imported Snapshots and Shared Snapshots for exactly this purpose

Still assembling the master template? Our guide to building and deploying GoHighLevel snapshots covers the source-account hygiene that makes updates painless.

A staged rollout: test sub-account, pilot client, then fleet

Never push somewhere for the first time and everywhere else in the same action. Three gates.

Gate one is a disposable test sub-account that exists only to receive pushes. Open every touched workflow, run a live test contact through it, and confirm custom fields resolve rather than landing blank.

Gate two is one friendly pilot client who has customised nothing. Push, then watch execution logs for 48 hours — real traffic exposes breakage, which is why workflow troubleshooting matters more than build skill.

Gate three is the fleet, in batches, checking Push Update History (My Snapshots → three-dot menu → View History) for Successful, Failed and Pending counts. Heed HighLevel's caveat, logged 12 November 2024, that asset-level status can read Completed even when not all assets loaded — spot-check the accounts.

When the client has customised the asset you're about to push over

This is the judgement call that separates operators from button-pushers. You have three honest options.

• Clone and orphan it. Duplicate their asset, repoint their workflows at the copy, let the push overwrite the original. The copy isn't snapshot-linked, so it survives
• Exempt the account. Disable that location under Edit Snapshot and maintain it manually, priced accordingly
• Unlink the asset. Disable that one asset so nobody receives it, keeping the rest current

Whichever you pick, tell the client first — a one-line email beats an angry call about a rewritten sequence. Put it in your client onboarding checklist as a day-one expectation.

Rollback reality: there is no undo

HighLevel is unambiguous. An accidental override "cannot be undone", and Version Management is explicitly informational — auditing visibility, no restore action.

Your only real rollback is a snapshot of the client account taken before the push. Create one for any account you'd be embarrassed to break, date-stamp it, keep it a cycle. It isn't a perfect restore — configuration only — but you can rebuild the automation layer instead of reconstructing it from memory.

A monthly snapshot maintenance SOP for a portfolio

• Week 1 — build: changes in the master source sub-account only. No edits in client accounts, ever
• Week 2 — refresh and review: read the version delta, confirm every change was intentional, retry failures
• Week 2 — audit links: in Edit Snapshot, confirm enabled assets and locations match intent
• Week 3 — stage: push to test sub-account, then pilot client. Hold 48 hours
• Week 3 — protect: take pre-push snapshots of your exposed accounts
• Week 4 — push in batches of ten to fifteen, checking Push History between each
• Week 4 — close out: log the version pushed per client and email them a change summary

Past twenty accounts, add a quarterly CRM health check and optimisation so duplicates get cleaned. HighLevel's documentation on refreshing and updating snapshots is worth bookmarking, and plan limits sit on the official HighLevel pricing page.

Common mistakes to avoid

• Pushing without refreshing — you ship a stale version, then blame the feature
• Editing assets inside client accounts — each is a future casualty of your own push
• Selecting all assets out of habit — push only what changed
• Trusting the Push History summary — status can read Completed when not all assets loaded
• Treating Version History as a rollback — it records changes; it can't reverse them
• Pushing Friday afternoon — breakage surfaces with live traffic, and nobody's watching

If you want a documented snapshot maintenance SOP and staged push process for your portfolio, book a strategy call with the HL Growth Partner team.

Book Your Strategy Call →

Or if you just need the software first: grab the 30-day HighLevel trial and book us when you're ready to scale it.

Frequently asked questions

Does a GoHighLevel snapshot update overwrite client data?

No. Snapshots carry configuration, not records. Contacts, appointments, conversations and message history do not transfer, so a push cannot delete a client's database. What it can replace are linked assets like workflows, funnels and templates.

Why do snapshot updates create duplicates instead of replacing assets?

Usually because the asset link was broken, or because you loaded rather than pushed. If a client deleted and rebuilt a workflow, it is a different asset, so the push has nothing to match and creates a new copy alongside. Loading into an existing sub-account is additive unless you choose Override.

Can I undo a snapshot push in GoHighLevel?

No. HighLevel states an accidental override cannot be undone, and Snapshot Version Management is informational only, with no revert or restore action. Your only practical rollback is a snapshot of the client account taken before the push.

What is the difference between loading a snapshot and pushing a snapshot update?

Loading applies selected assets into a sub-account and links it, with a conflict check offering Override or Skip. Pushing sends selected assets from a refreshed snapshot to sub-accounts that already imported it. Load is for deployment; push is for maintenance.

How do I push a snapshot update to only some sub-accounts?

Refresh the snapshot first, then click Push Update and select which previously-linked sub-accounts receive it and which assets to include. You can also enable or disable individual locations under Account Snapshots, My Snapshots, More Actions, Edit Snapshot.

Do I have to refresh a snapshot before pushing an update?

Yes. A snapshot does not update automatically when you change the source sub-account. Refresh it from the agency view, select the new or modified assets, and a new version is recorded after every successful refresh.

Can I push snapshot updates to another agency's sub-accounts?

No. Push Update only reaches sub-accounts inside your own agency that previously imported the snapshot. An external agency must re-import your snapshot using a new share link to receive changes.

Related Articles on HL Growth Partner

Snapshots and vertical templates

• The tradie snapshot blueprint
• Gym and fitness snapshot structure

Agency operations at scale

• White label setup guide
• Cutting SaaS time to value
• The 75-task implementation checklist

Account hygiene and data structure

• Custom objects and data modelling
• Tag strategy and structure
• Premium workflow action costs