Give Clients Their Website — Files AND a Live Site

A login is not ownership

Handing a client a seat in your GoHighLevel account is not a handover. It is a tenancy. The site still lives on your subscription, under your billing, at your discretion — and the client, correctly, can tell.

On GoHighLevel's Ideas board an agency puts the client's side of it plainly: they paid for the site, so “it's their right to take this asset”. He adds that he is now hesitant to build on GHL at all.

The risk nobody prices in

If your agency closes its GoHighLevel account, every client site you built goes down with it. Not degraded — gone. On a separate thread an agency owner describes clients as being “also at our mercy” for exactly this reason.

That is a single point of failure sitting under every site you have ever delivered, and it is not covered by any contract you have signed. It also cuts the other way: a prospect who has been burned by an agency folding will ask about it, and “we deploy to hosting you own” is a very short answer.

What a real handover contains

• The project files, in a GitHub repository owned by the client's account — not yours.
• A live deployment on the client's own Cloudflare Pages account, serving their domain.
• The DNS in their registrar account, or at least documented and transferable.
• A written note of what does not transfer: CRM, workflows, form backends, automations.
• Whatever forms now post to, and who holds that account.

Doing it with Hatch

The wizard connects the GitHub and Cloudflare accounts you point it at. For a handover, point it at the client's. Sit with them while they authorise it, or have them do it and send you the repository — either way the credentials never pass through us and the finished site is on infrastructure in their name from the first deploy rather than migrated to it later.

If handovers are a recurring part of the work rather than a one-off, the Agency plan at£297 is the tier built for that volume. Starter £29 and Studio £97.

Be straight about the limits

Tell the client what they are getting: the website. Not the CRM, not the workflows, not the form backends or the automations — those stay in GoHighLevel and, if they are leaving, need rebuilding somewhere else. A handover that quietly implies otherwise becomes your problem three weeks later.