Strangler Fig, in phases
Each phase ships on its own. No freeze, no big bang.
We run phased Strangler Fig migrations on business-critical Laravel, CakePHP and Symfony applications — and on the Vue 2 frontends in front of them. Every phase ships behind an automated parity suite, and no change reaches a pull request without a named senior engineer signing off.
No rewrite. No feature freeze. No data migration.
Book a technical assessmentThe framework is years past end of support, and security questionnaires are starting to fail.
One or two developers hold all the context, and neither can be spared for six months.
A previous attempt stalled halfway, or never started because nobody could estimate it.
Nobody can prove a change didn't break existing behaviour — so nothing gets changed.
Each phase ships on its own. No freeze, no big bang.
Every phase proves the new path behaves like the old one before it completes.
No AI-assisted change reaches a pull request without a named senior engineer signing off. QA validates every cutover.
Architecture decision records, an operational runbook, and a parity report per phase.
CakePHP 4 to Laravel 12, in production since 2018: 256 controllers, 150,000 lines. Strangler Fig over a single shared database — no data migration.
Rewritten alongside the live service, with no data migration and no interruption to it.
Frontend architecture allowing Vue 2 and Vue 3 to coexist, so components migrated gradually with no pause in feature delivery.
Later adopted as the company-wide standard.
Spanish market opened on a legacy Symfony application, with A/B testing running in production on an unsupported Vue 2 frontend.
No rebuild.
A complete technical assessment of the codebase, database, integrations and deployment pipeline, delivered as a written report and presented to your team:
50% of the audit fee is credited against the first phase if you proceed within 30 days. If you decide to run the migration internally, the plan is still yours.
Book a technical assessmentKlim Works is led by Rodrigo Klim, tech lead on the migration described above. Every engagement has a named senior engineer accountable for it.