How to install a GoHighLevel snapshot without breaking anything

The import takes four minutes. Everything that goes wrong afterwards is something that could have been checked in the twenty minutes before it. This is the order that keeps you out of trouble.

Before you import

1. Decide which sub-account, and be honest about it

The safest destination is a brand new, empty sub-account. No existing workflows, no existing forms, nothing listening for the same triggers.

Importing into a busy account is possible, but understand what you are agreeing to: if you already have a workflow triggered by “form submitted” and the snapshot adds another one triggered by the same form, both will run. The contact gets two welcome texts and lands in two pipelines. Nobody notices until a customer mentions it.

If you must import into a live account, list every existing workflow trigger first. That list is your conflict map.

2. Submit A2P registration now, not later

In the US, business SMS requires A2P 10DLC registration. Carrier approval takes anywhere from a day to well over a week and there is nothing you or your vendor can do to speed it up. Submit it before you import so the waiting happens in parallel with your setup rather than after it. The brand and campaign registration sequence is worth reading first, because a campaign rejected for sample messages that do not match its stated use case restarts the clock rather than pausing it.

3. Verify your sending domain

Email authentication is DNS, and DNS propagation is slow enough to ruin an otherwise smooth afternoon. Add the records at the same time you submit A2P.

4. Read the install notes properly

Any snapshot worth money ships with a document listing the custom values, the calendars, the integrations and the assumptions. Read it before you import so you know what you are looking at when it lands.

Importing

1. Open the share link the vendor sent, while logged into GoHighLevel.
2. Choose the destination sub-account.
3. Confirm the import.
4. Wait. Large snapshots take a few minutes and the interface is not always dramatic about telling you it is finished.

Then reload the sub-account. Assets sometimes do not appear in the list until you do.

The eleven checks before you go live

This is the part that separates a working import from a demo.

1. Custom values. Open Settings, then Custom Values, and fill every one. Business name, address, booking link, offer terms, review link, sender name, support number. A single empty value shows up in a customer-facing message as a gap. Fill the handful that appear in every message first, then send one test through the longest sequence, which is the twenty minute order rather than the afternoon one.

2. Calendars. Every imported calendar has no owner, because users do not travel. Assign the right user, set real availability, set the buffer, set the notice period. A calendar with default availability will happily book someone for 6am on a Sunday.

3. Phone number. Connect a number to the sub-account and confirm the workflows are sending from it. Send yourself a test.

4. Sending email. Send a test email through a workflow, not through the template preview. The preview does not prove authentication works.

5. Workflow triggers. Open each workflow and read the trigger. Confirm it points at the imported form or calendar rather than something that no longer exists. Broken references are the most common import artefact.

6. Publish state. Imported workflows often land as draft. A draft workflow does absolutely nothing and gives you no warning. Check every one.

7. Pipeline stages. Rename them to your language. “Quoted” and “Awaiting decision” mean specific things in your business, and generic stage names quietly stop your team using the board. A crate built for one trade already speaks that trade: the roofing contractor crate arrives with adjuster and supplement stages, the dental practice crate with treatment plan and recall stages. Rename what does not match, but do not flatten the ones that do.

8. Forms and their redirects. Submit every form yourself. Confirm it lands where it should, applies the right tag, and shows the right thank-you page.

9. Every message, read as a customer. Read the SMS and email copy start to finish. Generic snapshot copy is the fastest way to sound like a template. Rewrite anything that does not sound like you, and delete any claim you cannot back.

10. Opt-out and compliance. Confirm your SMS messages carry an opt-out instruction and that your sub-account honours it. Confirm your emails carry a physical address and an unsubscribe link. This is not optional anywhere.

11. A full live test lead. Submit the form as a stranger would. Use a real phone and a real inbox. Follow the whole path: the instant reply, the reminder, the branch when you reply, the branch when you do not. Then check the contact record shows what you expect.

The tests almost everyone skips

Three paths that only fail in production:

• The reply path. Reply to the first automated text. The sequence should stop. If it keeps sending, you have a stop condition missing, and you will find out from an annoyed customer.
• The after-hours path. Submit a form at 11pm. Confirm the message you get is the after-hours one rather than “we will call you in five minutes”.
• The duplicate path. Submit the same form twice with the same email. Confirm you do not get two parallel sequences.

After go-live

Watch the first ten real leads individually. Open each contact record and read the timeline. Every import has one thing wrong with it, and it is always visible in the first ten contacts and invisible in aggregate reporting.

After a fortnight, go back and delete what you are not using. An imported snapshot usually contains flows for scenarios you do not run, and leaving them in place makes the account harder to reason about a year from now, usually for someone who is not you.

If it is broken and you cannot see why

In order of likelihood: the workflow is in draft, a custom value is empty, the trigger points at a deleted asset, the calendar has no owner, the number is not connected, or two workflows are fighting over the same trigger.

That list covers the overwhelming majority of “the snapshot does not work” support tickets, including the ones where the snapshot was fine. Work it in that order rather than in the order the symptom suggests, because the cheap checks eliminate most of the field in under a minute. The full symptom by symptom diagnostic order picks up where this list stops, including how to prove a workflow ran without waiting on a timer.

Doing it yourself, or not

The import is four minutes and the eleven checks are about an hour. That hour is the part only somebody who knows the business can do, which is why it is also the part most often skipped.

If it is not going to happen this week, the fit-out service does the import, the checks, the message rewrite and the live test as one job, and every crate carries 12 hours of installation support to be used within 14 days of purchase whether or not you book it.

Ready to load one? The catalog is here, the pre-import checklist is worth printing, and the home and trade aisle is the busiest shelf if you are looking for a place to start.