Improve an old website or build a new one: how to decide
A full rebuild is often proposed before anyone checks the current system. The right decision depends on technical constraints, business goals, and long-term support costs rather than design age alone.
This article is based on recurring issues identified while reviewing commercial websites. Examples are generalised and do not reveal information about specific companies.
When improvement is usually enough
- the admin panel works
- key pages can be edited
- forms and calls to action can be changed
- the template has no critical limitations
- valuable content and domain history should be preserved
When a new website may be justified
- the platform is unsupported or insecure
- critical access is missing
- simple changes require expensive legacy-code work
- mobile adaptation is not realistic
- required business scenarios cannot be implemented
What to check first
Identify the CMS, access level, backup options, template-editing capabilities, old plugin dependencies, indexation, and the amount of useful existing content.
Compare more than the initial price
A cheaper repair can become expensive if every later change is difficult. A new website is also wasteful when the current foundation works and a few prioritised stages can solve the problem.
A practical method
Prepare two scenarios: a minimum viable improvement on the current platform and a migration to a new foundation. Compare scope, risks, timing, support, and actual business outcomes.
