Can you move a website off GoHighLevel?

A physiotherapy clinic asks a one-person AI agency for help. Their previous agency built the website inside GoHighLevel, along with a booking calendar and text reminders. The agency is closing its doors. The clinic owner's question is simple: "Can you just move our website over to you?"

It's a fair question, and HighLevel answered it directly this week. A help centre article updated on 10 February 2026 says websites built in HighLevel's page builder have no supported way to be exported for use on another platform. You can copy what a page shows, but you can't lift the site out and keep editing it somewhere else.

So the honest answer to the clinic is: we can keep your words, pictures, domain and search history, and we rebuild the site itself. This guide shows what that takes.

Can I export my GoHighLevel website?

No, not as a working site. HighLevel's article says there's no supported one-to-one website export, and that sites can't be exported in a way that lets them be managed or edited outside HighLevel.

What you can do, HighLevel says, is open a published page in the browser, view its source and save the HTML (the code the browser receives) as a file. HighLevel is clear about the limits of that copy:

• it's no longer managed by HighLevel and can't be edited in the builder;
• HighLevel doesn't support copies hosted elsewhere;
• it keeps working only while the original HighLevel account and its files stay active.

That last point matters. A copied page can look fine on the day you move it and then lose its images or forms when the old account closes. HighLevel lists three sensible uses for the copy: recovering content, rebuilding the site on another platform, and keeping a record.

What can you take with you?

More than the answer above suggests. The site's design stays behind, but most of what gives a website its value belongs to the business and can move. Work through this list before anyone cancels anything:

What	Where it usually is	What to do
Words on every page	The live site	Copy each page's text into a document, page by page
Photos, logos and documents	The live site and the HighLevel media library	Download originals where you can, not screenshots
The page list and addresses	The live site	List every page address, including old campaign pages
The domain name	A registrar, sometimes one the old agency chose	Find out whose account it's in; move it into the owner's name if needed
Forms and where they send	HighLevel forms and workflows	Write down each form's fields and who receives it
Contacts, bookings and message history	HighLevel's contact and calendar tools	Ask how to export them before the account closes
Tracking codes	Page settings	Note which analytics and advertising accounts the site reports to, and who owns them
Reviews and the Google listing	Google Business Profile	Usually separate from HighLevel; confirm the owner holds it

The domain is the one that causes the most trouble. If the old agency registered it in their own account, the clinic can't point it anywhere until it's moved. That's why who should own each client account starts with the domain: it's the hardest thing to replace.

Take your own copies of everything on the list, with dates, and keep them with the client's records. If the move is ever questioned, you can show exactly what the old site said and when. A single place for client management for freelancers makes that easy to find again.

What happens to forms, bookings and texts?

They stop when the HighLevel account stops. The HighLevel article says copied pages depend on the original account staying active, and forms, calendars and text reminders are HighLevel tools, not part of the page.

For each one, decide what replaces it:

• Contact form. A form on the new site that sends to the business's own email. Test it before launch.
• Booking calendar. Many clinics and salons already have booking software from their industry. Link to it, or pick one the business owns.
• Text reminders and follow-ups. These are a service, not a website feature. If the business wants them, they need their own account, ideally in the business's name.

Tell the owner plainly which of these will change, and when, before you start. People notice a missing reminder text far sooner than a new font.

Should you rebuild or stay on GoHighLevel?

Rebuilding isn't always right. HighLevel does a lot in one place, and a business that uses its texting, calendars and follow-ups every week may be better served staying, perhaps with a new agency that runs it.

Ask the owner three questions:

1. Which HighLevel tools do you use each week? If the answer is "just the website", a rebuild is simpler to own and to keep.
2. Who holds the HighLevel account? If it's the old agency's account, staying means working with them, or starting a new account anyway.
3. What would you want to take if you ever left again? If the answer is "everything", build the new setup so the business owns each piece from day one.

If you rebuild, you're not starting from nothing. You have the words, the pictures, the page list and the history. The design is the part you redo, and it's often due for a refresh anyway.

How do you rebuild without losing search traffic?

The domain stays the same, but the page addresses often change on a new site. Google's guidance on site moves describes the fix: make a list of every old address, decide where each one should go on the new site, and set up permanent redirects (instructions that send visitors and search engines from an old address to its new one).

A simple order of work:

1. List every page address on the old site, including ones no longer in the menu.
2. Build the new site, keeping the same addresses where you can.
3. For each address that changes, add a permanent redirect to the closest new page.
4. Switch the domain to the new site at a quiet time.
5. Click through the old addresses and check each one lands somewhere sensible.
6. Test every form and booking link.

Don't promise the owner their search position won't move. Nobody can promise that. What you can say is that you've kept their addresses working and their content intact, which is what Google's guidance asks for.

How do you avoid this next time?

Set the new site up so the business could leave you too, without a rebuild. That's the kind thing to do, and it makes the offer easier to accept.

• Register the domain in the owner's name, with you added for access.
• Keep the site as ordinary files you can hand over, or on a host where the owner holds the account.
• Put each service (forms, bookings, texts) in an account the business controls.
• Write down, per client, what they own and what you run for them.

The idea has a name: owner-held accounts. If you're a designer running your agency alone, the page for web designers shows how that looks across a handful of clients.

Where Volant fits

Volant keeps the agency side of this in one place: each client's notes, the list of what they own, and the history of the work. You can export your clients, projects and files as normal files that open without Volant. The page on keeping client accounts in the owner's name sets out how Volant treats the accounts themselves.

For the clinic, the answer is the same with any tool: keep what belongs to them, rebuild what doesn't move, and write down who owns what before you start.