Replace the old code piece by piece, while the app keeps running.
When an upgrade is not enough, we replace legacy parts in two-week sprints, each with a fixed scope and price. No big-bang rewrite, no frozen roadmap.
When an upgrade is not enough
The framework has no next version
Zend Framework 1, symfony 1, CodeIgniter 3 or a custom framework from years ago: there is nothing to upgrade to.
One part holds everything back
A module written in another era blocks the PHP upgrade for the whole application.
A full rewrite freezes the product
Months of rebuilding what already works, while customers wait for anything new.
The strangler fig method, in plain words
A strangler fig grows around an old tree until it can stand on its own. We do the same with software.
We put a thin routing layer in front of the old application. New code takes over one route or module at a time: first the reports, say, then the API, then checkout. Each step goes live on its own and can be rolled back.
When the old code has nothing left to do, we switch it off. Your users keep working the whole time.
How it runs
01
Roadmap
An inventory of modules, the order of stages, a test plan, the risks, and a fixed price for each stage.
02
Sprint
A fixed scope from the Roadmap. Characterization tests on the old part first, then the new code next to it.
03
Review and release
A demo, the merge requests and a release. You decide whether the next sprint goes ahead.
04
Switch off the old part
Traffic moves to the new code. The old module is removed once nothing calls it.
What you get
Roadmap document
Stages, order, risks and a fixed price for each stage.
Working code every sprint
Live in production after each sprint, used by your customers.
Tests
Characterization tests on the old part, regular tests on the new one.
Sprint report
What moved, what's next, what we learned about the old code.
Architecture notes
How the old and new parts talk to each other, kept up to date.
Time and price
| Price | Duration | |
|---|---|---|
| Roadmap | from €1,900 | set in the quote |
| Sprint | €4,000 | 2 weeks |
Modernization questions
How many sprints will we need?
The Roadmap answers that, with a price for each stage. You don't commit to all of them at once.
Can our team keep building features meanwhile?
Yes, that's the point of the method. Each sprint we agree which areas are ours, so we don't work on the same code.
Which framework do you move to?
Usually Symfony, on the current LTS version. Laravel when your team already works with it. The Roadmap explains the choice for your case.
Can we stop after a few sprints?
Yes. Each stage is finished and in production on its own. Stopping leaves you with a working, partly modernized app, not a half-built new one.
Start with a plan you can price
Tell us what the system does and what it runs on. We'll suggest whether a Code Audit or a Roadmap comes first.