Document the GoHighLevel account you inherited
You just got handed a GoHighLevel account someone else built. It runs real parts of the business, there are hundreds of things named "New Workflow (copy) 2," and nobody can tell you how any of it works. The fastest way to learn what a workflow was for is to break it.
The walkthrough
The steps
- 1
Connect the account exactly as you found it — one click with the Chrome app. Don't clean anything up first.
One click — the whole account, mapped as it stands. - 2
Read the map for what's safe to touch. A piece with nothing pointing at it is a low-stakes edit; the hub with twelve connections coming in is where caution lives.
The shape of the account — core systems, connections, and orphans. - 3
Ask Patchy the questions you'd ask the person who left. "What happens after someone books on this calendar?" Answers come from your account — not from how GHL accounts usually look.
Ask questions about your account, get answers grounded in it. - 4
Let Patchy write the baseline record — a plain description of everything, plus a list of what looks like junk, with the evidence behind each guess.
- 5
Correct the record as you confirm things — with the old agency, with whoever remembers fragments, or by testing. Every correction makes future answers more accurate.
- 6
Refresh as you take ownership. Rename the cryptic stuff, retire the confirmed junk, and the record keeps tracking reality.
Why this changes ownership
Most of digesting a stranger's account is just looking around — reading its patterns, working out what the previous builder was up to. The map compresses that from weeks to an afternoon, and the chat replaces reverse-engineering with asking: every answer is a piece of the previous builder's head, recovered. There's an honest breakdown of what AI can and can't see in your account — the short version is that generic AI guesses about your build because it has never seen it; Patchy sits on your actual account and doesn't have to.
And the record outlives you. The default ending of reverse-engineering is notes only you understand — the situation you inherited, one generation later. Instead, the next handoff is a link, not archaeology: whoever inherits this account after you gets a documented system on day one. The thing you didn't get.
The takeaway
You inherited a mystery. The next person inherits a documented system — the thing you never got.
FAQ
I don't have full admin access or an API token. Can I still connect the account?
If you can log into the account in a browser, the Chrome app can connect it — and a spreadsheet export works too. Use whichever your access level allows.
Will PatchyHub change or delete anything in my GHL account?
No. Connecting reads the account, and everything Patchy flags is a review list — any actual changes happen in GHL, made by you, when you decide. Exactly what you want in an account you don't fully trust yet.
The account is a disaster. Should I clean it up before documenting it?
No — bring in the mess as-is. You can't safely clean up an account you don't understand yet; that's how inherited accounts get broken. Document first, identify the junk with evidence, then clean up from a position of knowledge.