When is it time to move your website?

Moving a website is disruptive, takes longer than expected and occasionally makes things worse. It deserves to be a decision rather than a mood. A few signals genuinely justify it; several common ones do not.

Reasons that genuinely justify a move

The platform cannot do what the business now needs. Not a preference — an actual blocker, such as taking a booking or a payment the way your customers expect, and no reasonable workaround exists.

The cost no longer matches the value. Small monthly charges accumulate quietly, especially when several add-ons are each solving part of one problem.

You cannot get at your own content or data. If your pages, images and customer records are difficult to export, that is a reason to leave and also a warning about where you go next.

It is poor on phones and cannot be fixed. Most people will meet your business on a phone. If that experience is bad and the platform will not let you repair it, the site is working against you.

You do not control the domain. If an agency or a platform holds your domain, you do not fully own your address. That is worth resolving regardless of whether you move.

Reasons that usually do not

Boredom with the design is not a reason to move platforms; it is a reason to change the design. One bad month of traffic is noise, and rebuilding in response usually destroys the evidence you would need to understand it. Being told a platform is unfashionable is not an argument — your customers have no opinion about your stack. And a slow site is often slow because of oversized images or too many add-ons, which move with you if you do not fix them.

What to check before you commit

1. Can you actually export the content? Text, images, blog posts, product details and any customer or enquiry records. Check before you decide, not after.
2. Do you control the domain? Confirm you can access the registrar and change where the domain points.
3. Write down every URL that exists today. This is the step people skip and the one that matters most.
4. List everything that is not a page. Forms, bookings, payments, email sign-ups, tracking, integrations. These break individually and quietly.
5. Decide who does the work and when. Migrations stall in the middle, which is the worst place to be.

The part people get wrong: redirects

A new site usually changes the addresses of your pages. Every link anyone has ever made to you, and every result a search engine has already recorded, points at the old address. If those addresses return an error, the value attached to them is lost, and it does not come back on its own.

The fix is unglamorous and non-negotiable: map each old address to its closest equivalent on the new site and set up a permanent redirect. Not everything to the homepage — that is barely better than an error, because a visitor looking for a specific service has been dumped somewhere that does not answer them. This single step is the most common reason a migration loses traffic, and the most common thing nobody is asked about beforehand.

What to expect afterwards

A short unsettled period is normal while search engines re-crawl and re-evaluate the new addresses. What is not normal is a decline that continues for months, which usually means redirects are missing, pages were dropped, or content was thinned during the rebuild. Keep a record of what the old site had, so you can tell the difference between settling and losing.

The bottom line

Move when the platform blocks something the business genuinely needs, not when the design has gone stale. Before you commit, confirm you can take your content and your domain with you, and treat the redirect map as part of the job rather than an afterthought. If you are earlier than that and still weighing whether you need a site at all, start with whether social media is enough on its own.