How to Import a GoHighLevel Snapshot Into a Sub-Account (and What to Check After)

A GoHighLevel snapshot is a packaged copy of a sub-account's assets: workflows, pipelines, calendars, forms, funnels, tags, custom fields and more. Importing one is the fastest way to stand up a working system for a new client or your own business. This guide covers the two ways to import a snapshot, what GHL does with conflicts, and the five things that break most often after an import.

Before you import: you need an agency login

Snapshots live at the agency level, not inside a sub-account. If you only have a sub-account login (the kind a client usually gets), you cannot import snapshots. Log in with the account that can see Agency View in the top-left switcher.

Step 1: Add the snapshot to your agency

From a share link

1. Log in to GoHighLevel at the agency level.
2. Open the share link you were given (it usually looks like affiliates.gohighlevel.com/?share=...).
3. GHL shows a confirmation with the snapshot name. Click Yes, import.
4. Go to Agency → Account Snapshots → Imported Snapshots. The snapshot is now listed there.

From the Marketplace

Marketplace snapshots are added the same way after purchase: they appear under Imported Snapshots once the purchase completes.

Step 2: Load it into a sub-account

You have two options, and the right one depends on whether the account already exists.

Option A: Create a new sub-account from the snapshot

1. On the snapshot row, click the + icon ("Create sub-account from snapshot").
2. Fill in the business name, address and time zone. These populate {{location.name}} and the other merge fields the snapshot's messages use.
3. Click Save. The sub-account is created with everything in the snapshot already inside.

Option B: Load into an existing sub-account

1. On the snapshot row, click the ⋮ menu → Load Snapshot.
2. Pick the sub-account.
3. Review the asset list. Leave everything checked unless you know you want to exclude something.
4. If GHL flags conflicts (an asset with the same name already exists), choose Skip to keep your existing version or Override to replace it with the snapshot's version. When in doubt, Skip; you can always load again later.
5. Click Proceed. "Snapshot loaded" usually appears within a minute.

Step 3: The five things to check after every import

1. Workflows are in Draft

Snapshots import workflows as Draft. Open Automation → Workflows and publish each one. This is the most common reason an imported system "doesn't work."

2. Phone number and A2P registration

Phone numbers are never included in a snapshot. Buy or assign a number under Settings → Phone Numbers, set it as the default for outbound SMS, and complete A2P 10DLC registration in Trust Center. Until A2P is approved, SMS steps will run but carriers will drop the messages.

3. Calendars and booking links

If the snapshot includes a calendar, connect it to your Google or Outlook calendar and set availability. Then search the workflows for any booking-link placeholder (a well-built snapshot uses a placeholder like [Add your booking link] rather than the builder's own link) and replace it with your calendar's scheduling link. Also open any appointment-based trigger and make sure it points at your calendar.

4. Forms, chat widget and trigger links

Workflows that trigger on a form submission or chat message may reference the snapshot's forms. If you use your own forms, open the trigger and select them. Check that the chat widget is installed on your site if a workflow depends on it.

5. Anything hardcoded

Skim each SMS and email step for a business name, signature or link that belongs to whoever built the snapshot. Good snapshots use {{location.name}}, {{contact.first_name}} and {{user.first_name}} instead of literal text, and assign tasks to "Contact's assigned user" rather than a named person.

Step 4: Run a live test

• Call the GHL number from your cell and let it ring out. Check the contact was created, the text went out, and the task and notification fired.
• Book a test appointment and confirm the confirmation and reminder messages.
• Submit your website form once and check the follow-up text.

Frequently asked questions

Can I load one snapshot into many sub-accounts?

Yes. Once it is in Imported Snapshots you can load it into as many sub-accounts as you like. Agencies do this for every new client.

Does importing a snapshot overwrite my existing workflows?

Only if an asset has the exact same name and you choose Override at the conflict step. Choosing Skip leaves your version alone.

Will an imported workflow start sending messages immediately?

No. Workflows arrive in Draft. Nothing sends until you publish them, and SMS will not deliver until A2P is approved.

I got the snapshot but I only have a sub-account login. What now?

Ask whoever owns the agency account to import the share link and load it into your sub-account, or have the snapshot installed for you. Done-for-you installation is available on Fiverr.

Related guides

• GoHighLevel missed call text back: step-by-step setup
• 12 missed call text back templates that get replies