Legacy PHP Maintenance
Support for applications running on old PHP versions, ageing CodeIgniter installs or hand-written code with no framework, kept working safely while GullySystem plans a path to a supported version.
What Counts as Legacy PHP
This covers applications on PHP versions no longer receiving security updates, older CodeIgniter or hand-rolled code with no framework at all, and applications with no dependency manager, so every library was copied in by hand at some point in the past.
Common Problems in Older PHP Applications
- Functions the application relies on have been removed in current PHP versions
- Direct database calls with no protection against malformed input
- No package manager, so every library was copied in by hand at some point
- Passwords and configuration values hard-coded directly into files
- No local copy of the code that matches what is actually running in production
Keeping It Running As Is
Where an immediate version upgrade is not realistic, we can maintain the application on its current PHP version: fixing bugs, applying the security patches still available for that version, and keeping the server it runs on current, while being clear that this buys time rather than removing the underlying risk.
Moving to a Supported PHP Version
Compatibility Review
Checking which parts of the code use functions or patterns removed in newer PHP versions before any upgrade begins.
Staged Upgrade on a Copy
Making the change on a separate copy of the application first, so the live system is not the first place a break shows up.
Server and Extension Alignment
Upgrading the server's PHP installation and required extensions alongside the application code, since the two have to match.
Frequently asked questions
Does legacy PHP need to be rewritten to be maintained?
No. Maintenance keeps the application working as it stands. A rewrite is a separate decision, usually raised only when the code cannot reasonably be patched or upgraded any further.
What decides whether to patch in place or upgrade the PHP version?
How much longer the current version will realistically stay usable, whether the hosting environment still supports it, and how much of the business depends on the application continuing to work without interruption.
What decides the cost of legacy PHP work?
The absence of automated tests, how much custom logic sits outside any framework, and how far the current code has drifted from what a supported PHP version expects.
Can code with no framework and no dependency manager still be supported?
Yes. We read the code as it stands, document what it does, and maintain it directly rather than requiring it to be restructured into a framework first.
What do you need access to for legacy code?
A copy of the running application, server access, and database credentials. If no repository exists, we recover a working copy from the live server before starting.
Who keeps the source code and server access?
You do. Any repository we create from a recovered codebase, along with server and database access, stays under your business's accounts.
Tell us what you need.
Send a short brief and one of our engineers will come back to you — usually the same day.
- No obligation
- We reply the same working day
- Your details stay private