Do I Need a New Website When I Change Developer?

If the site is technically healthy, mobile-friendly, editable, reasonably fast and still fits the business, a takeover may be all that is needed. The new developer can establish backups, update the software, improve weak sections and support it going forward.

A broken form, slow theme, old plugins or a few poor landing pages do not necessarily justify rebuilding everything. Quote the repairs, compare that cost with replacement and consider how many more years the current site is likely to remain useful.

Sometimes the website itself is fine but the surrounding arrangement is not. Moving the same WordPress site to better hosting, separating the domain from the agency or changing maintenance provider can solve the real problem without changing what customers see.

A rebuild can make sense where the site is unsupported, insecure, very hard to edit, based on poor custom code, trapped in a platform that no longer fits, or so structurally weak that every future improvement becomes expensive.

This is the classic “pay cheap, pay twice” scenario: finishing or repairing poor work can cost more than starting again properly.

A credible recommendation should compare the routes. What can be kept? What is broken? What would repair cost? What would replacement cost? What SEO/content value needs preserving? What happens if nothing changes?

If the only explanation is “we always rebuild sites we take over”, that is a supplier preference, not necessarily a business case.

A website that is acceptable today but likely to need replacing in six months is different from one that could comfortably run for another three years. Repair costs should be judged against the useful life they buy. Spending £800 repairing a site that still fits the business for several years may be sensible; spending the same amount on a platform that is already blocking every planned improvement may not be.

Even when a rebuild is justified, the existing site can contain valuable assets: service copy, pages that rank, backlinks, successful calls to action, customer FAQs and analytics data. A rebuild should preserve those useful signals rather than treating “new website” as permission to erase everything that came before it.