We Loaded a GHL Snapshot and Took Down a Client's Live Website

We pressed one button in GoHighLevel and a client's production website went dark.

No warning dialog. No confirmation prompt. No "are you sure?" Just a snapshot load, and the site that was ranking, generating leads, and running their business returned a 404.

This happened to us with Sooner State Haulers. Their site was live. It was indexed. It was bringing in calls. Then we loaded a snapshot onto their sub-account, and three things broke at once.

Here's exactly what went wrong and how to make sure it never happens to you.

What We Did

The task was simple. We needed to load a GHL snapshot onto the Sooner State Haulers sub-account. Snapshots are GoHighLevel's way of importing pre-built configurations: workflows, pipelines, funnels, calendars, and website templates.

We loaded the snapshot. It took about 30 seconds.

Then we checked the website.

Gone.

Three Things That Broke

1. The domain got stripped from the website.

The snapshot overwrote the domain assignment. Soonerstatehaulers.com was no longer pointed at their live site inside GHL. The domain was still in the account, but it wasn't connected to anything. Visitors hit a dead end.

2. The website path changed from / to /ai-generated-website.

Even after we reassigned the domain, the root URL still returned a 404. The snapshot had changed the website's URL path from / (root) to /ai-generated-website. So the real site was buried at soonerstatehaulers.com/ai-generated-website while the homepage showed nothing.

3. A junk AI-generated template appeared alongside the real site.

The snapshot injected its own template website into the account. Now there were two websites in the sub-account: the real one and a garbage placeholder. The domain was assigned to the wrong one.

All three of these happened silently. GHL did not show a single warning.

Why GHL Works This Way

GHL snapshots are full-account configuration imports. They don't merge. They overwrite.

When a snapshot includes website settings, it replaces the existing website settings. That means domain assignments, URL paths, and site structure all get swapped out. The snapshot doesn't check whether a live site is already running. It doesn't ask if you want to keep your current domain mapping. It just writes over everything.

There's no toggle to exclude website settings from a snapshot load. It's all or nothing.

This is a known behavior, not a bug. GHL designed snapshots for blank accounts. The problem is that nobody tells you that, and nothing in the UI stops you from loading one onto a live account.

The Safe Way to Load Snapshots

Never load a snapshot onto a sub-account with a live website.

Here's what we do now:

1. Create a blank sub-account. Load the snapshot there. No live site, no risk.
2. Cherry-pick what you need. Move the workflows, pipelines, or funnels you actually want into the production account manually.
3. If you must load onto an existing account, screenshot every website setting first. Document the domain assignment, the URL path, and which website is active. You'll need this to restore everything.
4. Check the website within 60 seconds of loading. Don't wait. Open the live URL in an incognito tab immediately after the snapshot finishes.

The 3 extra minutes of setup save you from 45 minutes of emergency repairs while your client's phone stops ringing.

If It Already Happened to You

We fixed the Sooner State Haulers site in about 45 minutes. Here are the exact steps.

Step 1: Reassign the domain.

Go to the sub-account Settings > Domains. Not the website settings page. The Domains page under account settings. Find your domain and reassign it to the correct website.

This is the part that tripped us up. The website settings page has a domain dropdown (it's a Naive UI n-select component under the hood), and it's unreliable. Use the Domains settings page instead.

Step 2: Fix the URL path.

Go to the website settings for your real site. Find the URL path field. Change it back to /. If the snapshot set it to /ai-generated-website or anything else, that's why your root domain is returning 404.

Step 3: Delete the junk template.

If the snapshot created a new website in the account, delete it. Having two websites in one sub-account with overlapping domain assignments causes routing conflicts.

Step 4: Verify.

Open the live URL in an incognito browser. Check the homepage, a few inner pages, and any landing pages with active ad traffic. Make sure forms still submit to the right pipeline.

What We Changed After This

We built a pre-snapshot checklist into our process. Before any snapshot load, we document the current domain mapping, website path, and active site. We load snapshots onto blank accounts first, then migrate piece by piece.

It's slower. It's worth it.

One snapshot load took down a client site that was generating real revenue. The fix was manual and stressful. The prevention is a 3-minute checklist.

If you're managing GHL sub-accounts for clients and loading snapshots regularly, build the checklist now. Not after the first 404.

If you've already hit this and need help untangling it, reach out to us. We've been through it.

FAQ

Does loading a GHL snapshot always overwrite website settings?

Yes. If the snapshot contains website settings, they replace whatever is currently configured. GHL does not merge settings or prompt you before overwriting. There is no option to exclude website settings from a snapshot load.

How do I load a snapshot without breaking a live website?

Create a blank sub-account first. Load the snapshot there. Then manually move the specific workflows, pipelines, or funnels you need into the production account. Never load a snapshot directly onto an account with a live, domain-connected website.

My domain shows 404 after a snapshot load. What do I check first?

Two things. First, go to Settings > Domains and confirm the domain is still assigned to the correct website. Second, check the website's URL path in website settings. If it changed from / to something like /ai-generated-website, that's your problem. Set it back to /.

Can I undo a snapshot load in GHL?

No. There is no undo or rollback for snapshot loads. Once the settings are overwritten, you have to manually restore them. This is why documenting your current settings before any snapshot load is worth the 3 minutes it takes.

Need help with GoHighLevel setup or website recovery? We've broken things so you don't have to. Let's talk.