Snapshots

In practice

A snapshot is a saved copy of the setup in one HighLevel sub-account that you can load into other sub-accounts. HighLevel’s help center calls snapshots reusable templates that capture selected configuration from a source sub-account [1]. They copy how an account is built, not who is in it.

How snapshots work in HighLevel

You build the source account first, then create the snapshot from Agency View, Account Snapshots, by naming it, choosing the source sub-account and selecting the assets to include [1]. HighLevel groups assets into categories such as CRM and data structure, marketing and content, calendar and services, reporting and dashboards, communication templates and websites [1]. You can load a snapshot into an existing sub-account or create a new sub-account from one [1].

Snapshots do not update on their own. After you change the source account you refresh the snapshot, then push the update to eligible linked sub-accounts [1][2]. Agencies you shared with outside your own do not receive updates; you generate an updated share and they import it again [2].

Sharing, importing and loading are separate steps. Importing adds a shared snapshot to an agency’s snapshot library. Loading applies chosen assets from it to a sub-account [2]. When you load, a conflicting asset can be overridden or skipped, and HighLevel warns an override cannot be undone through the snapshot load [3]. Loading is meant to add assets: HighLevel says existing data changes only when you choose to override a conflict, and loading does not delete contacts [1].

What a snapshot does not copy

According to the Snapshots Overview, contacts, appointments, conversations and messages do not transfer, nor do Stripe connections and integrations [1]. Assigned phone numbers for Voice AI agents do not carry over, and WhatsApp assets are not usable before Meta approval [1]. Smart lists transfer as filter settings, not the records they show [1]. Assets Protected settings can also keep another creator’s assets from being redistributed; the protection boundary is the agency [4].

Why it matters for agencies and service businesses

If you set up the same pipelines, workflows, forms and calendars for every client, a snapshot lets you build that once and start each new account from it. In SaaS mode, a snapshot attached to a plan is applied after a customer checks out [5]. For a service business running several locations, it keeps accounts consistent. Our SaaS mode guide and snapshots guide go further.

Sharing options

HighLevel’s sharing page lists several link types: permanent links that anyone with the active URL can import, one-time links that end after one successful import, email links for a single intended recipient, agency-restricted links for agencies with specified relationship numbers, sub-account-restricted links, and Marketplace share links for snapshots distributed through an App Marketplace listing, where asset protection is applied automatically [2]. Sharing needs the Share/Import Snapshots permission [2]. Pick the narrowest link that does the job, especially for a client-specific build.

Who needs snapshots, and who does not

Snapshots help most when you repeat the same build. If you run one business in one account, you may never need one. If you use a snapshot sold or shared by a third party, check what it contains before loading it into a live account.

Common mistakes

• Expecting contacts or conversation history to move with the snapshot [1].
• Loading several snapshots with overlapping assets and overriding something by accident [3].
• Forgetting to refresh the snapshot after editing the source account [1].
• Assuming a shared copy updates itself in another agency [2].
• Loading a snapshot built by someone else into a live account without checking what it contains. HighLevel’s load page notes you cannot preview its contents directly [3].

You can use the 14-day HighLevel trialaffiliate (opens HighLevel in a new tab) (terms in our free trial guide) to practise by building a small source account and loading it into a test sub-account before using it with a client.

FAQ

Do snapshots copy contacts? No. HighLevel says contacts, appointments, conversations and messages do not transfer [1].

Do snapshots update automatically? No. Refresh the snapshot to capture changes, then push it to linked sub-accounts [1][2].

What is the difference between importing and loading? Importing adds a shared snapshot to your agency library. Loading applies selected assets from it to a sub-account [2].