How to move off a hosted website builder

Moving away from a hosted website builder — the kind where you signed up, dragged some blocks around, and never touched a file directly — is a different kind of migration from moving between two hosting accounts. There, you copy files and a database wholesale. Here, there usually is no file or database export worth having, because the builder's platform generates the site from its own proprietary system that does not exist anywhere else. What you are really doing is rebuilding the site on a platform you control, using the old one as a reference.

Why this is a rebuild, not an export

Most website builders keep your site in a format specific to their own platform, designed to work only inside their editor. A small number offer a basic export — usually static HTML with no working forms, search, or dynamic features — which can be a useful starting point but is rarely a finished result on its own. Assume you will be recreating the site rather than transplanting it, and the whole project becomes much more predictable.

Step 1 — Document everything before you start

Go through the current site page by page and record:

• Every page, with its exact URL.
• The text content of each page, copied out somewhere you can paste from later.
• Every image, downloaded at full resolution rather than screenshotted.
• Blog posts, in full, including publish dates if you want to preserve them.
• Anything functional: contact forms, a store, a booking system, and what each one actually needs to do.

This step takes longer than any other in the whole process, and it is the one that determines whether the finished site is actually complete.

Step 2 — Set up the new platform

Install the CMS you are moving to — commonly WordPress — on your new hosting account, and get it running with a theme in place before you start adding content. Trying to design and migrate content at the same time tends to produce a site that is neither finished nor faithful to the original.

Step 3 — Rebuild page by page

Recreate each page using the content gathered in step 1. Upload images at their original resolution rather than re-saving compressed versions from the old site, and rebuild forms using whatever form tool the new platform provides, testing each one as you go rather than leaving it until the end.

Step 4 — Match the old URL structure

Where possible, give each new page the same address it had on the builder — if the old about page was at /about, aim to recreate it at /about on the new site too. This matters more here than in most migrations, because a rebuild naturally tempts you to reorganise things, and every URL that changes needs a redirect to avoid losing links and search visibility. See keeping your URLs working after a move for handling the ones that genuinely have to change.

Step 5 — Test before the domain moves

With the domain still pointed at the builder, preview the new site privately using a hosts file entry — see previewing a site with your hosts file. Check every page against your original list from step 1, confirm every form sends properly, and compare the new site against the old one side by side to catch anything missed.

Step 6 — Switch DNS, then wait before cancelling the builder

Once testing passes, point the domain's DNS at your new hosting rather than the builder's servers. Keep the builder subscription active for a couple of weeks after the switch rather than cancelling immediately — partly for the usual DNS-propagation reasons, and partly as insurance while you confirm nothing was missed in the rebuild.

Does this hurt your search rankings?

A rebuild carries more risk than a like-for-like host migration, but mainly because content and URLs are more likely to change along the way, not because moving off a builder is inherently penalised. Keep URLs consistent where you can, redirect the ones that must change, and the transition is largely invisible to search engines over time.