Exporting your site and lock-in

On most website builders you can leave with your content but not with your site. “Export” usually means a file of text and posts. The design, the editor, the forms and the store stay on the platform, and on some builders nothing exports at all. Whether that matters depends on how long you plan to keep the site.

The short version

• Export comes in three levels: content, static code and full source in Git. Ask which one a builder means.
• How a builder stores your site predicts what it can export. Pages held as data in a proprietary editor export least. Pages that exist as code files export most.
• Your domain is the one asset that always moves, as long as you registered it in your own name.
• Test the export on day one, on a throwaway page.

The three levels of export

Level 1: content export. You get a file, often XML, holding page text and blog posts. The layout, styling and navigation are not in it. You import the file into a new platform and design the site again around it.

Level 2: static code export. You get the pages as HTML, CSS, JavaScript and image files. It can be uploaded to any host and it looks the same. It is a snapshot, though: the visual editor that made it stays behind, and anything dynamic, such as a CMS, search or a form handler, stops working unless you replace it.

Level 3: full source in a Git repository. You get the project itself, the files a developer or an AI coding agent would edit. This is the only level where work continues where it left off. Check what the code depends on, because a database or sign-in service may still live on the vendor’s platform.

How the builder is made predicts what you can take

You can guess a builder’s export level from how it works, before you read a word of its documentation. Then check the guess against the help centre.

How the builder stores your site	What export usually means	Why
As data in a proprietary visual editor	Nothing, or level 1	The pages are records in the vendor’s database, drawn by the vendor’s software. There are no files to hand over
On an open-source content system that the vendor hosts	Level 1, sometimes a full backup on higher plans	The content format is a public standard, but the theme and hosting set-up are the vendor’s
In a visual designer that produces clean markup	Level 2, often on paid plans only	The designer can write out HTML and CSS, but its CMS and forms run on the vendor’s servers
As code generated by an AI from your prompts	Level 3, through Git sync or a download	The site already exists as source files, so handing them over is easy
As files in your own repository	Nothing to export	You never gave the site to anyone

The pattern is consistent: the more the product hides the code from you, the less of the site can leave with you. That is a trade, not a trick. Hiding the code is what makes those builders easy to use.

Five questions to put to the help centre

Search the vendor’s help centre for “export”, “download”, “backup” and “transfer”, and look for answers to these.

1. What exactly is in the export file? Pages, posts, images, comments, products? A list of what is left out is a good sign that the vendor has thought about it.
2. Which plan includes it? Export is sometimes reserved for paid plans and is commonly unavailable during a trial.
3. Does the exported site run without the vendor? Ask about forms, search, log-ins and anything that stores data.
4. Can I download my data separately? Form submissions, customer lists, orders and bookings should each have a spreadsheet download.
5. What happens to the site and the domain when I cancel? The answer belongs in writing, in a help article, not in a sales chat.

If the help centre says nothing about export at all, treat the answer as “none” until the vendor’s support tells you otherwise.

What never comes with you

Even a good export leaves things behind. Plan for each one.

• The editor. After a static export you edit HTML by hand, or with an AI agent, or not at all.
• Forms and their submissions. The form on the page posts to the builder. Download past submissions and arrange a new destination.
• Bookings, members and store data. Customers, orders and appointments live in the vendor’s database. Look for a CSV download of each.
• A vendor subdomain. If your site lives on the builder’s address, that address stays with the builder. Printed cards and old links will keep pointing there.
• Built-in extras. Analytics history, email marketing lists and AI-generated images may or may not be downloadable.

Your domain is the part that moves

A domain registered in your own name, at a registrar you chose, can point at any host. That is why the cheapest protection against lock-in is to buy the domain separately and connect it to the builder, instead of taking the builder’s bundled one.

A domain can also change registrar. ICANN, which sets the rules for registrars, says an authorisation code is required to transfer a domain and that your registrar must provide it within five calendar days of your request. A transfer can be refused during the 60 days after the name was first registered, so do not plan a move for the week after you buy it.

Moving without losing your visitors

When you do move, keep the same domain and send each old page address to its new one. Google recommends “server side permanent redirects from the old URLs to the new URLs” and advises against sending every old address to the new home page.

1. List every old address before you cancel anything. The old site’s sitemap is the quickest source.

2. Write a redirect map: one line per old address, with the new address beside it.

3. Install the map on the new host. On Cloudflare’s static hosting, for example, this is a plain text file named _redirects with one rule per line.

   /services.html /services/ 301
   /blog/2025/opening-hours /news/opening-hours/ 301

4. Point the domain at the new host and test a dozen old links by hand.

5. Keep the old plan for a few weeks if you can, so that nothing is lost while you check.

Run the export test before you build

Do this on the free plan, in the first half hour.

1. Make a throwaway site with two pages, an image and a form.
2. Find the export feature. If the free plan hides it, read the help article to see what a paid plan would give you.
3. Export, and open what you get. Is it a content file, a folder of pages or a repository?
4. If it is code, try to run it or upload it to a free static host.
5. Write down what was missing. That list is the true cost of leaving later.

If the test gives you nothing, that is not a reason to avoid the builder. Plenty of good sites live on platforms with no export. It is a reason to keep your own copies of the content and to own the domain.

If you would rather not need an export

The alternative is to start at level 3. When an AI coding agent builds the site in your own repository, there is nothing to export, because the files are already yours. Build a website for free with AI shows that route, and What free really means covers the other limits to weigh against it.

Our pick · we make it

For sites that live in your own repository: Emdash

Emdash is our product. It is not a website builder and it will not rescue a site from one. What it does is run AI coding agents such as Claude Code and Codex on a repository you own, in parallel, each task in an isolated workspace with a diff and pull request to review.

That is useful after a move: rebuilding exported content as real pages is a pile of small, checkable tasks. Emdash Classic is a free, open-source desktop app, and you supply the agent subscription or API key. If nobody on your side wants to work with code, staying on a hosted builder and owning your domain is the sounder plan.

See Emdash →

Frequently asked questions

Can I move a site from a hosted website builder to another host?

Usually not as a working site. A hosted builder stores your pages as data inside its own system and renders them with its own software, so there are no files to copy. What you can normally move is the content, the images and the domain. The design has to be rebuilt on the new platform.

What does exporting a website actually give me?

One of three things, depending on the builder. A content export is a file of your text and posts without the design. A static code export is a snapshot of the pages as HTML, CSS and JavaScript. A source export or Git sync is the full project a developer or AI agent can keep working on. Many builders offer only the first, and some offer none.

Will I lose my search rankings if I move my site to another builder?

Not if you keep the same domain and redirect every old address to its new equivalent. Google recommends permanent server-side redirects from old URLs to new ones and advises against sending every old address to the home page. A site on a free vendor subdomain is harder to move, because you do not control that address.

What should I save before I cancel a website builder plan?

Save five things: every page's text, the original image files, a list of every page address, any form submissions, and customer, order or booking records as spreadsheet downloads. Then confirm that the domain is registered in your own name and note when it renews. Do this before cancelling, because access to the editor can end with the plan.

How do I avoid lock-in when using a website builder?

Register the domain yourself with a separate registrar, keep your own copies of every text and image, write down the address of each page, and test the builder's export on a throwaway page before you build the real site. Those four habits make any later move far easier.