When Not to Migrate Your Website

You should not migrate your website just because a developer wants a new project. If the current site is bringing enquiries, fits the business, and the real problem sits somewhere else, moving platforms can waste money and create fresh risk.

This is the anti-sales post most owners need before they spend five figures solving the wrong problem. I do migration work, and I still tell some prospects to stay put. That is because the point is not to get you onto WordPress. The point is to help the website do its job.

What is often really happening when a rebuild gets pitched?

A rebuild pitch is often a mix of truth, convenience, and sales. The truth is that many older sites are clunky. The convenient part is that rebuilding can be easier for the developer than repairing what exists. The sales part is that a rebuild sounds strategic and expensive.

Sometimes the pitch is valid. If the current platform traps your content, blocks proper SEO work, hides important access, or makes simple changes painful, a rebuild can be the cleanest move. That is the part of the job covered by platform migration, not by vague promises about “modernising” the site.

But many owners hear rebuild advice when the real issues are weaker than that. The site may simply need better copy, better follow-up, proper forms, stronger local SEO, or a faster homepage. Rebuilding the whole system because lead handling is bad is like replacing the shopfront because the receptionist never answers the phone.

What are the clearest cases where staying put wins?

Staying wins when the current site already converts well enough and the business has higher-return work elsewhere. Ugly is not the same thing as broken.

Case one is the site that still brings steady enquiries. If the offer is clear, the mobile experience is fine, the forms work, and customers trust it, a redesign may be lower priority than SEO, reviews, better follow-up, or photography. Case two is the small local business on a simple platform that only needs bookings, opening hours, service pages, and some proof. In that case, the platform may already match the size of the operation.

Case three is the business whose biggest problem is not the website at all. I see this often. The owner is frustrated because leads are quiet, but the real causes are poor Google Business Profile optimisation, no review process, weak internal linking, or zero follow-up once a form is submitted. Case four is the business with a limited budget that would get more from fixing one painful thing than from starting over. Case five is the site that already has strong search equity on a platform that is annoying but manageable. Migration introduces redirect risk, content cleanup, launch issues, and weeks of attention. Sometimes that cost is not worth paying yet.

Billy’s salon is a good example of honest platform fit. It is a Wix build because that suited the client’s size and budget. Not every win needs a custom stack. A site can be right for the moment without being my preferred technical setup.

Where should the budget go instead when migration is not the answer?

If staying is the right decision, the next question is where the money actually moves bookings. That answer is usually much less glamorous than a rebuild.

For one business it is local SEO. A clinic outside a major city may get more from finishing its Google Business Profile, review flow, and service pages than from moving platforms. For another, it is lead handling. If form submissions are not stored, email deliverability is weak, or nobody follows up properly, the business is leaking opportunity after the site has already done its part. That is why work like CRM and marketing automation often matters before any rebuild does.

For some owners, the money belongs in speed fixes. Large images, bad caching, and builder clutter can be repaired without migrating. If the site is only slow, speed optimisation is usually a better first spend than a platform move.

And sometimes the best spend is no spend for a few months. Keep the current site, tighten the offer, gather proof, improve photos, and learn what customers actually respond to. A calmer decision later is often better than a rushed migration now.

How can you decide in one sitting whether to migrate or stay?

You can decide a lot with one practical checklist. Ask whether the site is failing at ownership, performance, search, editing, or conversion, and whether those failures can be fixed without changing platforms.

Start with ownership. Do you control the domain, hosting or platform account, admin access, and backups? If not, that is serious. Then check editing friction. Can you update text, offers, services, and images without dread? Next check lead flow. Do forms work, store entries, and notify the right person? Then check search basics. Are service pages indexable, titles editable, and redirects manageable? Finally check whether customers can understand and contact you easily on mobile.

If most of those answers are yes, a migration may be optional. If several are no, the case gets stronger. The important part is to separate inconvenience from structural limitation. A site can be annoying and still be commercially fine. It can also look tidy while quietly blocking the next stage of growth.

If you do need to move, then move on purpose. That is where platform migration earns its keep, and where seeing examples on my work page helps you judge whether the move is being scoped honestly.

When have I told someone not to hire me?

I have told owners not to hire me when the current site was plain but effective, when the business had not yet proved its offer, and when the budget would be better spent on traffic or follow-up. That answer usually saves them money and makes them trust the next recommendation more.

I have also told people not to leave a builder platform when their team would never maintain a custom WordPress site properly, or when the business model was so simple that the extra flexibility would go unused. A business that only needs a brochure site, booking flow, and rare edits can be perfectly fine on a simpler platform.

The hardest truth for developers to say is that sometimes the current site is not the bottleneck. The owner may need better positioning, faster response to leads, clearer pricing, or stronger proof. A rebuild cannot fix a weak offer.

Quick answers

My site is ugly but converts. Should I touch it?

Only if the ugliness is harming trust, mobile use, or editing. If it converts well, be careful not to swap a working asset for an expensive vanity project.

How old is too old for a site?

Age alone does not decide it. An older site can still be fine if it loads well, converts, and stays editable. Structural limitations matter more than birthdays.

What is the difference between a redesign and a rebuild?

A redesign changes the look and sometimes the content. A rebuild changes the underlying system or platform. Many owners need one but get sold the other.

If you want an honest yes or no on whether a migration is worth it, send me the site and I will tell you plainly if you should leave it alone. You can start on platform migration or message me here: wa.me/923185687120.