LEGACY SYSTEMS
A legacy PHP upgrade without starting over
Your application still runs on PHP 5 or 7. The hosting provider wants to upgrade, or will soon simply do it. Rebuilding is expensive and often not needed. I bring the existing code to the newest PHP version with the longest support. That puts you years ahead again.
Why now
- PHP 7.4 and older have not had security updates for years.
- Hosting providers switch off old PHP versions, or charge extra for extended support.
- New packages and libraries no longer work on the old version, so even small changes get difficult.
How I approach an upgrade
- I set up the application locally and find out what no longer works on the new PHP version: removed functions such as
mysql_*, stricter types and warnings that are now errors. With static analysis and a code scan I see that up front, not when it fails live. - I update the code and the packages step by step, so the application keeps working along the way.
- Are there passwords or API keys in the code? I take them out and store them safely outside the website, readable only by the server.
- I test on a copy of your production environment. Only when everything works does the new PHP version go live, and the old one stays ready. Where possible, the checks stay in place afterwards: on every change, static analysis, code scans and tests run automatically, and an update only goes live when everything passes.
What I upgrade
Custom PHP, and custom WordPress plugins and themes. A Laravel application? See Laravel upgrade. Is your site running on Drupal 7? Then see Drupal migration.
In practice: a training company
A training company had its own PHP site with a CMS, custom-built years ago. The site ran on an old PHP version.
Brief
The hosting dropped the old PHP version, and on a newer version the site threw errors. Rebuilding was expensive and not needed: the site did exactly what it had to do.
Approach
First a full backup of the files and the database. Then a local copy with the same settings as the hosting. I scanned the code automatically for everything that no longer works in newer PHP versions and fixed it. Passwords and API keys were sitting in the code. I took them out and stored them safely outside the website, readable only by the server. I tested every public page, every CMS page and the booking form, before and after.
Result
The site runs on a current PHP version that will be supported for years, without errors. The CMS works the way it always did. And passwords and keys are no longer in the code, but stored safely apart.
Frequently asked questions
Does everything need to be rebuilt?
Usually not. Most code can be brought to PHP 8 with targeted changes. If part of it really cannot be saved, you will hear that up front.
How long does an upgrade take?
That depends on the size and the state of the code. After a first analysis I can give an estimate.
Can it be done cheaper?
Is it a website that hardly changes anymore? Then I can also convert it to static HTML. It looks the same and keeps running, but without PHP and a database online. That is secure, and cheaper than an upgrade. For an application with a login or forms that does not work: it really has to move to a new PHP version.

A legacy application?
Tell me which PHP version it runs on and what it does. You will hear from me.