# Make old code safe to change again

Page: https://pixelteh.com/services/legacy-modernization · Last updated: 2026-11-19

_Takeovers and modernisation_

If your previous team left or nobody understands the system your business runs on, we take it over. A two-week takeover audit covers code, hosting and security and ends with a written plan. Then we stabilise it, keep it running and modernise it in stages, keeping the old system up until the new one is proven.

## Sounds familiar?

- Your developer or agency left, and nobody else understands the code.
- Every release breaks something that used to work.
- The system runs on versions nobody supports any more.
- You know about security issues and haven't had anyone to fix them.

## What you get

- **Takeover audit**: Code, hosting, security and data reviewed in two weeks. Findings ranked by business risk, in plain language.
- **Stabilisation**: Hosting and support taken over, security holes closed, incidents brought down.
- **Refactoring**: Duplicated, tangled code consolidated into shared parts with tests around it.
- **Framework upgrades**: Old PHP to current Laravel, older Node.js to current versions, riskiest parts tested first.
- **Data and CRM migrations**: Data moved between systems with its history intact.
- **Staged rebuilds**: When a system can't be saved, a new one built from a plan and run in parallel.

## How it runs

1. **Audit**: Two weeks across code, hosting and security.
2. **Present**: Findings ranked by business risk, before any change.
3. **Stabilise**: Security, backups, monitoring and the worst bugs first.
4. **Decide**: Refactor or rebuild, with the trade-off in writing.
5. **Modernise**: In stages, with the old system up until the new one is proven.

## Proof

- [Taking over a legacy platform and rebuilding it without stopping the business](https://pixelteh.com/work/gold-buyback-legacy-takeover): 36 of 36 security issues closed in week one of a legacy takeover
- [Rescuing a live casino, then building its second brand from scratch](https://pixelteh.com/work/crypto-casino-rescue-second-brand): A live casino rescued in under two weeks, then a second brand to 80K users
- [From one augmented developer to the client's entire dev team](https://pixelteh.com/work/news-clips-platform-dev-team): From one augmented developer to the whole dev team of a US media platform

## Engagement

- **Takeover audit**: 2 weeks · One-off
- **Dedicated team**: starts in 1 to 2 weeks · 3-month minimum, one month's notice

[All engagement models and terms](https://pixelteh.com/engagement)

## Stack

php, laravel, node.js, wordpress, java, postgresql, mysql

We take over what you have, then move it to tools any good engineer can maintain.

- [PHP and legacy PHP](https://pixelteh.com/technologies/php)
- [Laravel development](https://pixelteh.com/technologies/laravel)
- [Node.js development](https://pixelteh.com/technologies/nodejs)

## Free check

[Legacy risk check](https://pixelteh.com/tools/legacy-risk-check): How exposed is the system you run on?

## Frequently asked questions

### Can you take over code another team wrote?

Yes. Most of this work starts that way. We begin with an audit and share the findings before we change anything.

### Can we buy just the audit?

Yes. The takeover audit takes two weeks, has a fixed price and ends with ranked findings and a plan you can use with any team.

### Will the business have to stop during a migration?

No. We migrate in stages and keep the old system running until the new one is proven.

### Refactor or rewrite?

Refactoring in place is usually cheaper and safer. We recommend a rewrite only when the audit shows it pays off, and explain the trade-off in writing.

### What if the source code is lost?

It has happened. For one casino operator we rebuilt a working codebase from the compiled build and the files that survived, in under two weeks.
