How to load a snapshot into a GoHighLevel sub-account without breaking it

Loading a snapshot is one click. That click is also the reason a lot of agencies have accidentally texted a client’s entire contact list at two in the morning. The click is not the risk — everything around it is.

Here is the method we use on every install, in order.

1. Decide whether the destination account should be empty

If the sub-account is brand new, load away. If it is live, stop and answer one question: is anything in this account currently able to message a contact?

Loading a snapshot into a populated account does not merge intelligently. You get both versions of everything, both listening to the same triggers. Two workflows watching for an inbound SMS will both respond to an inbound SMS.

When the destination is live, the safer pattern is to load into a blank sub-account, compare, and move across only what you want.

2. Write the conflict list before you load

Open the destination account and list, on paper:

• pipelines with stages that will duplicate
• workflows that respond to the same trigger the snapshot uses
• tags that mean something different in each account
• calendars that share availability with a real person’s diary
• trigger links and form redirects pointing at the current account

That list takes fifteen minutes and prevents nearly every post-load surprise.

3. Load with sending disabled

Wherever the platform lets you, load first and publish messaging workflows last. If the snapshot arrives with workflows already published, the install itself can enrol existing contacts.

The practical order is: load, immediately unpublish anything that sends, configure, test, then publish in dependency order — housekeeping and tagging workflows first, message-sending workflows last.

4. Re-point everything that carries a URL

This is the step that silently breaks self-serve installs. Snapshots carry the structure of trigger links, form redirects, calendar embeds and webhook URLs, but the values often still reference the source account.

Walk through:

• trigger links
• form and survey redirect URLs
• calendar embed codes on any external site
• webhook URLs in workflows
• links inside email and SMS templates

Anything pointing at the account you built the snapshot in needs to point at the account you just built.

5. Fill the custom values before you test

A good snapshot puts every client-specific string in a custom value. That is only useful if you fill them in before the first test send, otherwise you will test a message that says “Hi from” followed by nothing and conclude the workflow is broken.

Our Agency Starter Kit ships thirty of these with a load sheet that lists them in the order they appear in the account, which is faster than hunting through the settings page.

6. Test on a real contact you control

Create a test contact with your own phone number and email. Then:

• submit every form
• book on every calendar
• trigger every entry point you can trigger manually
• mark an appointment as no-show
• reply to a message and confirm the sequence stops

The exit conditions are what you are really testing. Most sequences work. Far fewer stop correctly.

7. Publish in dependency order

Turn on tagging and housekeeping workflows first, confirm they behave, then publish the ones that send. If something is wrong, you would rather find out from a tagging error than from a message.

8. Write down what did not travel

Snapshots do not carry everything. Conversation history, some integration credentials, certain account settings and third-party auth stay behind. Write the list. Someone will ask about it in three weeks and the answer should not be a guess.

If this is your tenth install this month

Then the real fix is not a better checklist — it is a kit that was built to be installed repeatedly, with a load sheet that already knows which values to fill and which workflows to publish last. That is the whole premise of the snapshot catalog, and if you would rather not do it at all, snapshot installation is a service.

When it goes wrong anyway

Loads fail in six recognisable ways — missing permissions, an expired share link, partially failed assets, duplicate assets after a merge, an account where nothing works because credentials never travel, and an account that works but writes into somebody else’s CRM. There is a fixed diagnosis order that gets you to the cause in about ten minutes: GoHighLevel snapshot not loading.

And before the account goes live, run the full journey rather than a spot check — testing GoHighLevel workflows properly.