PHP upgrade service
Upgrade PHP 7.4 to PHP 8
Your host requires PHP 8, but the application still runs on 7.4. I identify the code and package changes needed before switching the production runtime.
Your PHP version, hosting setup and any error message are usually enough to start the conversation.
I’m Stefan Pilz, a PHP and Shopware developer based in Paphos, Cyprus. I help companies and agencies take over, upgrade and maintain existing PHP software remotely across Europe and worldwide.
- Building PHP websites since 2004
- Work directly with the developer
- Custom applications welcome
- Framework optional
Why changing the hosting setting is not the whole upgrade
PHP 7.4 is no longer supported by the PHP project. Moving to PHP 8 can expose more than obsolete syntax: previously tolerated input and changes in comparisons can affect behaviour. The application needs a compatibility check before the production switch.
The destination should be a currently supported PHP release that fits the project. Reaching PHP 8.0 alone is not the objective. Changes in later releases up to the selected target also belong in the assessment.
What makes the 7.4 transition distinctive?
Type handling and errors
Some internal functions handle invalid arguments more strictly and can throw a TypeError where older code produced a warning. Real input values and data from external systems matter when testing these paths.
Comparisons and business outcomes
Comparisons between numbers and non-numeric strings changed. A page may load successfully while following a different branch of business logic. Test expected outcomes, not just HTTP responses.
Composer constraints
A project can already use Composer and still be held back by one outdated dependency. I review version constraints and installed packages together. Ignoring a PHP requirement does not make a package compatible.
The official PHP 8.0 incompatible changes are a starting point, followed by the migration notes through the selected target release.
Keep the first engagement focused
Establish the runtime, package versions and important workflows first. Make changes in a test environment, then check the application’s relevant logins, forms, calculations, imports and background jobs.
Web requests and scheduled jobs need the intended runtime and extensions after the switch. Backups, a release window and a rollback plan are agreed beforehand. If production is already failing, start with diagnosing a site broken after a PHP upgrade.
Preserve the application where it still serves the business
A PHP 7.4 upgrade does not automatically require new architecture. For older Symfony, Laravel or CakePHP projects, the framework assessment establishes whether additional version steps are needed.
New APIs and features can follow as separate work. Explore the PHP upgrade service or broader legacy modernization.
FAQ
Can we just hide warnings?
No. Hiding a message does not resolve its cause. Errors should be logged and the underlying behaviour assessed.
Must the upgrade include new features?
No. The scope can focus on preserving existing functionality on the supported target version.
Tell me what your PHP application needs
Your PHP version, hosting setup and any error message are usually enough to start the conversation.
If available, include the target PHP version and a short description of the application. You do not need a complete specification to get in touch.
