How to Create and Deploy Snapshots in HighLevel – Agency Guide
A HighLevel snapshot captures the configuration of a sub-account – its workflows, funnels, pipelines, forms, calendars, email templates, and Custom Values – and packages it for deployment to other sub-accounts. Build a template sub-account with the ideal client setup. Capture it as a snapshot from the Snapshot Manager. Deploy to new client sub-accounts during onboarding. Update Custom Values with client-specific information after deployment. The snapshot is the agency’s primary quality assurance and efficiency tool – every client starts from the same proven, tested configuration.
Why Snapshots Are the Agency’s Most Important Asset
A well-built snapshot encodes months of refinement into a single deployable package.
The first time an agency builds out a HVAC client’s HighLevel setup, it takes 10 to 15 hours. The second time, with a snapshot, it takes 30 minutes.
Consistency is the other major benefit – every client of the same type starts from the same tested configuration. Client quality does not vary based on who did the setup.
Building the Template Sub-Account
Create a dedicated sub-account named ‘TEMPLATE – [Industry]’ or similar. This is never a live client account – it exists only as the source for snapshots.
Configure the template sub-account fully: Settings (Business Info uses placeholder Custom Values), Workflows (all core automations built and tested), Funnels (standard landing pages), Pipelines, Forms, and Calendars.
Test every workflow in the template sub-account with test contacts before capturing the snapshot. A snapshot that deploys broken workflows means every client that receives it gets the same broken configuration.
Capturing a Snapshot
In the Agency Dashboard, navigate to Snapshot Manager. Click to create a new snapshot and select the template sub-account as the source.
The snapshot captures: workflows, funnels, websites, forms, surveys, email templates, pipelines, calendars, products, and Custom Values. Some elements (like connected integrations) do not transfer in snapshots – they must be reconnected per sub-account.
Name the snapshot descriptively – ‘Home Services – Standard’ or ‘HVAC Client – Full Setup.’ Include the date or a version number.
Deploying a Snapshot
When onboarding a new client, create a new sub-account. In the setup flow or from the sub-account’s Settings, find the snapshot import option.
Select the appropriate snapshot. The deployment populates the sub-account with all the snapshot’s contents. Review the deployed elements – check that workflows imported correctly, funnels are present, and pipelines are configured.
After deployment, update the Custom Values for the client: business name, phone number, address, website URL, booking link, and Google Review link. These client-specific values populate throughout all templates and workflows automatically.
Maintaining and Versioning Snapshots
Update the template sub-account when improvements are made – when a workflow is optimized, a funnel converts better, or a new automation is added.
Capture a new snapshot version after meaningful updates. Keep the previous version accessible in case a rollback is needed.
Document what each snapshot version includes – a simple notes file or comment in the snapshot name (‘v3 – Added review request + MCTB’) helps the team understand what changed.
Snapshot Elements That Do Not Transfer
Connected third-party integrations – Google, Facebook, Stripe – must be reconnected per sub-account after snapshot deployment.
LC Phone numbers must be provisioned separately – each sub-account gets its own phone numbers.
A2P 10DLC registration must be completed for each sub-account – it is not captured in the snapshot.
Try HighLevel free – see every feature during your trial
Full platform access, no credit card to start.