Your PHP application —
safely up to date.
Outdated PHP, old framework, hardly any tests? We move your application to current PHP and a framework with long-term support — in parallel operation, protected by golden-master tests and with a fixed rollback plan.
The risk grows every year
A running legacy application looks stable — until a hosting change, a security flaw or a staff change turns it into a problem.
Four phases, each bookable on its own
You start with the legacy check. Afterwards you decide, with a reliable fixed price, whether and how to continue — also with your own team for individual phases.
Six principles that keep risk small
Distilled from several migration projects — independent of framework, industry and vendor.
What you get — and what you don't
- Legacy inventory: code, dependencies, interfaces, cron, configuration, legacy debris
- Reproducible sandbox (container) with database seed and stubs
- Golden-master cases and differential tests old vs. new
- Working rebuild on current PHP (default 8.4, 8.5 readiness verifiable) and an LTS framework
- CI with quality gates: unit tests, static analysis, code style
- Rollout plan, cutover and rollback concept, stage verification
- Acceptance report and operations documentation
- Functional redesign or UI redesign (possible as a follow-up project)
- New features during migration — feature freeze within migration scope
- Migration of frontend frameworks outside PHP (on request)
- Operation of the target environment (bookable separately, see lifecycle care)
Stay current instead of aging again
After cutover we keep PHP, framework and dependencies in step: regular updates with test runs, early tests on upcoming PHP versions and response to security advisories. Scope and price are agreed with you after the legacy check.
Prices on request · Phases 1–3 as a fixed price based on the legacy check · Offer exclusively for businesses, traders, public authorities and legal entities under public law (§ 14 BGB) — no consumer business (§ 13 BGB)
Good to know
Does the application have to be shut down during migration?
No. The old application keeps running unchanged. The rebuild happens in parallel and is only switched over after acceptance, with a documented rollback.
We have hardly any tests. Is that a knock-out criterion?
No, it is the normal case. Phase 1 builds the safety net retroactively: we record the actual behavior of the old application and test the rebuild against it.
What if third-party systems have no test environment?
We build stubs from interface descriptions (WSDL, OpenAPI, captures). Anything that can only be verified against the real system is explicitly marked open in the acceptance report and checked deliberately during stage rollout.
Which framework and PHP version is the target?
The default is the current PHP version with a long-term-support framework, usually Symfony or Laravel. We choose with you based on the legacy check — a pure PHP version update without a framework change is also possible.
What happens to passwords and credentials?
Existing password hashes stay valid and are upgraded to a current algorithm at the next login (optional, only after the rollback window). Credentials in the repository are reported and rotated together; we never print values in reports.
How is the fixed price calculated?
From the legacy check: code size, number and type of interfaces, cron jobs, existing tests and risks. You get an offer for phases 1–3 with clearly stated assumptions.
How outdated is your application really?
The legacy check delivers a reliable risk picture and a fixed-price offer within a few days — discussed without obligation in an initial call.