Choosing a provider
Legacy website rebuild services
Rebuilding a legacy website needs a partner who is comfortable reading old, undocumented systems and patient enough to understand what they do before replacing them. It also needs one who builds something that will not become the next legacy problem.
This page explains how to choose that partner and what their assessment should tell you.
Illustrative diagram
- Summary — versions, hosting, age
- Critical finding — for example unsupported software
- Evidence
- Recommendation
- Features, automations and data
- Rebuild plan and estimate
Investigation before quotation
Legacy systems hide surprises: a form that also emails a supplier, a script that updates prices nightly, a members area used by a handful of important clients. A partner who quotes without investigating may miss these until after launch.
A paid assessment, reviewing code, database, integrations and usage, usually costs a fraction of the rebuild and makes the rebuild quotation reliable.
What the assessment should tell you
| Finding | Why it matters |
|---|---|
| Software versions and support status | Shows security urgency |
| Features and who uses them | Decides what to rebuild |
| Hidden automations and integrations | Prevents silent breakage |
| Data held and how to extract it | Plans privacy-safe migration |
| Recommended approach and estimate | Basis for a confident decision |
Questions for a rebuild partner
About the old site
- How will you find features nobody documented?
- How will you handle user data?
- What if you find something we did not know about?
About the new site
- Why this platform, and how widely is it supported?
- What documentation will we receive?
- Could another developer maintain it?
Not creating the next legacy site
Legacy problems usually start with choices that seemed reasonable at the time: a niche platform, custom code without notes, accounts held by one person. A good partner avoids repeating them by choosing widely supported technology, documenting the build, keeping all accounts in your name and using version control.
Ask how the new site could be maintained by someone else in five years. A clear answer is the best sign the rebuild will last.
Warning signs
Fixed price without looking
Legacy surprises will appear as change requests or cut corners.
Proprietary replacement
Another system only the provider can maintain.
Old site switched off immediately
No safety net if something was missed.
Handling data responsibly
Old sites often hold personal data nobody remembers collecting: years of form submissions, old accounts, mailing lists. A rebuild is a chance to decide what to keep under your retention rules and to delete what is no longer needed, with a partner working from secure copies throughout.
How a rebuild engagement runs
Assessment
Code, data, integrations and usage investigated.
Output: Assessment report
Plan
Features to rebuild, replace or drop agreed.
Output: Rebuild plan
Rebuild
New site built and data migrated from copies.
Output: Verified new site
Retire
Switch-over, redirects, archive and shutdown of old site.
Output: Secure, documented site
An honest assessment includes alternatives
Not every old site needs a full rebuild. Sometimes upgrading software, moving hosting or replacing one fragile component is enough. A trustworthy partner includes those options in the assessment, with their risks, even when they mean less work for the partner. You can then choose based on evidence rather than on what someone wants to sell.
What you should own at the end
At the end of a rebuild you should hold the domain, hosting and every service account in your name, a copy of the code in a repository you control, documentation of how the site works and the archived export of the old system. With those, you are never dependent on one person again.
Questions about legacy website rebuild services
Why pay for an assessment first?
Legacy systems hide undocumented features. An assessment makes the rebuild quotation reliable and reduces surprises.
What if the original developer is unavailable?
We investigate the code, database and hosting directly. It takes longer but is usually possible.
How is old personal data handled?
From secure copies, keeping only what your retention rules require and deleting the rest.
How do we avoid the new site becoming legacy?
Widely supported technology, documentation, version control and all accounts in your name.
Can the old site stay up during the rebuild?
Yes, with interim security precautions, until the new site launches.
What if the assessment shows the old site can be repaired?
Then we will say so and quote for the repair instead.
Can you work on a site written in an old programming language?
Usually we can read it well enough to understand what it does, which is what a rebuild needs.
Do you sign confidentiality agreements for old systems?
Yes, where required. Send it with your enquiry.
Will you provide documentation?
Yes. Handover notes explain the new site's structure, accounts and common changes.
What if the old site has no backups?
Taking a full backup is the first step, before any investigation or change.
How long does an assessment take?
It depends on the size and complexity of the old system. We give a timeframe once we know what it runs on.
Request a Custom Quote
Ask about Legacy website rebuild services
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.