A stuck or failed GoHighLevel snapshot import almost always falls into one of three categories: a full failure, a partial per-sub-account failure, or a "silent mismatch" where the import shows complete but assets are missing, and each one has a different fix. Retrying the entire import when only one sub-account failed wastes time and can create duplicate assets. This guide walks through how to diagnose which failure type you're dealing with and the exact steps to resolve it.
Quick Verdict: If the import never started or errored out immediately, retry it once before contacting support. If it pushed to multiple sub-accounts and only some failed, use Load History → "Retry All Failed" instead of re-running the whole snapshot. If the import shows "complete" but pages, funnels, or pipelines are missing, manually audit the asset counts against the source snapshot rather than assuming success. Most stuck imports resolve without needing a support ticket.
Why GoHighLevel Snapshot Imports Get Stuck or Fail
A snapshot in GoHighLevel is a packaged copy of a sub-account's configuration: pipelines, workflows, funnels, forms, custom fields, and more. Importing one into a new or existing sub-account involves moving a large bundle of interdependent assets in a single operation, and any single piece that can't be written cleanly can stall or interrupt the rest of the load.
Before troubleshooting, it helps to separate "the import is stuck" from "the import failed" from "the import finished but something's missing." These look similar from the user's side but require different fixes, which is why generic advice to "just retry" or "contact support" doesn't always work.
| Loaded | |
|---|---|
| Workflows and triggers | ✓ |
| Funnels, calendars, forms, emails | ✓ |
| Custom fields and custom values | ✓ |
| Contacts and appointments | ✕ |
| Conversations and reputation data | ✕ |
| Stripe connection and integrations | ✕ |
| Phone numbers and email-domain DNS | ✕ |
Source: HighLevel snapshot help articles, read October 18, 2026
The Three Types of Snapshot Import Failures
Most troubleshooting guides treat every stuck import the same way. In practice, HighLevel's own tooling (specifically the Load History and Snapshot Load Retry features) implies the platform itself distinguishes between failure types, and your fix should match.
| Failure Type | What It Looks Like | Fix |
|---|---|---|
| Full failure | Import never completes, shows an error, or the load appears stuck for the entire process | Retry the import once. If it fails again, contact HighLevel support. |
| Partial / per-sub-account failure | Snapshot pushed to multiple sub-accounts; some succeeded, others show a failed status in Load History | Go to Snapshots → Load History → open the load → click "Retry All Failed." This retries only the failed sub-accounts. |
| Silent asset mismatch | Import shows "complete" with no error, but pages, funnels, or pipelines from the source snapshot are missing or empty | Manually count and compare assets (pages, funnels, pipeline stages) in the imported sub-account against the source snapshot. |
Branch 1: Full Import Failure
A full failure means the import didn't complete at all: it errors out immediately, hangs indefinitely, or the sub-account shows no evidence that any assets were loaded.
HighLevel's official guidance for this scenario is straightforward: retry the import first. If the issue persists after a retry, contact HighLevel support (Source: HighLevel Support Portal, "How to Import Snapshots in HighLevel", which says to retry after confirming the share is still valid and to contact support if the problem continues). Don't skip the retry step.
If the retry also fails, check the specific error message before opening a ticket. One common error is "snapshot unavailable."
"Snapshot Unavailable" Error
This error means the snapshot you're trying to import no longer exists in a shareable state. HighLevel's import article gives two causes: the source snapshot may no longer exist or be available through that share, or the shared link is no longer valid.
The fix here isn't on your end. Contact the person or agency who originally shared the snapshot with you and ask them to confirm the snapshot still exists and that the share link (or marketplace listing) is still active. If they've since updated their template, ask for the current share link rather than reusing the old one.
Setting up a sub-account from scratch instead? The GoHighLevel setup guide gives the order of work.
Branch 2: Partial or Per-Sub-Account Failure
If you pushed a snapshot to multiple sub-accounts at once (a common workflow for agencies rolling out a template across several client accounts), it's possible for some sub-accounts to succeed while others fail. A single sub-account might time out or hit a permission conflict, while the rest of the batch loads normally.
HighLevel built a specific feature for exactly this situation: Snapshot Load Retry. Instead of re-pushing the entire snapshot to every sub-account again, which risks duplicating assets in the accounts that already succeeded, you can retry only the ones that failed (Source: HighLevel Support Portal, "Snapshot Load Retry", modified February 20, 2026). HighLevel notes that loads older than 48 hours can't be retried; after that window, create a new load.
Here's the process:
- Go to Snapshots in your agency-level view.
- Open Load History for the snapshot you pushed.
- Find the load that shows one or more failed sub-accounts.
- Click "Retry All Failed."
This retries the push only for the sub-accounts that failed the first time. The sub-accounts that already loaded successfully are left untouched, which avoids the duplicate pipelines, funnels, and workflows you'd risk by re-running the entire batch.
Branch 3: Silent Asset Mismatch (Shows Complete, But Assets Are Missing)
This is the failure type most people don't check for, because the import shows as successful. There's no error message and no failed status in Load History, but when you open the sub-account, something's missing: fewer pages than the source snapshot had, an empty funnel, or a pipeline with no stages.
This isn't a hypothetical edge case. A user in the GoHighLevel Skool community reported importing a 5-day-challenge snapshot that showed as complete but arrived with zero website pages, despite the source snapshot including a full page set. HighLevel's own Snapshot Push Update History article (modified November 13, 2024) states that "the asset level details might say Completed even if less than 100% of the assets loaded." Treat it as a known risk rather than an expected outcome.
Because the platform doesn't flag this automatically, the fix is a manual audit:
- Open the source snapshot's asset list (or the original sub-account it was built from, if you have access) and note the number of funnels, website pages, pipelines, pipeline stages, and workflows.
- Open the imported sub-account and count the same asset types.
- Compare the two. Any gap, especially an entire category showing zero, means part of the import didn't come through even though it reported success.
- If you find a gap, don't re-run the full snapshot import blindly. Try re-importing just the missing asset category if the snapshot sharing settings allow it, or contact HighLevel support with the specific discrepancy (source count vs. imported count) so they can investigate the load logs.
If the pipeline did not load as expected, rebuild it with the steps in GoHighLevel pipeline setup.
Asset Conflicts: Why an Import Can Appear Stuck Without Actually Failing
Sometimes what looks like a stuck import is actually the system waiting on you. When a snapshot includes assets that already exist in the destination sub-account, such as a pipeline stage with the same name or a funnel page that conflicts with an existing one, the import can pause and prompt you to choose "Override" or "Skip" for each conflicting item, as described in HighLevel's guide to loading snapshots into an existing sub-account (modified September 27, 2026).
Real user reports from the GoHighLevel Skool community describe exactly this pattern: the import appears frozen, but it's actually halted on an unanswered conflict-resolution prompt. If your import seems to be hanging, check for a modal or notification asking you to resolve asset conflicts before assuming it's broken. Resolve each prompt deliberately: override when you want the snapshot's version to win, skip when you want to preserve what's already in the sub-account.
Preventing Import Problems Before They Start
The current, redesigned HighLevel import flow gives you more visibility than earlier versions did. HighLevel's import article says a snapshot appears greyed out while processing is underway and that a shield indicator marks snapshots containing protected assets. "Assets protected" means the creator has restricted redistribution of those assets to other agencies; the agency that receives them can still load and reuse them (HighLevel's assets protected snapshots article, modified September 12, 2026).
Check for the shield indicator before importing, especially with third-party or marketplace snapshots, so you know the protection stays in place after import.
Two habits reduce most import headaches:
- Confirm the snapshot is still active with the sharer before starting a large rollout, especially for older share links.
- Do a test import into one sub-account first if you're planning to push the same snapshot to several accounts. This surfaces conflict prompts and asset gaps before you're troubleshooting across a whole batch.
Planning a med spa build? See what a med spa snapshot includes and leaves out.
Sources and further reading
Checked at the time of writing; prices, features and policies change. Checked 2026-10-19.
- HighLevel: How to Import Snapshots in HighLevel (retry guidance, unavailable shares, assets protected indicator; modified September 12, 2026)
- HighLevel: Snapshot Load Retry (Retry All Failed, 48-hour limit; modified February 20, 2026)
- HighLevel: Snapshot Push Update History (status can show Completed below 100% of assets; modified November 13, 2024)
- HighLevel: Load Snapshots into an Existing Sub-Account (Override or Skip conflicts; modified September 27, 2026)
- HighLevel: Assets Protected Snapshots (modified September 12, 2026)
Frequently Asked Questions
What does "snapshot unavailable" mean in GoHighLevel?
It means the snapshot you're trying to import is no longer accessible, usually because the original sharer deleted it, unpublished it, or the share link expired. Contact the sharer to confirm the snapshot still exists and get a current link.
How do I retry a failed GoHighLevel snapshot import?
For a full failure, simply retry the import from the same screen. For a partial failure across multiple sub-accounts, go to Snapshots → Load History, open the load, and click "Retry All Failed" to retry only the sub-accounts that didn't succeed.
Why did my snapshot import say complete but pages are missing?
This is a known, if uncommon, issue reported by users where an import reports success without transferring every asset. Manually compare page, funnel, and pipeline counts in the imported sub-account against the source snapshot to catch this.
Why is my GoHighLevel import stuck on a prompt?
The import may be waiting for you to resolve asset conflicts. If the snapshot includes a pipeline stage, funnel, or other asset with the same name as something already in the destination sub-account, the system pauses and asks you to choose "Override" or "Skip" for each conflict.
Should I re-import the whole snapshot if only one sub-account failed?
No, re-pushing the full snapshot to sub-accounts that already succeeded risks creating duplicate pipelines, funnels, and workflows. Use Load History's "Retry All Failed" option instead, which only retries the sub-accounts that didn't load successfully.
What is an "asset-protected" snapshot?
It's a snapshot containing assets whose creator has restricted redistribution to other agencies. HighLevel marks these snapshots with a shield indicator, and importing one does not remove its protection.
When should I contact GoHighLevel support about a stuck import?
Contact support if a full import fails again after you've already retried it once, or if a manual audit reveals a specific asset gap (with source and destination counts) that you can't resolve through a re-import or the Load History retry option.
For a second opinion on what loaded and what did not, our free GoHighLevel audit reads the account with you.
Need Help Fixing a Stuck Snapshot Import?
Snapshot imports across multiple sub-accounts, especially with custom pipelines, funnels, and workflow dependencies, can be difficult to troubleshoot without visibility into the load logs. If you're dealing with a stuck, failed, or incomplete import, contact us and we'll help you diagnose which of the three failure types you're facing and get it resolved.