What a snapshot is
A snapshot is a reusable template. HighLevel describes it as a way to capture selected configuration assets from a sub-account so you can copy them into new or existing sub-accounts. You build the setup in a source account first, then create the snapshot from that account. A snapshot cannot start from a blank page.
You create one from Agency View under Account Snapshots. You name it, pick the source sub-account, choose the assets, and save.
What copies over
HighLevel adds asset types over time, so check the picker when you create a snapshot instead of trusting a list from last year.
- Workflows and their triggers
- Funnels
- Calendars
- Forms
- Email templates
- Pipelines
- Custom fields and custom values
- Dashboards, campaigns, and blogs
What stays behind
This protects customer records, and it also means a loaded account starts empty of people. Every integration your workflows depend on needs reconnecting in the new account.
- Contacts
- Appointments
- Conversations and message history
- Reputation data
- Integrations, such as a Stripe connection
- Tracking codes
What to fix after you load one
Copied assets often need a second pass. HighLevel notes that some assets need connected integrations, approvals, or configuration after loading. WhatsApp templates need the WhatsApp integration and approval. Voice AI agents need a phone number assigned. Website and WordPress assets may need a domain, plugin, or license update.
Run this check before real leads arrive:
- Reconnect the integrations your workflows use, such as payments, calendar sync, and email sending.
- Fill in the custom values with the new business name, phone number, and booking link.
- Register the account for A2P 10DLC before any workflow tries to send a text.
- Send a test lead through every form and workflow, and watch where it lands.
Loading into an account that already has data
Loading a snapshot adds the assets you select. HighLevel says existing data changes only when you choose to override a conflicting asset. The load screen lets you override or skip each conflict, so read that list before you confirm.
Building a snapshot you can reuse
This is how we build them for agencies:
- Start from a clean source account with no client data and no test contacts.
- Name every workflow, form, and pipeline stage so a stranger can tell what it does.
- Keep client specific text in custom values, so you fill in one list after loading instead of editing each asset.
- Write a short setup checklist for whoever loads the snapshot.
- Keep a dated changelog each time you update it.
Common questions
Does a snapshot copy my contacts?
No. HighLevel excludes contacts, appointments, conversations, message history, and reputation data. A snapshot copies configuration only.
Can I share a snapshot with another agency?
Yes. You can generate a share link that gives another agency or recipient access to the snapshot.
Will loading a snapshot overwrite my existing setup?
Only if you choose to override. Loading adds the assets you select, and you decide for each conflicting asset whether to override or skip it.