Funnels are the most visible thing an agency builds in a GoHighLevel sub-account. They are the pages clients look at, the designs that took a week of revisions to approve, and in many cases the thing the client believes they are paying for. Which makes it worth knowing that of all the objects in a sub-account, funnels and websites have one of the weakest safety nets when they are deleted.
Here is the direct answer to the question in the title: HighLevel has no way to export a funnel or website to a file. There is no download button and no scheduled backup. What it offers instead is real protection against bad edits (version history is a strong feature here), partial protection through duplication (snapshots and share links), and almost nothing against deletion. Workflows get a 90 day Deleted tab. Contacts get a 60 day restore window. A deleted funnel gets neither.
Each of those pieces deserves a closer look, because the strong parts and the missing parts are easy to mix up.
Can you export a HighLevel funnel?
No. The importers all point one direction. HighLevel will happily import a funnel from ClickFunnels, and share links let one HighLevel account pull a copy of a funnel from another. Nothing performs the reverse trip. There is no export to HTML, no export to a file, and no way to hand a client a copy of their own site that exists independently of the platform.
The API tells the same story. HighLevel’s public Funnels API contains exactly three endpoints: fetch the list of funnels in a location, fetch the list of pages in a funnel, and fetch a count of those pages. All three are reads, and none of them returns the page content you would need to rebuild anything. There are no endpoints to create, update, or restore a funnel. As with workflows, even a team willing to build its own backup pipeline can only capture an inventory, a list of names and page counts, not the pages themselves.
What does version history actually cover?
This is the good news section, and it is worth being fair about it. HighLevel added auto-save and version history across funnels, websites, blogs, webinars, and e-commerce stores, and the feature is well built. Changes save in real time as you edit. A new version is captured every 10 minutes whenever changes were made, and manual saves create versions too. Each item keeps up to 50 versions, time-stamped, and you can preview any of them before restoring or publishing it.
For the most common way funnels get damaged, someone editing the wrong thing, this is a real safety net. A client user drags a section into oblivion on Thursday, you open the clock icon on Friday and restore Wednesday. No support ticket required.
What version history cannot do is survive the loss of its container. The versions live inside the same sub-account as the funnel. Delete the funnel and its history goes with it. Lose the sub-account and every version of every page inside it is gone at once. Version history is an undo stack, not a backup, and the difference shows up precisely when things go badly instead of mildly wrong.
What happens when a funnel is deleted?
It stays deleted. There is no trash, no Deleted tab, and no restore window for funnels or websites. Bringing back deleted funnels has been an open request on HighLevel’s ideas board for years, alongside a companion request for a recycle bin covering deleted pages and funnel steps. Some agencies report that support has occasionally recovered a very recently deleted funnel, but there is no documented restore path and nothing you can count on.
What HighLevel does give you is a record of the crime. Audit logs, found under Settings, track funnel deletions, step deletions, step edits, settings changes, and more, with timestamps and user IDs, and the logs can be exported to CSV. They are retained for a rolling 60 days, after which the records are permanently removed. Audit logs will tell you that a contractor deleted the client’s funnel at 4:12 pm on a Tuesday. They will not return a single pixel of it.
That asymmetry is worth sitting with. The platform can tell you exactly who destroyed the asset and when, and still has no mechanism to undo it. If a funnel matters, the copy has to exist before the deletion, somewhere the deletion cannot reach.
Do snapshots or share links count as a backup?
Partially, in the same way they do for workflows, and with the same fine print.
Snapshots capture funnel and website structure along with the rest of a sub-account’s configuration, which makes them the closest thing HighLevel has to a native funnel backup. They carry no contacts, conversations, or opportunities, but pages travel well. Take a snapshot today and you can load today’s funnels into a fresh sub-account later. The catch is the tense: today’s. A snapshot is frozen when you take it, so a snapshot from March knows nothing about the redesign you shipped in June, and keeping snapshots current means someone re-snapshotting after every meaningful change, forever.
Share links are the lighter option. Any funnel can generate a share link from the three dots menu on the funnel list, and another HighLevel account can import a copy from that link. Agencies sometimes use this as an informal backup, importing copies of important funnels into a spare sub-account. It works as duplication, but the copy is point-in-time like a snapshot and it still lives inside HighLevel, usually inside the same agency.
| Native option | Protects against | Window | Where the copy lives |
|---|---|---|---|
| Version history | Bad edits | Last 50 versions | Inside the same funnel or page |
| Audit logs | Nothing (a record, not a copy) | Rolling 60 days | Inside the same sub-account |
| Snapshot | Rebuilding from scratch | Point in time, goes stale | Inside the agency account |
| Share link | Single-funnel loss | Point in time, goes stale | Another HighLevel account |
The last column is the recurring theme on this blog. Every native copy of a funnel lives inside HighLevel, and most live inside the same agency account as the original.
What can still go wrong?
Run the failure cases against that table. A funnel deleted by anyone with access is simply gone, because nothing in the table restores deletions. A redesign that went wrong 51 versions ago is out of version history’s reach, and a busy page can burn through 50 auto-saved versions in a few working days. A snapshot from before the current design is a backup of the wrong thing.
Then come the container failures. If a sub-account is deleted, the funnels, their version history, and their audit logs all vanish together, and if the agency account itself lapses, the sub-accounts follow it down, taking the agency’s stored snapshots along. HighLevel keeps roughly 7 days of infrastructure database backups for its own disaster recovery, but there is no process for requesting your funnel back from them. And through all of this, the live domain is serving nothing, because unlike a lost contact record, a lost funnel is a public outage the client can see.
How do you actually back up HighLevel funnels?
Without an export, the honest options are discipline or tooling.
The discipline version: snapshot every sub-account on a schedule, weekly for accounts under active development. Keep share-link copies of your most valuable funnels in a spare sub-account and refresh them after major changes. Save full-page screenshots and copy deck for the pages that took real design work, because if you ever rebuild by hand, those are what you will rebuild from. Check the audit logs periodically so you know who is touching what. All of this works while someone remembers to do it, and every copy it produces still sits inside HighLevel.
The tooling version is why we built GHLArmor, and since it is our product, weigh the recommendation accordingly. GHLArmor is the first backup approved by the HighLevel Marketplace, and it backs up funnels continuously alongside contacts, workflows, custom fields, and opportunities, keeping the copies outside HighLevel entirely. That location matters more for funnels than for almost anything else, because funnels are the one object where deletion is permanent by design. When there is no Deleted tab to fall back on, the restore has to come from a copy the deletion could not touch. We compared the approaches, ours included, in our roundup of HighLevel backup tools.
Use the native features either way. Version history in particular is excellent at the job it was built for, and it costs nothing. Just keep its job description in mind: it undoes edits. It does not survive deletions, and it does not leave the building.
Frequently asked questions
Can I export a HighLevel funnel to a file? No. HighLevel has no feature that exports a funnel or website to a file you can store outside the platform. Share links let another HighLevel account import a copy, and the ClickFunnels importer brings pages in, but nothing brings a funnel out. Every native option keeps your pages inside HighLevel.
Can I recover a deleted funnel in HighLevel? There is no native restore for deleted funnels or websites. Unlike workflows, which sit in a Deleted tab for 90 days, and contacts, which can be restored for 60 days, a deleted funnel has no documented recovery path. Audit logs will show who deleted it and when, but they do not bring it back. Restoring deleted funnels remains an open request on the HighLevel ideas board.
Does version history protect my funnels? Against bad edits, yes. HighLevel auto-saves as you work and keeps up to 50 versions per item, with a new version captured every 10 minutes when changes are made. You can preview and restore any of them. But version history lives inside the same sub-account as the funnel, so it disappears if the funnel or the account does.
Do HighLevel snapshots back up funnels? Snapshots capture funnel and website structure, so they are more useful here than they are for contacts. The limits are the usual ones: a snapshot is frozen at the moment you take it, it goes stale as soon as anyone keeps editing, and it is stored inside the same agency account it is meant to protect.
Can the HighLevel API back up funnels? Not meaningfully. The Funnels API has three endpoints: list funnels, list a funnel’s pages, and count those pages. There is nothing to read full page content for rebuilding, and nothing to create, update, or restore a funnel. At best you can keep an inventory of names and page counts.