Redesign or a new website: choosing the next step
What to keep and what to rethink: content, interface and technical foundations.
Identify what prevents the site from doing its job. A visual refresh can fit when structure and technology work well. Deeper limitations call for a broader review.
01. Name the specific problem
Don’t start by deciding to replace everything. Identify the difficulty: customers do not understand the offer, the mobile form is awkward, or the team cannot update the catalogue.
Break “the website is outdated” into observations you can check. Do people fail to find a service? Can editors update a price? Is a button covered on phones? Record an example and operational impact for each issue. Navigation, copy or form changes may resolve some problems. If the current system cannot support necessary roles or integrations, a visual refresh will not remove that limitation. Diagnose the problem before choosing the scope.
02. Review the foundations
Review content structure, main journeys and the current system’s capabilities. A technical audit helps distinguish local issues from architectural limitations.
Review the CMS and extensions, data structure, update path, editorial workflow and connected systems. Investigate performance causes separately: images, third-party scripts or the server may be responsible rather than the whole platform. An audit should explain which issues can be fixed locally, which need structural changes and what remains unknown. The age of a site alone does not determine whether it needs rebuilding. Evaluate its ability to support the agreed requirements.
03. Decide what to preserve
Useful content, important URLs, customer data and integrations can remain valuable even when the interface changes completely. List materials and data to migrate before work starts.
Inventory pages, files, products, accounts and integrations. Where data is available, identify URLs bringing enquiries, traffic or external links. Changed addresses need a mapping from the old page to its relevant replacement. Do not send every old page to the homepage; visitors should reach equivalent content. Valuable material can be retained and improved even when the interface and technology change entirely. Migration is a separate workstream, not an automatic consequence of a new design.
04. Compare scope and risks
Compare updating the current solution and building a new one against the same requirements. Consider data migration, support and future changes as well as the initial estimate.
Compare design, implementation, content, migration, integrations and post-launch checks. A lower initial estimate may omit important dependencies. Ask what remains from the current solution and which limitations still apply. For a rebuild, clarify which data and journeys will be reproduced. Compare future editing and development capabilities, not only the homepage appearance. A useful decision includes explicit assumptions and risks so both options are assessed against the same operational outcome.
05. Test migration before switching
Run a trial migration and compare relationships as well as record counts. A product without a category or a document without an owner may exist in the database but fail in the real journey. Check images, languages, important URLs and integrations. Agree how to handle data added to the old site after the trial. A rollback plan must cover data as well as interface files; otherwise a technically successful switch may still disrupt ongoing work.
06. Choose the smallest sufficient scope
For a local issue, start with a focused improvement and check its effect. When the foundation cannot support agreed requirements, a rebuild may be more appropriate. A staged route also exists: improve the main journey, then the editorial workflow and remaining sections. It requires compatible parts and a clear plan. After launch, compare against the original problem: can people find a service, edit the catalogue or complete an enquiry more easily? The decision should remain tied to those tasks.
A guide to choosing the scope
| Situation | What to consider |
|---|---|
| The foundation works; copy or navigation causes problems | A focused structure and UX improvement. |
| The appearance needs changing, not the business logic | A redesign with checks of existing journeys. |
| The CMS or architecture blocks essential features | Structural changes or a rebuild following an audit. |
| Important data and an ongoing flow of orders | A separate migration, verification and rollback plan. |
