Your snapshot imported but nothing works right. Forms send to the wrong place, automations misfire, calendars show the wrong owner. Here is the exact order I use to rescue it.
A broken snapshot import feels chaotic. The pages look right, but leads route wrong, messages use the wrong business name, and your calendar books under someone else. I see this often in rescue calls.
I am Joe Asis. I work in GoHighLevel every day and have taken 100+ systems snapshot-to-launch while supporting 400 to 700+ subaccounts. I also coached 70+ students via Extendly on setup and support. The method below is the same one I use for clients like LeadJuice, Seven Figure MSP, StandOut Funnels, Smith Barid, Agent FlyWheel, and 7FigureCRM.
The core idea is simple: do not rebuild yet. Most snapshot failures are connection failures, not structure failures. If you fix them in the right order, you save days of work.
Snapshots move structure well. They move pipelines, workflows, forms, funnels, and templates. They do not move live connections cleanly. That gap causes almost every break I fix.
Custom values hold your business name, phone, email, address, links, and branding. On import, they either keep the source values or get overwritten with blank defaults. The result: emails signed by the wrong company, SMS with the wrong number, footers with dead links.
I audit custom values first on every rescue because they touch every message. If you skip this, you will chase symptoms in five workflows when the cause sits in one settings table.
This is the most damaging failure. If workflows stay live during import, they can send to imported test contacts or old contacts carried in the snapshot. I have seen welcome sequences, invoices, and review requests go to the wrong people within minutes.
The fix is prevention plus control. Pause before you import. Verify after you import. My full automation standard is covered in GoHighLevel automations every build needs.
Snapshots do not bring your team with them. Workflow actions tied to a specific user, round robin groups, or notification steps often point to a missing user or the account owner by default. That breaks lead assignment, internal alerts, and task creation.
Check every action that assigns, notifies, or mentions a user. If the source build used a staff member you do not have, remap it to the correct role in the new subaccount.
Calendars import as shells. The connected Google or Outlook calendar, the assigned user, the availability, and the confirmation workflows often still reference the old setup. Bookings then land on no calendar, or worse, on someone else's calendar.
Reconnect each calendar to the correct user and test the booking flow. For speed to lead impact, see speed to lead workflow for any niche.
Funnels and sites import with placeholder or source domains. Forms may post to the right list but redirect to a dead thank you page. Trigger links and buttons may still point to the source domain. Go live without checking this and your ads send traffic to a 404.
Relink the domain, update every funnel step URL, then click every button as a stranger would.
Do not start editing. Start containing. This triage order stops further damage and shows you the true scope in under 30 minutes.
Write this down in a simple sheet. One row per issue, one owner, one status. This sheet becomes your rescue plan. It also stops random fixes that create new breaks.
If you plan to hand this to a helper later, read how to hire a GoHighLevel virtual assistant so access and QA stay tight.
Fix in layers. Settings first, then people, then connections, then messages, then traffic. This order prevents rework.
Turn all active workflows to draft or paused. Pause triggers on forms, surveys, and inbound numbers. Tell the team no live testing until QA starts. This takes five minutes and prevents the most costly errors.
Update company name, phone, email, address, hours, social links, logo URLs, and legal links. Use clear names like biz_phone_main and biz_email_support so future imports map fast. Replace any source brand text in email and SMS templates with these values.
Add the correct users with the least access they need to do the job. Remap assignment in pipelines, round robin, workflow notify steps, and calendar ownership. Send a test internal notification to each role to confirm routing.
If you are vetting outside help for this step, use the questions to ask before you hire a GoHighLevel expert.
For each calendar: assign the right owner, connect the right Google or Outlook account, set availability and buffers, then link the correct confirmation, reminder, and no show workflows. Test book, reschedule, and cancel. Confirm the event lands on the right calendar and the contact gets the right messages.
Connect the live domain. Update funnel settings, each step URL, form thank you redirects, chat widgets, and payment product links. Replace any hard coded source domain in buttons and emails. Click through every path on mobile and desktop.
Open each workflow in order of risk: new lead response first, then booking, then nurture, then review and referral. For each one confirm trigger filters, wait steps, SMS and email content, custom value tokens, assignment steps, and goal events. Keep what matches the new business. Archive duplicates from the snapshot that you do not need.
My baseline for a clean build is detailed in GoHighLevel snapshot to launch. Use it to confirm you kept the essentials.
Reconnect LC Phone, email sending domain with SPF and DKIM, Facebook and Google integrations, Stripe, and any webhook or API keys. Keys do not transfer in snapshots. Replace them and test each one with a live action, not just a green checkmark.
You need proof the system works end to end. Use three fresh test contacts with real mobile numbers and inboxes you control.
Log results with timestamps and screenshots. If a step fails, fix the source setting, not the message copy. Then rerun the full contact path, not just the failed step.
Rescue when the core imports clean twice and only connections fail. If pipelines, workflows, forms, and funnels are present and sound, rescue is faster. Most cases I take on fall here.
Rebuild when the snapshot itself is corrupt. Signs: key pipelines missing after two imports, workflows import empty, media and templates fail repeatedly, or contacts merged into the wrong subaccount with no clean backup. Rebuilding a clean core with my snapshot to launch process beats patching a broken base.
Rule I use with clients: if triage shows more than 40 percent of core assets missing or firing wrong after containment, price a rebuild. If under that line, rescue. Either way, keep a clean snapshot backup before you touch anything further.
I keep rescues direct and contained. You get a fixed scope, a clear order, and proof at each step.
This comes from daily reps: 5 years in GoHighLevel, 100+ systems snapshot-to-launch, 400 to 700+ subaccounts supported, 70+ students coached via Extendly, plus builds for LeadJuice, Seven Figure MSP, StandOut Funnels, Smith Barid, Agent FlyWheel, and 7FigureCRM.
Related reading: automations every build needs, speed to lead workflow, and hire questions.
Most breaks come from five causes: custom values overwritten on import, workflows left live that fire to old contacts, user roles and permissions not mapped, calendars still linked to the source account, and domains or funnels pointing to the wrong location. Triage in that order before you change anything.
Rescue when the structure is sound and the damage is limited to settings, links, and triggers. Rebuild when pipelines and workflows were deleted, data was merged into the wrong subaccount, or no clean snapshot backup exists. If the core assets import clean twice and only connections fail, rescue saves time.
Run three test contacts through the full path: one new lead from a form, one from a funnel or calendar booking, and one revived old contact. Confirm tags, pipeline stage moves, SMS and email delivery, calendar assignment, and notifications. Check in test mode first, then with a live number.
A clean rescue often takes hours, not days, when you follow a fixed order: freeze sends, audit custom values, pause risky workflows, remap users and calendars, relink domains, then QA with test contacts. Complex builds with many subaccounts or custom integrations take longer because each connection needs verification.
Send me your triage sheet or give me view access. I will confirm rescue vs rebuild and fix it in order.
Book Your Rescue Call