What is a snapshot, and why do agencies use them?
A snapshot is a saved copy of how an account is configured, ready to apply to the next client. It copies the setup and leaves the records behind on purpose.
Want to see it first? Book a demo
The short answer
- A snapshot is a reusable template of one account's setup: its pipelines, workflows, forms, calendars, custom fields and templates. You save it so you can apply it to another account.
- Snapshots copy setup, not records. HighLevel's own docs say contacts, appointments, chats, messages, reputation data and third-party links don't move, as of September 2026.
- Agencies use snapshots because onboarding time is the constraint on how many clients one person can run, and rebuilding the same pipeline, cadence and form set by hand for every client does not scale past a handful.
- One question splits a useful snapshot feature from a token one. Can you push an updated snapshot to accounts that already exist, or only apply it once when you create the account?
What a snapshot actually contains
Think of an account as two layers. The setup layer is how the account is shaped: pipeline stages, automations, forms, calendars, custom fields and message templates. The record layer is what is in it: the contacts, the conversations, the appointments, the history. A snapshot copies the first layer and leaves the second.
That split is what makes the feature safe. If snapshots carried records, you'd move real people's data between two firms that have no tie to each other every time you used one. Every vendor that offers snapshots draws the line in roughly the same place for that reason.
HighLevel calls its snapshots reusable templates. Each one grabs the parts of a sub-account's setup you pick, so you can copy them into new or existing sub-accounts. Its docs say a snapshot can carry workflows, triggers, funnels, forms, email templates, campaigns, calendars, custom fields, pipelines, tags, custom objects and dashboards. The same docs say contacts, appointments, chats, messages, reputation data and third-party links don't move. Those facts come from HighLevel's help pages as of September 2026.
Snapshot support, vendor by vendor
Facts from each vendor's own documentation and pricing pages, as of September 2026.
| Vendor | Feature name | What it copies | How it is applied |
|---|---|---|---|
| GoHighLevel | Snapshots | Configuration assets: workflows, triggers, funnels, forms, email templates, campaigns, calendars, custom fields, pipelines, tags, custom objects and dashboards. Contacts, appointments, conversations, messages, reputation data and third-party connections do not transfer. | From the agency dashboard. A snapshot can create a new sub-account during setup, be loaded into an existing account, or push updates to linked accounts. Creating a sub-account from a snapshot requires agency admin permissions. |
| SalesCrew | Snapshot export and apply | The setup layer: pipeline stages, cadences, segments, ICPs, suppression entries and agent policy. Contacts, deals and conversations stay in the instance they belong to. | Export from one instance and apply it to a new or an existing one. Each step is also an MCP tool (snapshot_export, snapshot_apply), so an agency can script its standard setup and reapply it when the setup changes. |
GoHighLevel facts verified on help.gohighlevel.com (snapshots overview, and creating a sub-account from a snapshot) as of September 2026. Vendor features change; check the source before quoting.
Why the reapply question matters more than the create question
Every vendor that has snapshots can create a new account from one. That is the demo. The question that decides whether the feature saves you time in month nine is different: when your standard setup changes, can you push the change to the twelve clients already running on the old version?
If the answer is no, snapshots save you time exactly once per client and then hand you a growing pile of accounts that drift apart. Every improvement you make to your standard pipeline has to be applied by hand, twelve times, and the twelve will not end up identical. If the answer is yes, your standard setup is a thing you maintain in one place.
Ask a second question alongside it: what happens to a client's own customisations when an update is pushed. A snapshot that overwrites everything is dangerous on a live account; one that lets you choose which assets to include is workable. HighLevel's docs let you pick which assets to include each time you apply one.
Disclosure: SalesCrew is our product. SalesCrew exports a snapshot from one instance and applies it to another, and every configuration action in the app is also an MCP tool with the same effect. An agency scripts a standard setup once and runs it against every new instance. Reapplying the updated snapshot carries a change to clients already live.
A snapshot is not a backup, and treating it as one loses data
Questions
- Does a snapshot copy the client's contacts too?
- In HighLevel, no. As of September 2026, its docs say these don't move: contacts and appointments, chats and their history, messages and live account activity, reputation data, and third-party links. That split is on purpose, and it's the right one. A snapshot is a template of how an account is set up, not a copy of who is in it.
- What is the difference between a snapshot and a backup?
- A backup restores one account to an earlier state, records included. A snapshot copies the setup into another account and leaves the records behind on purpose. Using a snapshot as a backup will lose you the data you actually cared about, and using a backup as a template will drag one client's contacts into another client's account.
- Can I update a client account after the snapshot has already been applied?
- It depends on the vendor. HighLevel's docs show you can load a snapshot into an existing account and push updates to linked accounts, as well as start a new sub-account from one (as of September 2026). Ask any vendor this specific question, because a snapshot you can only apply once, at creation, leaves you editing every client by hand the first time your standard setup changes.