Legacy application takeover
The developer has left. The application is still running your business.
It happens constantly. The person who built it moves on, the agency closes or loses interest, or the one employee who understood it hands in their notice. The application keeps working, until it doesn't, and then nobody knows where it lives, how it's deployed or what it depends on.
I take over that responsibility. The objective is simple: regain technical control of your own software.
Does this sound like you?
- Nobody can tell you where the application is hosted, or who has the logins.
- The original developer, employee or agency is gone, unreachable or unhelpful.
- You can't make changes without fear of breaking something.
- There's no documentation, no tests, or a code folder nobody has opened for years.
- Other developers have looked at it and declined.
- You were quoted a full rewrite as the only option.
- It's running on old PHP and your host is about to drop support.
- Something has just broken, and nobody knows why.
You don't need to understand any of it. That's what I'm for.
What I do
1. Secure control
First, make sure you actually own and can reach everything the application depends on. I help you establish and recover:
- Source code, and whether it's in version control
- Hosting and server access
- Domain registrar and DNS
- Database and file storage
- Third-party accounts: payment providers, email services, APIs, SSL certificates, monitoring
- Scheduled jobs that run in the background, which are easy to forget about
Missing pieces are common and usually recoverable, but they're far easier to sort out early, while systems are still running.
2. Make it safe
Before anything else is changed, I make sure you can recover if something goes wrong:
- A verified backup of code and data, tested and not just assumed
- A safe working copy of the application to investigate and test on
- Identification of urgent risks: expired certificates, unsupported software, exposed credentials, failing jobs
3. Understand it
I map the application, infrastructure, database, integrations and critical workflows. AI-assisted analysis makes this far quicker than it used to be, but findings are checked against the real running system, not taken on trust. How I use AI
The aim is to answer: What does it do? How does it run? What does it depend on? What's risky? What's valuable? What could safely be left alone?
4. Document it
You end up with documentation that doesn't depend on any one person's memory: architecture, components, database relationships, integrations, deployment, scheduled processes and key business workflows. Documentation service
5. Give you a plan
A prioritised view of what to fix now, what to schedule and what to leave: security, upgrades, technical debt and costs. You decide what happens next. Legacy System Assessment
6. Stay on as technical owner (optional)
If you want, I continue as your technical owner: maintaining, monitoring, updating and developing the application. Ongoing care
Why a takeover often beats a rewrite
When nobody understands a system, a rewrite looks attractive. But an old application often contains decades of business knowledge: pricing rules, customer exceptions, reporting logic and edge cases nobody remembers deciding. Throw the code away and you may throw that knowledge away with it.
I first establish what you actually have. Then we make rational decisions about what to repair, document, secure, upgrade, refactor, replace or leave alone. Rewrite vs refactor vs upgrade
What I'll need from you
Very little, to begin with:
- What the application does and who relies on it
- Whatever you have: hosting account, domain registrar, old invoices, emails from the previous developer, an old backup. Fragments are enough to start
- Contact details for the previous developer or agency, if there's any chance they'll cooperate
- An idea of urgency: is something broken now, or are you getting ahead of a risk?
If you have almost nothing, say so. I can often trace systems from a domain name.
If the previous developer or agency is still around
Even a difficult handover is worth attempting politely. Useful things to request:
- Source code and repository access
- Server and hosting credentials
- Database exports and backups
- A list of third-party services and accounts
- Any notes, however rough
I can help you draft that request and review what you receive. Questions about who legally owns the code or accounts depend on your contract and circumstances. For those, take legal advice.
Data protection
Taking over a system means working with a business's most sensitive data. I work least-privilege and read-only wherever possible, with an NDA and data processing agreement available on request, and prefer limited or sanitised data. Data protection and security
What it costs
Most takeovers start with an assessment: from £2,500, with larger or more complex systems typically £4,000-£7,500+. That gives you control, documentation and a clear plan, with no obligation to continue with me.
After that, work is quoted fixed-price where scope is clear, at £950 per day for open-ended work, or as ongoing care from £2,000 per month. Urgent recovery work starts from £1,300 per day. Full pricing
For agencies
Inherited a client application your team would rather not own? I can take it on white-label, or work direct with your client with you as the referrer. Agency terms
Frequently asked questions
What if we've lost the source code?
It's more common than you'd think. Often it can be recovered or reconstructed from the live server, backups or the hosting account. I'll tell you honestly what's possible once I've looked.
What if we don't know where it's hosted?
Starting from a domain name, DNS records and billing history often lead to the host. Tell me what you have.
The application is old and in a state. Will you really take it on?
Yes, that's exactly the work I specialise in. I'll tell you honestly after a first conversation if it's not something I can help with.
How quickly can you start?
It depends on my availability and how urgent your situation is. If a system is down or at risk, tell me straight away, and we can prioritise. Urgent recovery
Will you change things straight away?
No. I make it safe and understand it first. Changes come after there's a backup, a working copy and ideally tests.
Will I be tied to you?
No. The documentation and code remain yours. You can hand everything to another supplier or an in-house team at any time.
Tell me what you've inherited.
You don't need to know exactly what's wrong. If an important application has become a mystery, that's enough to start.
Book a free conversationLegacy System Assessment, from £2,500