GoHighLevel Snapshots: A Practical Guide for Agencies

Description and use

Agencies can quickly and safely onboard new clients in GoHighLevel using snapshots with settings, custom values, and a checklist to avoid data copying and trigger errors.

Problem

Agencies need a repeatable, clean onboarding process for new clients on GoHighLevel without copying client data or misconfiguring triggers.

Outcome

Agencies can onboard new clients in hours, maintain clean workspaces, and avoid accidental data leakage or trigger errors.

Workflow

• Build the system in a real client account and run real leads through it
• Save the configuration as a snapshot
• Name workflows and tags clearly for maintainability
• Use custom values for all client‑specific data
• Keep triggers safe by publishing only after client details are entered or guarding with tags
• Create an onboarding checklist: load snapshot, fill custom values, port phone numbers and register A2P 10DLC, connect payments and integrations, add users, import contacts with consent, test workflows, then publish

Evidence

Snapshots are how GoHighLevel agencies onboard clients in hours instead of days.

Source

A snapshot is a saved copy of a sub-account's setup, not its data.

Source

Snapshots don't carry contacts, conversations, call logs or appointment history, phone numbers, payment connections, users, reviews, reporting and analytics data.

Source

Workflows that send messages should be safe the moment the snapshot loads: either published only after the client's details are in, or guarded by a tag or filter so nothing fires to the wrong people.

Source

Because snapshots skip so much, every snapshot I build comes with a checklist: Load the snapshot, fill in every custom value, buy or port phone numbers, connect payments, add users, import contacts, run a test lead, then publish.

Source