What is a GoHighLevel snapshot?

A snapshot is the closest thing GoHighLevel has to a project template. It is a saved copy of the structure of a sub-account, and loading it into another sub-account recreates that structure in a few minutes.

That word, structure, is doing all the work in this definition. It is also where almost every misunderstanding starts.

What transfers

When you load a snapshot into a sub-account you get:

• Funnels and websites, including every step, every page and the design on them
• Workflows, with their triggers, filters, wait steps and actions intact
• Pipelines and stages, including any automation attached to a stage
• Calendars, with availability rules, buffers and reminder configuration
• Forms and surveys, including conditional logic
• Custom fields and custom values, which is what makes everything else portable
• Email and SMS templates
• Triggers, tags and campaign structures

That set is enough to rebuild an entire operating account. It is why a well-built snapshot can turn a two-week onboarding into an afternoon.

What does not transfer

This is the part worth reading twice, because it is the single most common false expectation:

• Contacts. None of them.
• Conversation history, including SMS threads, emails and call recordings.
• Opportunities already sitting in a pipeline.
• Appointments already on a calendar.
• Payments, invoices and transactions.
• Connected integrations and credentials. Your Stripe key, your Google Calendar connection, your phone numbers and your A2P registration all belong to the sub-account, not the snapshot.
• Media library files in most cases, so images referenced by a funnel may need re-uploading.

If somebody sells you a snapshot on the promise that it will move your customer data, they have either misunderstood the product or they are being careless with the truth.

Snapshot, template, or clone

Three words get used interchangeably and they mean different things.

A template is one asset. A funnel template is one funnel. An email template is one email. You can import a dozen of them and still have to wire them together yourself, which is where the time goes.

A snapshot is the whole structure with the connections intact. The form still feeds the workflow. The workflow still moves the pipeline stage. The calendar is still attached to the right funnel step. That connective tissue is roughly seventy percent of the build effort and it is exactly what a template pack leaves out.

A clone normally means duplicating a single asset inside the same account. Useful, but it does not cross the sub-account boundary.

When a snapshot is the wrong tool

Snapshots are not always the answer.

• You need data moved. Use an export and import, or a migration, not a snapshot.
• You want to push changes into live accounts. Loading a snapshot over a running sub-account can overwrite customisation. Ship changes deliberately, asset by asset, rather than hoping the import is polite about it.
• Your process genuinely differs per client. If every client build is different, a snapshot encodes a fiction and you will fight it. Fix the process first.

How to judge a snapshot before buying one

Ask three questions, and be willing to walk away if any answer is vague.

1. How many workflows, and are they named? A count with no names usually means empty shells. Ask for the list.
2. Is the copy written? A workflow with an unedited placeholder email is not a finished workflow, it is a diagram.
3. What does a new install actually require? A good seller can hand you the list of custom values you have to change. If nobody has written that list, nobody has installed it twice.

Everything we sell answers all three on the page, before you reach a checkout, because those are the questions we ask when we buy one.

The honest summary

A snapshot is a structure transfer. It saves the part of a build that is long rather than hard, it moves no customer data, and its value is entirely determined by how much thought went into the version you are importing. A bad snapshot is a folder of empty names. A good one is somebody else’s finished build, handed over.