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 deliberately leaves the records behind.
The short answer
- A snapshot is a reusable template of one account's configuration, meaning its pipelines, workflows, forms, calendars, custom fields and templates, saved so it can be applied to another account.
- Snapshots copy setup, not records. HighLevel's own snapshots documentation lists contacts, appointments, conversations, messages, reputation data and third-party integrations among the assets that do not transfer, 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.
- The question that separates a useful snapshot feature from a token one is whether you can push an updated snapshot to accounts that already exist, or only apply it once when the account is created.
What a snapshot actually contains
Think of an account as two layers. The configuration layer is how the account is shaped: pipeline stages, automations, forms, calendars, custom fields, 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, applying one client's snapshot to another client's account would move real people's data between two businesses that have no relationship. Every vendor that offers snapshots draws the line in roughly the same place for that reason.
HighLevel describes its snapshots as reusable templates that capture selected configuration assets from a sub-account so they can be copied into new or existing sub-accounts. Its documentation lists workflows, triggers, funnels, forms, email templates, campaigns, calendars, custom fields, pipelines, tags, custom objects and dashboards among what a snapshot can carry, and lists contacts, appointments, conversations, messages, reputation data and third-party account connections among what does not transfer. Those facts are from HighLevel's support documentation 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 | Not available yet. On the roadmap. | On the roadmap. Today the repeatable path is configuration through MCP tools: stages, cadences, segments, ICPs, suppression entries and agent policy each have a tool, so a setup script can rebuild a standard configuration on a new instance. |
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 documentation describes selecting which specific assets to include during each application step.
Disclosure: SalesCrew is our product, and it does not have snapshots today. Export and apply are on the roadmap. What exists now is that every configuration action in the app is also an MCP tool with the same effect, so an agency can script a standard setup and run it against a new instance. That is slower to build than clicking one button and faster than clicking through every screen, and it is the honest state of it.
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. Its snapshots documentation lists contacts and appointments, conversations and conversation history, messages and live account activity, reputation data, and integrations and third-party account connections among the assets that do not transfer, as of September 2026. That split is deliberate and it is 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 configuration into a different account and deliberately leaves the records behind. 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 documentation describes loading a snapshot into an existing account and pushing updates to linked accounts, not only creating 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.