Snapshot Conflicts Now Protected in Sub-Accounts

TL;DR

Snapshot application to sub-accounts now includes a conflict check for existing customizations. You can choose to preserve existing assets or overwrite them.

Who this affects

This update affects agencies using snapshots, particularly those provisioning SaaS V1 and V2 accounts. If you enable SaaS for sub-accounts and apply snapshots, this change matters to you. HighLevel has not confirmed who is specifically affected beyond this.

What changed

When enabling SaaS for a sub-account and attaching a snapshot, the system now checks for potential conflicts with existing customizations. If conflicts are detected, a warning message is displayed before any changes are made. Users are given the option to either keep their existing assets or overwrite them with the snapshot's version. If no conflicts are found, the snapshot applies as it did previously. This new functionality applies to both SaaS V1 and V2 accounts. For bulk SaaS enablement, existing assets are automatically protected by default. HighLevel has not confirmed if attaching a snapshot is available for bulk SaaS enablement yet. HighLevel has not confirmed the rollout status, limits, or plan gating for this feature.

Where to find it

HighLevel has not confirmed the exact location within the product. Based on the description, this functionality will likely appear during the process of enabling SaaS for a sub-account and attaching a snapshot, specifically when a conflict between the snapshot and existing sub-account assets is detected. It will manifest as an additional step or prompt during that workflow.

How agencies will use this

Consider an agency owner setting up a new SaaS V2 client, 'Acme Marketing,' through their HighLevel dashboard. They enable SaaS for Acme's sub-account. Previously, if they applied a standard snapshot containing pre-built funnels, forms, or custom fields, it would simply overwrite anything Acme's team might have already created or modified within their new sub-account. Now, when the agency owner goes to attach a snapshot, HighLevel will scan Acme's sub-account for any existing assets that match names or types within the snapshot. If Acme's team has, for example, already built a custom 'Lead Capture' form with their own branding, and the snapshot also contains a form named 'Lead Capture,' the agency owner will see a warning. They can then choose to keep Acme's custom 'Lead Capture' form, thereby preserving their client's work, or overwrite it with the agency's standardized snapshot version. This prevents accidental data loss or overwrites when standardizing client accounts.

Our take

This is a practical, albeit standard, quality-of-life update. It addresses a specific pain point around snapshot management and client customization. It's not a major release, but it shows HighLevel is refining core processes. This should reduce support tickets related to accidental overwrites. Agencies should be aware of it, but it doesn't fundamentally change how you operate this week.