Look beyond the version number
Running an older release does not always mean an immediate rebuild is required. The important questions are whether it remains supported, can be patched safely and still allows the organisation to operate and improve the website confidently.
Signs that action is becoming necessary
- Security or platform support is ending or has already ended.
- Routine content or functionality changes have become slow and risky.
- Important integrations or hosting services are becoming incompatible.
- The editing experience is creating avoidable work for the content team.
- The current website no longer supports the organisation’s customer or commercial plans.
Upgrade, rebuild or modernise in stages?
The correct route depends on the condition of the current platform. A well-structured site may justify a focused upgrade. A heavily customised or poorly understood implementation may be safer to rebuild. A large service may need a staged transition so that risk and cost remain manageable.
Before deciding, review the content model, bespoke functionality, integrations, search visibility, hosting, deployment process and current support position. The assessment should identify what can be retained as well as what needs to change.
Protect the business during the move
Content, redirects, analytics, accessibility and important customer journeys should form part of the migration plan from the beginning. An upgrade is successful when the organisation gains a safer, easier-to-change platform without losing the value already created by the existing site.