Upgrade your PHP version: from PHP 7 or 8.0/8.1 to a supported version.
If your application runs on a PHP version without security updates, newly discovered vulnerabilities stay open. I move the application step by step to a supported version, backed by tests and without downtime, with over six years of experience in PHP development.
Your PHP version no longer receives security updates.
According to php.net, security support ended on 28 November 2022 for PHP 7.4, on 26 November 2023 for 8.0 and on 31 December 2025 for 8.1. For PHP 8.2 it ends on 31 December 2026. After that, newly discovered vulnerabilities are no longer fixed, and libraries and frameworks gradually drop old versions. Some hosting providers and Linux distributions deliver updates for longer, but that does not solve the problem of the dependencies.
Your application runs on a supported PHP version, with current dependencies and tests that make future updates routine.
- Who it is for
- Operators of PHP applications on PHP 7.x, 8.0, 8.1 or 8.2, such as custom portals, shops or business software.
- How you recognise success
- The application runs on a supported PHP version, and the next upgrade can be planned.
What you get
-
Assessment
PHP version, Composer dependencies and whether they support newer versions, deprecated functions, server and deployment.
-
A safety net of tests
Tests capture today’s behaviour of the most important processes before code is changed. That way you notice if the upgrade changes anything.
-
Migration with tools
Recurring changes automated with Rector, static analysis with PHPStan for type errors and legacy code. What the tools do not cover is migrated and checked by hand.
-
Delivery without downtime
Version jumps in stages, tested on a copy of the environment, switch-over with a prepared way back.
Exactly what you need?
Tell us briefly what it is about. You get a personal reply with the next steps.
How it works
- Check
Record version, dependencies and deprecations.
- Secure
Write tests for the most important processes.
- Migrate
With Rector and PHPStan, version by version.
- Deliver
Test on a copy, then switch over.
Frequently asked questions
Your question is missing? Call us or write to us.
When does my PHP version become a risk?
As soon as its security support ends, newly discovered vulnerabilities are no longer fixed. php.net publishes the dates on its “Supported Versions” page.
Can I jump straight from PHP 7.4 to a current PHP 8 version?
Technically often yes. It is usually safer in stages, because behaviour has changed between versions and dependencies have to follow. The assessment shows which order makes sense.
What about frameworks such as Laravel or Symfony?
Newer framework versions require newer PHP versions, and older ones often do not run on new PHP. Framework and PHP are therefore planned together and updated step by step.
Does the application have to go offline?
Usually not. The migration is prepared and tested on a copy; the actual switch-over is short and has a prepared way back.
Who does the work?
I do, Moritz Schacke. I have over six years of experience in PHP development and handle assessment, tests and migration personally. You have the same contact from the first call to the handover.
What does a PHP upgrade cost?
It depends on size, dependencies and existing tests. The first call is free; after the assessment you receive an offer with a fixed scope. For large applications a paid modernisation check comes first.
First understand. Then build.
Briefly describe your situation and goal. You get a personal reply with the questions that matter for a sensible scope.