Snapshots

Snapshots are portable templates that capture the entire configuration of a sub-account and let you package workflows, funnels, calendars, forms, email templates, pipelines, custom fields, and dozens of other assets into a single reusable bundle. Instead of rebuilding every piece of a sub-account from scratch, you create the setup once, snapshot it, and deploy it to as many new accounts as you need.

What Snapshots Do

Snapshots capture a wide range of sub-account assets and transfer them to target accounts. This is the backbone of agency scaling, letting you standardize delivery, onboard clients faster, and maintain consistency across every account you manage.

What transfers in a snapshot:

• Custom Fields, Custom Values (keys only, not data), Triggers (in Draft mode), Trigger Links
• Surveys, Forms, SMS Templates, Email Templates (from Marketing, Text and Email Templates, and HTML Builder)
• Campaigns (Published state, but user assignments do not carry over), Pipelines, Calendars, Tags, Folders
• Funnels (pages and steps, but products created within funnels and tracking codes do not transfer)
• Membership Products and Offers, Workflows (with some integration action exceptions noted below)
• Teams (transferred in inactive state, requiring manual activation), Marketplace Actions and Triggers (requires the associated app to be installed on the destination account)

What does NOT transfer: Contacts and conversations, appointment data, tracking codes on websites and funnels, third-party integrations (Stripe, Google, Facebook), user accounts and permissions, reporting and analytics data, reputation and review data, custom value data (only the keys transfer), chat widget customizations, connected domains, company settings, existing tasks and manual actions.

Workflows saved in snapshots do not include certain third-party integration actions like Facebook Add/Remove Custom Audience, Google Analytics events, Google Adwords conversions, and Facebook Conversion API actions. These must be reconnected manually after loading the snapshot.

Key Configuration Options

Creating a snapshot: Navigate to Agency View and click Account Snapshots. Click the blue + Create New Snapshot button in the top-right corner. Enter a descriptive name (for example, “Dental Practice Full Setup” or “Real Estate Lead Gen v2”), select the sub-account that contains the assets you want to capture, and review the asset list. Click Select All to include everything, or expand each category using the + icon to pick individual items. Click Proceed to generate the snapshot.

Sharing snapshots: Go to Account Snapshots in Agency View, find the snapshot you want to share, and click the three-dot menu. Select Share Snapshot and copy the generated share link to send via email, chat, or messaging platform. Or enter the recipient’s email address and click Send to deliver an email with a direct import link.

Importing snapshots: Log into HighLevel in your web browser, open the snapshot share email or paste the share link into a new browser tab, and click Yes! Import Now on the confirmation dialog. Imported snapshots are stored at the agency level under Settings > Account Snapshots > Imported Snapshots tab.

Loading a snapshot into a sub-account: From Agency View, click Sub-Accounts in the left menu, find the target sub-account, and click the three-dot menu next to the Switch to Sub-account button. Click Manage Client, then Actions > Load Snapshot. Pick a snapshot from the list, click Proceed, select or skip individual assets, review the Conflicts section, and type Confirm in the confirmation box to begin the loading process.

Power Features

Selective asset snapshots: You do not have to include every asset when creating or loading a snapshot. Expand each category to see individual items and check only the ones you want. When loading a snapshot into a sub-account, you get a second opportunity to pick and choose. This is useful for creating lightweight, purpose-specific snapshots like one that only contains email templates and another that includes your full funnel and workflow setup.

Updating and refreshing snapshots: Snapshots are not static. Navigate to Account Snapshots in Agency View, find the snapshot you want to update, click the three-dot menu, and select Refresh (or Update). Review and select the updated assets and confirm the refresh. The updated snapshot replaces the previous version. If you want to keep the old version, create a new snapshot instead of refreshing.

Pushing snapshot updates to client accounts: When you update a snapshot, the changes do not automatically propagate to sub-accounts that already loaded the previous version. Go to the snapshot’s management page, view the list of sub-accounts that have loaded this snapshot, select the accounts you want to update, and push the new snapshot version. This gives you full control over rollout timing.

Using snapshots for SaaS mode: If you run a SaaS business on HighLevel, snapshots are the engine behind your product delivery. When a new customer signs up for one of your SaaS plans, the platform can automatically load a snapshot into their new sub-account. Go to SaaS Configurator in Agency settings and assign the snapshot to the relevant pricing plan. When a new customer subscribes, their sub-account is automatically provisioned with the snapshot’s assets.

Pro Tips

• Name snapshots descriptively by including the niche, version number, or purpose in the name. “v3 - HVAC Lead Gen Full Stack” is far more useful than “My Snapshot”.
• Build a dedicated template sub-account instead of snapshotting a live client account. Create a clean sub-account specifically for building and maintaining your snapshot templates.
• Use Custom Values strategically since custom value data does not transfer. Use custom value keys as placeholders (like {{business_name}} or {{phone_number}}) throughout your templates. After loading the snapshot, you only need to fill in the values once.
• Test before deploying widely by loading a new or updated snapshot into a test sub-account first. Verify that workflows trigger correctly, funnels render properly, and all automations function as expected.
• Review triggers after loading because triggers from snapshots load in Draft mode. This is intentional. Review each trigger, verify it matches the destination account’s needs, and then publish it manually.

Common Questions

What is the difference between a snapshot and a backup?

A snapshot is a portable template designed to be applied to other sub-accounts. It is not a full backup of account data. Contacts, conversations, reporting data, and integrations are not included. Think of it as a configuration blueprint, not a data archive.

Can I apply a snapshot to an account that already has data?

Yes. Loading a snapshot into an existing sub-account adds the snapshot’s assets alongside what is already there. It does not delete existing data. However, you should review for conflicts, especially with pipelines, calendars, and workflows that may have similar names.

Do triggers fire immediately after loading a snapshot?

No. Triggers from snapshots are loaded in Draft mode. You must manually publish each trigger after reviewing it. Campaigns, however, are loaded in Published state by default.

Can I use a snapshot more than once?

Yes. You can load the same snapshot into as many sub-accounts as you need. There is no limit on how many times a snapshot can be reused.

Why do custom values not include their data?

Custom values are account-specific information like business name, phone number, or address. Since every sub-account represents a different business, transferring the values would populate incorrect data. Only the keys transfer so you can fill in the correct values for each account.