The GHL Backup GoHighLevel Doesn't Offer

Where is the only copy?

Worth sitting with for a second: right now, where does the only copy of your client's website exist? If the answer is “GoHighLevel's servers”, you do not have a backup. You have a dependency.

GoHighLevel offers no website backup or download. That is not an oversight on their part — the site is a rendered view of platform data, not a folder of files sitting somewhere waiting to be zipped. But it does mean there is nothing to restore from if the account closes, billing fails, or the agency that owns the subscription winds down.

What a real backup has to survive

• A cancelled or lapsed subscription.
• An agency closing its account, taking every sub-account site with it.
• Somebody deleting or overwriting a page and nobody noticing for a fortnight.
• A client leaving and asking for their site on the way out.

A screenshot survives none of those. A page-source copy survives the fourth one badly.

A ZIP is a start

Pulling the rendered front end into a project ZIP gets you a real artefact: pages, assets, structure, on your own disk. Keep it somewhere that is not the same account as everything else, and date it — an undated backup is a guess about what was live.

A live mirror is better

The reason a ZIP is only a start is that restoring it is still a project. A mirror deployed to your own Cloudflare Pages account is a backup you can point a domain at the same day: the site is already built, already served, already on TLS. If the GoHighLevel side disappears at 9am, you change DNS and you are back.

That is the same route as a full migration, run on purpose and kept in reserve. With Hatch it is the extension, then the wizard, then a live URL on infrastructure you own — Starter £29, Studio £97, Agency £297 depending on how many sites you are covering.

What this does not back up

The front end only. Contacts, form submissions, workflows and automations are separate exports from inside GoHighLevel, and they are the ones with a legal clock on them — do those on their own schedule. A site backup that quietly implies it covered the CRM is worse than no backup at all, because somebody will rely on it.

Keeping it current

A mirror taken once is a snapshot of a site that has since changed. Re-run it when the site changes materially — a new page, a new offer, a rebrand — rather than on a calendar nobody keeps to. For client sites, the natural moment is whenever you invoice for a change.