How to Safely Import and Test a GoHighLevel Snapshot

Never import an unfamiliar snapshot directly into a critical production account. Create a blank or demo sub‑account just for testing—no real leads, no mission‑critical workflows, freedom to turn things on and off. Once you're confident, you can import into the real sub‑account with a clear plan.

From your agency view, create or open your test sub‑account, then use the snapshot link or list to load the snapshot. After import, give GoHighLevel a moment to finish processing, then check pipelines, funnels, workflows, calendars, tags, custom fields, and custom values.

Before enabling workflows or sending live traffic, get familiar with what's inside. Review how many pipelines exist, what stages they have, which workflows are active, which funnels and forms are included, and note what you'll keep, rename, edit, or remove.

Update logos, colors, and fonts on funnels and pages. Update business name, address, and contact info in custom values. Update default email/SMS sender details, time zone, and calendar availability. This ensures that when you test, you're seeing something close to what real leads will see.

If importing into an account with existing assets, look for pipelines with the same name but different structures, overlapping tags, workflows triggered by common events, and calendars that might duplicate existing booking flows. Ask: 'If I added this snapshot on top of what's already here, where might it double‑fire or conflict?'

Simulate being a lead: fill out forms, book appointments, and confirm contacts are created correctly with the right tags, pipeline stages, and workflow messages. Mark appointments as completed or no‑show and verify follow‑up logic. Note broken links, confusing copy, or generic placeholders.

You don't have to use every part of a snapshot. Decide which pipelines, workflows, funnels, tags, and fields you'll adopt. In your production sub‑account, you can import the full snapshot and disable unneeded assets, or import selectively. The key is to have a plan before you press import.

When ready for production: backup or document your current setup, import the snapshot, immediately disable non‑essential workflows until confirmed, and resolve naming conflicts. Think of this as merging two systems—not dropping one on top of the other without looking.

Monitor new leads and appointments for a few days. Double‑check correct workflows are running, no duplicate messages, and pipelines show accurate stages. If you see unexpected behavior, check workflow logs, adjust triggers, and update tags or forms as needed.

After customizing the snapshot to your brand and process, save it as your own internal snapshot. Use it to onboard new clients or locations faster. Maintain an 'operational master' that you update, then redeploy. This turns a purchased snapshot into a proprietary asset you control.

Related GoHighLevel Articles