Disclosure: some links in this article are affiliate links. If you start a GoHighLevel trial through one of them I may earn a commission, at no extra cost to you.
Snapshots are the single biggest time-saver in GoHighLevel, and the single biggest source of “why is nothing working” panic. Those two facts have the same cause: a snapshot copies configuration, not connections.
Everything you built gets recreated in the new account. Almost nothing you connected comes with it. Once you understand that one sentence, every strange thing a freshly imported snapshot does starts making sense.
What a GoHighLevel snapshot actually is
A snapshot is a template of a sub-account. You take one that is set up the way you like, save it as a snapshot at agency level, and then load it into new sub-accounts so you are never rebuilding the same pipeline and follow-up sequence for the fifteenth time.
What comes across is the structure and the assets:
- Automation: workflows, triggers, AI agents and Brand Voice
- CRM and data: custom fields, pipelines, tags, custom objects
- Marketing: funnels, forms, emails, blogs, campaigns, templates
- Calendars: calendars, services, resources and categories
- Advertising: Google, Meta and LinkedIn campaign structures
- Memberships: courses, webinars, certificates, products
- Plus: dashboards and custom reports, design kits and brand colours, knowledge bases and contracts, review settings, WhatsApp templates, and WordPress sites
That is a lot, and it is why snapshots turn a two-day onboarding into a twenty-minute one. You need at least a Starter plan to have sub-accounts to build them from, and an agency-level plan if you intend to deploy them across many clients. If you are still working out which tier you need, I have broken that down in GoHighLevel plans and pricing. If you do not have an account yet, you can start a 14 day trial here.
What does not transfer
This is the list that matters, and it is the one most snapshot tutorials skip.
- Contacts and conversation history. Snapshots are not a data migration tool. No contacts, no messages, no appointments.
- Integrations and Stripe connections. Every OAuth connection has to be re-authorised in the new account.
- Phone numbers. Including numbers used for Voice AI.
- Third-party licences. Anything requiring re-authentication comes across unauthenticated.
- Private dashboards and reputation data.
- Contact-to-contact associations.
None of that is a bug. A snapshot is a blueprint, not a moving van.
The post-import checklist
Here is the part that saves you the afternoon. Work through this in order, because several items depend on the ones above them, and do not send a single test message until you have finished.
- Fill in the custom values. This is the most common cause of a snapshot that appears broken. Workflows, emails and funnel pages reference custom values, and those import empty. Every message that references one will send with a blank where the business name should be. Do this first, before you look at anything else.
- Reassign users. Workflow steps that assign a task, and calendars that route to a team member, were pointing at a user who does not exist in this account. They now point at nobody. Go through every calendar and every assignment step.
- Reconnect the calendars. The calendar configuration imported. The Google or Outlook connection behind it did not. Each user reconnects their own, and until they do, availability will be wrong rather than obviously broken, which is worse.
- Sort the phone number and A2P. There is no number in the new account, so every SMS step will fail. Provision a number, then complete A2P 10DLC registration before you test. Registration takes time and can be rejected, so start it early rather than discovering it on launch day.
- Rebuild email authentication. Your templates came across. Your verified sending domain did not. SPF, DKIM and DMARC need setting up again, along with the tracking subdomain. The tracking subdomain in particular fails silently: mail appears to send, and quietly lands in spam.
- Reconnect payments. Stripe and PayPal are disconnected, so order forms and invoices will take nothing. If the snapshot includes a membership or course, this is the step that stops it selling.
- Re-authorise every integration. Facebook, Google, TikTok, Zapier, anything with an OAuth handshake. Ad campaign structures may have imported, but they are not connected to an ad account.
- Point the domains. Funnels and websites imported without a domain, or still referencing the source account’s. Assign the new domain, then click through every page.
- Check trigger links and redirects. Anything hard-coded to an old URL is now sending people to someone else’s funnel, or to a 404.
- Look at the funnel pages with your eyes. Images referenced from the source account’s file library can come across broken. Nothing will warn you. Load each page.
- Then test, with a fresh contact. Not one you have already run through a workflow, because re-entry rules will make it look like the automation is not firing when in fact it is refusing to run twice.
Roughly forty minutes of work, and every one of those items has generated a support ticket somewhere this week.
How to create a snapshot
Set up one sub-account exactly as you want it, then from agency settings create a snapshot from that account and choose which asset types to include.
Two things worth doing while you build it, because they cost nothing now and hours later:
Put every client-specific string in a custom value. Business name, phone, address, booking link, sender name. If it is hard-coded into a workflow or an email, you are editing thirty steps per deployment instead of filling in a form once.
Name things so future you can navigate them. A snapshot with forty workflows called “Workflow copy 3” is nearly unusable by anyone other than its author, including you in six months.
How to import one
Import into a new, empty sub-account wherever you can. Snapshots do not merge cleanly, and loading one on top of an account that already has pipelines and custom fields is how you end up with duplicates and half-connected automations that are harder to untangle than a rebuild.
If you are importing a snapshot someone shared with you by link, note that shared links can be capped on the number of imports, so it is worth confirming you have a spare use before you plan a client launch around it.
The dangerous bit: pushing updates
You can push an updated snapshot to sub-accounts that already use it. This is genuinely useful and it is also the fastest way to destroy a client’s customisations, because the push can overwrite what they changed after deployment.
Never push to live client accounts first. Push to a test sub-account, confirm what it actually changed, and only then roll it out. If the client has built anything themselves since deployment, tell them before you push, not after.
Bought snapshots versus building your own
There is a market in prebuilt niche snapshots, and some are excellent. The honest test is whether you understand what is inside it.
A snapshot you did not build is a system you cannot debug. When a workflow misfires for a client at 8pm, you either know why or you are reverse-engineering somebody else’s logic on a live account. Buying one to learn from and then rebuilding it in your own conventions is usually the better path than deploying it as-is to twenty clients.
Whatever you use, apply the post-import checklist above. A bought snapshot has exactly the same disconnected integrations as one you made yourself.
Frequently asked questions
Do contacts come with a snapshot?
No. Snapshots carry configuration only. Contacts, conversations and appointments have to be imported separately.
Can I import a snapshot into an account that already has data?
You can, and it usually creates a mess. Duplicated pipelines and custom fields, and automations pointing at the wrong copies. Import into an empty sub-account whenever the choice is yours.
Why are my snapshot’s emails sending with blanks in them?
Empty custom values. The templates reference values that did not carry across with content. Fill them in and resend.
Why is my snapshot not sending any SMS?
Almost always no phone number provisioned, or A2P 10DLC registration incomplete. The workflow is running correctly and has nothing to send through.
Will pushing a snapshot update overwrite client changes?
It can. Test the push on a spare sub-account first and warn the client before rolling it out.
What plan do I need to make snapshots?
You need sub-accounts, so Starter at minimum, and realistically an agency-level plan if you are deploying across clients. The plans breakdown covers where the line sits.
The short version
A snapshot moves what you built and none of what you connected. Fill the custom values, reassign the users, reconnect the calendars, sort the number and A2P, redo email authentication, reconnect payments and integrations, point the domains, then test with a fresh contact. Do that in order and snapshots go back to being the best feature in the platform.
More GoHighLevel fixes in Troubleshooting, or start a 14 day GoHighLevel trial if you are still deciding.