PHP upgrade service
Upgrade PHP 5.6 to PHP 8
A business application built for PHP 5.6 may still be useful. I assess the existing code and adapt it for a supported PHP 8 release where that is the practical path.
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
Can production move straight from PHP 5.6 to PHP 8?
It can. Production does not necessarily have to run each intermediate release, provided the code has been adapted and tested for the destination. The changes in skipped releases still matter. Framework or library upgrades may need intermediate steps in development.
PHP 5.6 is no longer supported by the PHP project. A host continuing to offer it is not the same as upstream maintenance. Choose the destination by its support window, hosting availability and application compatibility. PHP 8.0 is not a suitable endpoint merely because it starts with an 8; consult the official supported versions.
Where the compatibility work can sit
Database access
The old mysql_* extension was removed in PHP 7. Code using it needs attention, but that does not automatically mean replacing the database itself.
Error handling and language changes
Error classes and exception handling changed across releases. Existing handlers need review alongside removed functions and later changes to type handling.
Libraries and framework versions
Copied library directories matter just as much as Composer packages. We need to establish which versions can run on the target PHP runtime and whether required extensions remain available.
The official PHP 7.0 incompatibility guide and PHP 8.0 incompatibility guide provide examples. The actual migration must also account for the other releases between the starting version and the chosen destination.
Custom code does not need a framework first
An application built from individual files can be adapted directly. Introducing Composer, Symfony or Laravel is not a prerequisite for changing the PHP runtime. Read about upgrading PHP without a framework.
With framework applications, runtime and framework compatibility must be considered together. A framework upgrade may be part of the scope without becoming an architecture replacement.
Preparing for the production switch
Agree which workflows matter: forms, logins, administration, exports and scheduled jobs. Establish a separate test environment, usable file and data backups, required extensions and the host’s available PHP configuration. Decide how the release will be checked and rolled back if necessary.
Loading the homepage is not enough. A background job or a rarely used form can execute code that normal browsing never reaches.
A completed PHP 5.6 to PHP 8.4 upgrade
I adapted an individually developed website with no framework to run on PHP 8.4. The existing application was retained. Read the anonymous case study.
That project demonstrates a possible outcome, not a fixed scope for another codebase. See the PHP upgrade service and process for the next step.
FAQ
Can we keep the database?
Possibly. Application code, database drivers and the database server are separate concerns. Their versions and usage determine whether changes are necessary.
Do we need a complete specification before contacting you?
No. Start with the system information you have. We identify the important workflows during assessment and test planning.
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.
