Accounts age the way garages fill: nothing was ever wrong, things just accumulated. Three years of campaigns, three team members who each had a tagging philosophy, a dozen snapshots and every experiment that was never deleted. The account works, but nobody can say what is load-bearing. Here is the cleanup method that does not break anything.
Map what is load-bearing first
Before deleting anything, list what unquestionably works: the funnels taking traffic, the workflows with recent enrollment, the calendars with bookings this month, the forms with submissions. That list is your do-not-touch zone.
Everything outside it is a candidate, not a verdict. The difference between cleanup and outage is checking references before archiving.
The four zombie categories
Tags nobody has applied in six months. Workflows with zero enrollment this quarter. Pipelines whose stages have not moved a deal since last year. Calendars with no bookings and no availability. Each category has a report or export that surfaces it in minutes.
Archive in batches by category and wait a week between batches. Slow cleanup finds the hidden dependency that fast cleanup discovers in production.
Keep it clean with two rules
Rule one: every new automation gets an owner and a naming prefix, so next year someone knows what it is and who to ask. Rule two: quarterly, run the zombie reports again and archive anything that qualifies twice in a row.
Clean accounts stay clean with 30 minutes a quarter. Dirty accounts cost a full rebuild every three years. The math is not close.
Key takeaways
- Map the load-bearing list before touching anything
- Archive zombies in weekly batches, never in one sweep
- Naming prefixes plus quarterly zombie reports keep it clean
Want this looked at on your account?
Free 15-point health check with an ex-HighLevel engineer - findings with proof, fix list you keep.
Book a free diagnosis