Legacy Modernization & PHP Upgrades

We bring old PHP applications — and not only PHP — onto the latest supported versions: we adapt existing code and rewrite only what cannot be carried over.

Overview

We take on applications that still make money but run on PHP versions that are out of support, or can no longer be changed safely — including applications written in other languages. We bring them onto the latest officially supported versions. We do not start with a rewrite from scratch: we adapt the existing code and rewrite only the parts that cannot be carried over. And the first step is always the same — we put the system under test and make it start reproducibly on any machine.

Legacy Modernization & PHP Upgrades

We bring old PHP applications — and not only PHP — onto the latest supported versions: we adapt existing code and rewrite only what cannot be carried over.

PHP 8.5PHP 8.4RectorPHPStan
Use cases

PHP 8.1 or older, on a public server

On a version that is out of support, every vulnerability found afterwards stays open, and its details become public. On 21 October 2026 the PHP project fixed two critical vulnerabilities that allow unauthenticated remote code execution, and published fixed releases only for 8.2–8.5. PHP 8.1 and older no longer receive updates.

Applications in other languages, on abandoned versions

The same problem outside PHP: code stuck on a language or framework version that no longer receives patches, and that nobody has dared to upgrade.

Applications with no dev environment

Systems that run on exactly one server, where nobody dares touch anything.

Taking over after the team left

Code with no documentation and no original author available.

Key benefits

The business keeps running

We modernise piece by piece, old and new running side by side. There is no single day when everything changes.

On a version that still gets patches

We move the application to the latest stable PHP release, not to one that drops out of support in a few months. Existing behaviour is pinned down in tests before the upgrade, so any difference shows up in CI, not in production.

Risk measured, not guessed

The opening audit states what is covered by tests, what is not, and which dependencies are out of support.

How we work

  1. 01

    Discovery

    We map the current system, its constraints and the business goals before proposing anything.

  2. 02

    Architecture

    We design the structure, data model and integration points. Decisions get documented, not improvised.

  3. 03

    Implementation

    Delivered in short iterations, with reviewed code and a staging environment you can see at any time.

  4. 04

    Testing & QA

    Automated tests plus performance and security checks before every release.

  5. 05

    Launch & support

    We ship with a rollback plan, then stay on for monitoring and iteration.

Technologies

8 tools
PHP 8.5
PHP 8.4
Rector
PHPStan
Strangler Fig
Docker
CI/CD
PHPUnit

Want to talk through your project?

Tell us where you are and where you need to get to. You get a concrete assessment back, not a templated reply.

Request an assessment