Quick start
- Name Everything Clearly – “Onboarding – Welcome Email” beats “Email #3.”
- Add Descriptions in Workflows – every workflow lets you add notes, use them.
- Record Loom Videos – show the logic behind complex automations.
Follow the detailed steps below to complete the setup.
You ever open an old snapshot and think, “Wait… who built this? And why?”
Yeah, been there.
Snapshots are one of the most powerful tools inside HighLevel. They let you duplicate entire systems, launch client accounts in minutes, and standardize your agency’s processes.
But here’s the truth: most people treat snapshots like magic buttons instead of living systems.
And when you skip documentation, you’re not building a system, you’re building chaos that multiplies every time you hit “load snapshot.”
Let’s fix that. 👇
What a Proper Snapshot Actually Includes
If you want your snapshots to scale (and be usable by anyone on your team), you can’t just save workflows and call it a day.
A complete, functional snapshot should include:
✅ Workflows – with clear naming conventions that actually describe what they do.
✅ Custom Fields – all organized and labeled so you’re not hunting for “custom_field_47.”
✅ Email & SMS Templates – tied to the right automations and tagged by purpose.
✅ Form & Funnel Assets – tested for lead capture and trigger flow.
✅ Descriptions & Instructions – inside notes or Loom videos explaining logic and intended use.
When every asset is documented and labeled, your team can understand it at a glance, and your future self will thank you six months from now.
The Problem: “It Works on My Account” Syndrome
Here’s the trap I see agencies fall into all the time:
They set up everything perfectly inside one subaccount, test it, love it.
Then they snapshot it, and boom. Something breaks.
Maybe the triggers didn’t map correctly. Maybe a pipeline didn’t carry over. Maybe an email template decided to go rogue.
The cause? Missing documentation and untracked dependencies.
Workflows don’t exist in isolation, they rely on forms, calendars, triggers, tags, and other elements.
If you don’t document those relationships, every migration becomes a guessing game.
Pro tip: Keep a running “Snapshot Dependencies” doc that lists:
- Which workflows connect to which triggers
- Which pipelines and tags each workflow depends on
- Which assets (forms, calendars, funnels) are tied to those workflows
That one doc can cut your setup time in half and prevent those “Why isn’t this firing?” moments.
Documentation = Scalability
Let’s be real: systems don’t scale, documentation does.
When you document your snapshots, you make it possible for:
👥 New team members to deploy and customize without breaking things
🧠 Your clients to understand how their system works (and appreciate your expertise)
🚀 You to replicate success faster, without rebuilding every time
It’s not about creating a “perfect” process.
It’s about creating a repeatable one.
The Best Way to Document Your Snapshots
If you’re not sure where to start, here’s my go-to process:
- Name Everything Clearly – “Onboarding – Welcome Email” beats “Email #3.”
- Add Descriptions in Workflows – every workflow lets you add notes, use them.
- Record Loom Videos – show the logic behind complex automations.
- Create a Snapshot Index – a simple Notion or Google Doc that lists every major asset, what it does, and where it lives.
- Version Control Your Snapshots – label updates (v1.0, v1.1, v2.0) and note what changed each time.
When your systems are documented this way, onboarding new clients (or staff) becomes plug-and-play instead of panic-and-pray.
Pro Tip: Build Snapshots Like You’ll Sell Them
Even if you’re not reselling snapshots now, build them as if you will someday.
That means clean naming, clear documentation, and scalable logic.
Because one day, that same system might turn into your next big product.
Pro Tip: Build Snapshots Like You’ll Sell Them
Even if you’re not reselling snapshots now, build them as if you will someday.
That means clean naming, clear documentation, and scalable logic.
Because one day, that same system might turn into your next big product.
Because when your snapshots are documented, your agency isn’t just growing, It’s scaling on purpose. 🚀
Frequently Asked Questions
What a Proper Snapshot Actually Includes?
If you want your snapshots to scale (and be usable by anyone on your team), you can’t just save workflows and call it a day. A complete, functional snapshot should include:✅ Workflows – with clear naming conventions that actually describe what they do.✅ Custom Fields – all organized and labeled so you’re not hunting for “custom_field_47.”✅ Email & SMS Templates – tied to the right automations and tagged by purpose.✅ Form & Funnel Assets – tested for lead capture and trigger flow.✅ Descriptions & Instructions – inside notes or Loom videos explaining logic and intended use. When every asset is documented and labeled, your team can understand it at a glance, and your future self will thank you six months from now.
What should I know about the Problem: “It Works on My Account” Syndrome?
Here’s the trap I see agencies fall into all the time: They set up everything perfectly inside one subaccount, test it, love it. Then they snapshot it, and boom. Something breaks. Maybe the triggers didn’t map correctly. Maybe a pipeline didn’t carry over. Maybe an email template decided to go rogue. The cause? Missing documentation and untracked dependencies. Workflows don’t exist in isolation, they rely on forms, calendars, triggers, tags, and other elements.If you don’t document those relationships, every migration becomes a guessing game. Pro tip: Keep a running “Snapshot Dependencies” doc that lists: Which workflows connect to which triggers Which pipelines and tags each workflow depends on Which assets (forms, calendars, funnels) are tied to those workflows That one doc can cut your setup time in half and prevent those “Why isn’t this firing?” moments.
What should I know about documentation = Scalability?
Let’s be real: systems don’t scale, documentation does. When you document your snapshots, you make it possible for:👥 New team members to deploy and customize without breaking things🧠 Your clients to understand how their system works (and appreciate your expertise)🚀 You to replicate success faster, without rebuilding every time It’s not about creating a “perfect” process. It’s about creating a repeatable one.
Start Your HighLevel Free Trial
Browse all GoHighLevel guides · Marketing.