Website redesign
Legacy website rebuild
Some websites are past saving: built on software that no longer receives security updates, dependent on a developer who has gone, or so fragile that every change breaks something. Continuing to patch them costs more each year and leaves the business exposed.
We rebuild legacy websites on modern, maintainable foundations, recovering the content and features that matter and switching over without losing visitors.
Illustrative diagram
Legacy website
- Security
- Unsupported software
- Known weaknesses
- Dependency
- One person knows it
- Missing source
- Cost of change
- Simple edits break things
- Compatibility
- Hosting cannot upgrade
When a site becomes legacy
A website becomes legacy when keeping it running is risky or disproportionately expensive. Common signs include software versions that no longer receive security updates, hosting that cannot be upgraded without breaking the site, custom code nobody understands and the inability to make simple changes without help from one specific person.
At that point, careful patching only delays the inevitable. A planned rebuild costs less than an emergency one after a failure or security incident.
Inventorying what the old site does
| Feature type | Question | Typical outcome |
|---|---|---|
| Content pages | Is the content still accurate and used? | Migrate, update or retire |
| Forms | Where do submissions go and are they used? | Rebuild with modern validation |
| Custom tools | Does anyone still rely on them? | Rebuild, replace with a service or drop |
| Member or customer areas | How many active users? | Rebuild carefully or move to a dedicated tool |
| Integrations | Which systems does it exchange data with? | Reconnect or replace |
Getting content and data out
Legacy systems often lack clean export tools. Content may need extracting from the database, from the file system or, as a last resort, from the published pages. Data such as user accounts or form submissions needs particular care, both technically and for privacy.
We always work from copies, document what was extracted and verify counts before the old system is retired.
How a legacy rebuild runs
Assess
Risks, features, content and data inventoried.
Output: Assessment and plan
Extract
Content and data recovered from copies.
Output: Verified extracts
Rebuild
New site built with features that still matter.
Output: New site on staging
Switch and retire
Redirects, launch, then old system archived and shut down.
Output: Secure live site
Interim risk reduction
While the rebuild is planned, reduce exposure on the old site.
Now
- Take a full backup and store it safely
- Remove unused admin accounts
- Change passwords on remaining accounts
If possible
- Disable unused features and forms
- Apply any available security updates
The cost of waiting
Delaying a legacy rebuild rarely saves money. Patches get harder, hosting options narrow and the risk of a security incident grows. Planning the rebuild while the old site still works lets you choose timing, scope and partner calmly, rather than under pressure after something fails.
Choosing a foundation that lasts
The aim of a legacy rebuild is to end up somewhere maintainable. That means widely used, actively supported technology, a structure another developer can understand, documentation, and all accounts held by the business. Exotic platforms or heavily customised code recreate the original problem in a few years.
We explain the chosen foundation in plain language, including why it should remain supportable.
All at once or in phases
Single switch-over
Suits you when
- The old site is small
- Features are simple
Watch out for
- Everything must be ready at once
Phased replacement
Suits you when
- Several features or user groups
- Some parts are more urgent
Watch out for
- Old and new run side by side for a while
Planning the timeline
Rebuild timelines depend most on the assessment's findings: how much content and data must be recovered, how many features are rebuilt and how quickly decisions can be made. Clear ownership of decisions on your side keeps the project moving.
Questions about legacy website rebuild
How do I know if my site is legacy?
Signs include unsupported software, hosting that cannot be upgraded, custom code nobody understands and changes that only one person can make.
Can content be recovered without an export tool?
Usually, from a database copy, the file system or the published pages.
Do we have to rebuild every old feature?
No. Features nobody uses are dropped; important ones are rebuilt or replaced.
What happens to user accounts on the old site?
They are migrated carefully or users are invited to re-register, depending on the systems and privacy considerations.
Will old links still work?
Yes, with redirects from old addresses to their new equivalents.
What happens to the old site afterwards?
It is archived, with a full backup kept, then shut down so it cannot be exploited.
Can old forms keep working during the rebuild?
Yes, unless they are a security risk. If so, a temporary simple contact route can replace them.
Should we fix security issues before rebuilding?
Yes, take interim precautions such as backups, removing unused accounts and disabling unused features while the rebuild is planned.
Can you rebuild while keeping the same domain?
Yes. The domain stays; only the system behind it changes, with redirects for any changed addresses.
Request a Custom Quote
Ask about Legacy website rebuild
Thank you — your enquiry has been sent.
We have received your message and will reply by email. If you need to add anything, email info@letgetgrow.com.