Rebuild or Migrate? Why a Platform Website Can Only Ever Be Rebuilt

You cannot move a website off a hosted platform in the way you can move a file between two computers. Your domain will follow you and most of your words and images can be exported. The design will not come with them. What is described as migrating a site is, almost always, rebuilding it - and knowing that early changes which question you are actually asking.

Because the question most people think they are weighing is: do I keep what I have, or do I start again? It is a reasonable question and it has a comforting answer, which is usually keep. But it is not the question in front of you. If you are moving at all, you are rebuilding either way. The real choice is what you rebuild onto.

What actually transfers

It helps to stop treating a website as one object. It is four, and they separate cleanly.

Your domain travels. This is the part everyone worries about and the part that is genuinely portable. A domain is registered to you, not to the platform hosting your site, and it can be pointed anywhere. Even where a platform sold you the domain as part of a bundle, you can normally unlock it and transfer it out. Your address does not change and your email is unaffected.

Your content mostly travels, in a reduced form. Most platforms offer some kind of export. What comes out is usually the text of your pages and posts, plus your images, in a generic format. What tends not to come out cleanly: anything built with the platform's own special blocks, product catalogues and their variants, form submissions and the forms themselves, custom fields, and the settings that decide how anything is arranged. You get the words. You do not get the pages.

Your design does not travel at all. This is the part that surprises people, and it is not a failing of any particular platform - it is how they work. The design of your site is not a document sitting in your account. It is the platform's rendering system applying its own theme, its own layout rules and its own styling engine to your content, freshly, every time someone visits. There is no file that contains your website's appearance. There is a system that produces it, and that system stays where it is.

Your standing on Google can travel, if it is handled properly. Rankings are attached to URLs, and a rebuild is where URLs are most easily broken. Done carelessly, this is the part of a move that actually costs you something. Done properly - old addresses mapped to new ones, redirects in place before the switch, nothing quietly dropped - it survives.

Put those together and the shape of it is clear. You keep your address, you keep your words, you rebuild the site.

Why the design cannot come with you

Imagine asking a hotel to send you your room. Not a photograph of it, and not a list of what was in it - the room. The furniture can be shipped. The layout, the light through that particular window, the way the corridor opens onto it: those were properties of the building, not of your stay.

A hosted platform is the building. The theme, the section types, the spacing system, the way the navigation collapses on a phone, the animation when a panel opens - these belong to the platform and are shared with every other site on it. That is precisely what you were paying for, and it is a fair deal. But it means there is nothing to hand over. When you leave, you take the contents of the room.

WordPress is a different case, and worth being accurate about

Self-hosted WordPress does not belong in the paragraphs above, and it would be convenient but wrong to put it there. It is open source. The content exports properly, the code sits on hosting you control, and you can move it between hosts or hand it to another developer without anyone's permission. On the question of ownership, WordPress gives a straight answer.

Its difficulty is a different one: accumulation. A site that has been running for a few years is typically a theme, a page builder and somewhere between fifteen and forty plugins, each on its own update cycle, each a small ongoing security obligation, and each adding weight to every page a visitor loads. The plugins that make it work are also what make it slow, and the maintenance never stops.

And there is a specific trap worth knowing about. If your pages were built with one of the large page builders, the layouts are stored as that builder's own markup. Turn the builder off and the pages do not revert to plain content - they come apart. So a WordPress site often keeps the ownership promise while still needing a rebuild to modernise, for reasons that have nothing to do with lock-in and everything to do with what has been piled on top over the years.

What this means for the money you have already spent

The instinct to protect an existing investment is sound. It is just pointing at the wrong thing here.

If you paid for a platform site three years ago, that money bought you three years of a working website. It has been spent and it did its job. What it did not buy is an asset that can be carried forward, because there is nothing to carry - no code, no design files, no ownership stake in the thing you were using. That was the arrangement from the start and it is not a scandal. It just means the past spend is not an argument for staying, in the way that a paid-off mortgage is an argument for staying in a house. There is no equity in a rental.

Which is why the sunk-cost objection dissolves once you look at it directly. You are not throwing away a site by rebuilding. The site was always going to be rebuilt the moment you wanted it somewhere else.

The choice you are actually making

So, granted that you are rebuilding: rebuild onto what?

Onto another platform if your needs genuinely fit inside one and you would rather not think about it again. This is a real answer and sometimes the right one. If you are doing the work yourself, on a small budget, and the template does what you need, a platform is a sensible choice and we would happily tell you so. The trade is that you will be in the same position next time - which is fine, as long as you know it, and as long as the next time is far enough away.

Onto something you own if you are paying a professional either way. This is where the arithmetic changes. The same fee buys either an arrangement of a template inside a platform's limits, or a site designed and built around your business that belongs to you afterwards: the code on hosting in your name, movable to any host or any developer, with no licence to renew and no plan to upgrade. If you are writing the cheque regardless, the second is a strictly better use of it.

The one thing not worth doing is deciding by default. Staying because moving sounds disruptive is a decision too, and it quietly renews itself every month.

Doing it without losing anything

A rebuild handled properly should cost you nothing you currently have. What that requires is unglamorous and mostly happens before the switch.

Take a full inventory of your existing pages and their addresses first - every one, including the ones you have forgotten. Export the content while you still have access, rather than after you have cancelled. Build the new site alongside the old one so nothing goes dark in between. Map every old URL to its new equivalent and put the redirects in place at the moment of switching, not the week after. Keep your domain where it is until the new site is ready to receive it. Then watch search performance for a month afterwards, because that is when anything missed shows up.

Done in that order, the move is invisible to everyone except you. Your customers see a better site at the same address, and nothing they had bookmarked breaks.

If you want a read on where your current site stands before deciding anything, our website health check will tell you how it performs, how readable it is to search engines and AI assistants, and what is holding it back - in a few seconds, without anyone calling you afterwards.