GoHighLevel Agency TrainingA Dynamic AI HUB training resource
Snapshots

Snapshot basics

Reusing configuration across subaccounts.

Advanced30 min

Purpose

This SOP explains how to think about snapshots as reusable configuration tools. A snapshot can help reuse parts of a setup across subaccounts, locations, or client accounts. It can save time when the source system is clean and documented. A snapshot can also spread mistakes quickly. If the source account has messy pipelines, unclear tags, broken workflows, hardcoded values, or untested automations, the snapshot may duplicate those problems into every account where it is applied. The purpose of this SOP is to help you treat snapshots as controlled deployment tools, not shortcuts around planning.

When to Use This SOP

  • You want to reuse setup from one account in another account
  • You are preparing a template account
  • You are building a standard client onboarding setup
  • You inherited a snapshot and need to review it
  • You want to create a clean repeatable system
  • You need to apply similar structure across multiple accounts

Before You Start

  • Do not snapshot a messy account.
  • Before creating or applying a snapshot, the source account should be reviewed for pipelines
  • Tags
  • Custom fields
  • Custom values
  • Calendars
  • Workflows
  • Forms
  • Campaigns
  • Email templates
  • Documents
  • Reporting setup
  • Hardcoded business information
  • Old test assets
  • Disabled or temporary workflows
  • A snapshot should only package structure that is clean enough to reuse.

Step-by-Step Procedure

  1. 1
    Define the purpose of the snapshot

    Write down what the snapshot is supposed to do.

    Examples:

    • Standard new client setup
    • Local service business starter structure
    • Appointment-based sales process
    • Internal demo account
    • Training account
    • Industry-specific starting point

    If the snapshot has no clear purpose, it will become a junk drawer.

  2. 2
    Review the source account

    Open the source account and review the major assets.

    Check:

    • Pipelines are clean and named clearly
    • Stages have clear meanings
    • Tags follow the naming convention
    • Custom fields are useful and not one-off clutter
    • Custom values are generic enough or clearly need updating
    • Calendars are not tied to the wrong user
    • Workflows are named clearly
    • Temporary workflows are disabled or removed
    • Forms have clean fields
    • Campaigns are not connected to the wrong audience
    • Email templates do not contain outdated or client-specific language

    Do not create the snapshot until the source account passes review.

  3. 3
    Remove client-specific or account-specific information

    Look for anything that should not be copied into a new account.

    Examples:

    • Client name
    • Client address
    • Personal phone numbers
    • Personal booking links
    • Hardcoded support emails
    • Brand-specific offers
    • Old logos
    • Test contacts
    • Old form links
    • Internal notes that do not apply
    • Workflow messages referencing the wrong business

    Where possible, replace reusable business information with custom values or placeholders.

  4. 4
    Review workflows carefully

    Workflows are the highest-risk part of a snapshot.

    Before including or applying them, check:

    • Are they turned off by default if they need account-specific review?
    • Are triggers too broad?
    • Do they use contact-created triggers?
    • Do they depend on tags or fields that will exist in the destination account?
    • Do they send email or SMS immediately?
    • Do they reference the right pipeline stages?
    • Do they contain hardcoded links?
    • Do they have stop conditions?
    • Are unsubscribe and do-not-contact safeguards respected?

    Do not let a snapshot activate unreviewed automations in a live account.

  5. 5
    Review calendars and users

    Calendars may not transfer cleanly because they often depend on users, availability, external calendar connections, and meeting ownership.

    After applying a snapshot, confirm:

    • Calendar owner is correct
    • Availability is correct
    • External calendar sync is reviewed
    • Booking form fields are correct
    • Reminder messages are correct
    • Calendar links are tested
    • Calendar-to-workflow logic still works

    Never assume calendar settings are ready after applying a snapshot.

  6. 6
    Document what the snapshot includes

    Create a snapshot documentation note.

    Include:

    • Snapshot name
    • Purpose
    • Source account
    • Date created or reviewed
    • Pipelines included
    • Tags and fields included
    • Calendars included
    • Workflows included
    • Forms included
    • Campaigns included
    • Custom values that must be updated
    • Assets that must be tested after applying
    • Known limitations

    This documentation is what makes the snapshot maintainable.

  7. 7
    Apply the snapshot to a test account first

    Before using a snapshot on a real account, apply it to a test or staging account when possible.

    After applying, test:

    • Pipeline structure
    • Tags and fields
    • Workflows
    • Calendar links
    • Forms
    • Campaigns
    • Custom values
    • Reporting views
    • Any links inside messages

    Do not judge snapshot quality by whether it imported. Judge it by whether the destination account works correctly after review.

  8. 8
    Review the destination account after applying

    After applying a snapshot to the destination account, complete a post-application review.

    Check:

    • Business identity is correct
    • Custom values are updated
    • Users are assigned correctly
    • Calendars are connected correctly
    • Workflows are reviewed before activation
    • Forms send to the correct path
    • Email and SMS settings are safe
    • Test contacts behave correctly
    • Reporting uses the right pipelines and sources

Checks Before You Finish

  • ✓The snapshot purpose is documented
  • ✓The source account was reviewed
  • ✓Client-specific information was removed or replaced
  • ✓Workflows were reviewed for risk
  • ✓Custom values needing update are listed
  • ✓Calendar and user dependencies are documented
  • ✓Snapshot contents are documented
  • ✓A test application was completed where possible
  • ✓Destination account was reviewed after applying
  • ✓No unreviewed automations are live

Common Mistakes

Watch for these
  • Creating a snapshot from a messy account
  • Assuming snapshots transfer perfectly
  • Copying hardcoded client information into new accounts
  • Leaving test workflows active
  • Forgetting to update custom values
  • Forgetting to reconnect calendars
  • Applying snapshots directly to live client accounts without review
  • Overpromising exact portability
  • Treating snapshots as a replacement for planning

Related SOPs

← Back to SOP Library