How to import a snapshot into GoHighLevel

A GoHighLevel snapshot is a package of a sub-account: funnels, websites, workflows, pipelines, calendars, forms, surveys, triggers, custom fields, custom values and tags. Importing one is genuinely a two-minute job. The reason people find it stressful is that almost nobody tells you what happens to the sub-account you load it into, or what to check before the first lead arrives.

Before you start: three things to have ready

• Agency-level access. Snapshots load from the agency view, not from inside a sub-account.
• A destination sub-account. Create a fresh one if you are testing; you cannot cleanly un-load a snapshot.
• The share link. Every snapshot we sell is delivered as a link that looks like app.gohighlevel.com/?share=…

Step by step

1. Log into GoHighLevel as the agency, not as a sub-account user. If you are in a sub-account, use the account switcher in the top left first.
2. Open the share link in the same browser session. GoHighLevel will show you the snapshot name and ask where to load it.
3. Choose the destination sub-account from the dropdown, or create a new one from the same screen.
4. Confirm. Loading runs in the background and takes between thirty seconds and four minutes depending on how many workflows the snapshot carries.
5. Wait for the confirmation email or refresh the sub-account. Assets appear progressively, so a half-loaded funnel list is normal for the first minute.

What a snapshot does and does not overwrite

This is the question that stops most people. Loading a snapshot adds assets alongside what is already in the sub-account. It does not delete your existing funnels, contacts or workflows.

What it can do is collide on names. If your sub-account already has a workflow called "Nurture" and the snapshot brings one called "Nurture", you now have two, and six weeks later nobody knows which is live. Every snapshot we build prefixes its assets with the funnel name for exactly this reason, and if you are importing a snapshot from elsewhere it is worth renaming your existing assets before you load.

Custom values are the exception worth watching. If the snapshot ships a custom value with the same key as one you already use, the snapshot version wins.

The eight-point check before you send traffic

A freshly loaded snapshot is not a live funnel. Run through these eight before a single click reaches it, in this order.

1. Custom values. Open Settings → Custom Values and replace every placeholder. This is where the business name, offer price, calendar link and support email live, and it is the single largest source of "why does the email say Example Co".
2. Domain and funnel URLs. Point the funnel at your own domain and check the path on every step, not just the first page.
3. Calendar connection. If the funnel books appointments, connect the calendar and set real availability. A snapshot cannot carry your Google account.
4. Payments. Order forms need a payment provider connected on the sub-account. Stripe and NMI support one-click upsells; PayPal does not.
5. Email and SMS sending. Confirm LC Email or your own Mailgun is connected, and that the sub-account has a phone number with SMS enabled.
6. Workflow publish state. Imported workflows arrive in draft. Every one of them. Publish the ones you want live and leave the rest in draft deliberately.
7. Test submission. Fill in the form yourself with a real email and phone number. Walk the whole funnel including the thank-you page.
8. Clean up the test. Delete the test contact so your first real conversion is genuinely your first.

The mistake nearly everyone makes

Publishing every imported workflow at once. A snapshot with six workflows will usually have two that only apply to a variant of the funnel you are not running — a payment-plan branch, a waitlist path, a downsell. Publishing them all means a contact can end up in two sequences at the same time and receive two different emails an hour apart.

Publish the core path first, run one real lead through it, then publish the branches one at a time.

How long it should take

If configuration is taking you an hour, it is almost always because the copy is being rewritten at the same time. Separate the two jobs: get the funnel technically live first, then rewrite it.