PHP update for legacy applications

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.

No more security updates
PHP 7.x, 8.0 and 8.1 are out of support, 8.2 ends in late 2026. Open vulnerabilities are no longer fixed — your host, your insurer and your customers will ask.
Framework and libraries age along
Old framework majors and dependencies don't run on new PHP. Every year of delay makes the jump bigger and the pool of developers smaller.
Operations and knowledge depend on a few people
Hand-maintained servers, cron scripts, credentials in the repository, hardly any tests: the risk lies less in the code than in the missing safety net.

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.

Phase 0
Legacy check
Inventory of code, dependencies, interfaces, cron and configuration. Risk picture, target picture, fixed-price offer for phases 1–3.
Phase 1
Safety net
Sandbox with database seed and stubs for third-party systems. The behavior of the old application is recorded as a golden master.
Phase 2
Migration
Rebuild on current PHP using the strangler pattern next to the old application. Differential tests old vs. new, quality gates in CI.
Phase 3
Rollout & cutover
Stage verification, cutover with a rollback window, handover with documentation. The old application stays untouched until sign-off.

Six principles that keep risk small

Distilled from several migration projects — independent of framework, industry and vendor.

01
The old system is the truth
We don't improve business logic on the side. Behavior is pinned down as a golden master and rebuilt 1:1. Functional oddities are reported, not silently fixed.
02
Parallel operation instead of big bang
The old application keeps running unchanged while the new one is built next to it (strangler). We only switch after acceptance — with a way back.
03
Third-party systems as stubs
SOAP, REST and file interfaces are replaced by stubs in the sandbox. That lets us test reproducibly without touching production systems.
04
Differential tests old vs. new
The same inputs go through both systems, deviations are classified. Intended differences are written down in the acceptance report.
05
Take security along
Credentials out of the repository, password hashes migrated by rehash-on-login, unsafe output closed — without locking out existing users.
06
Evidence instead of claims
Every statement in the acceptance report has proof (test run, commit, check log). What wasn't verified is listed as “not proven”.

What you get — and what you don't

Included
  • 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
Not included
  • 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.