Old PHP websites kept running safely
When your host drops PHP 5 or PHP 7, we can keep the site online in an isolated setup.
In plain English.
Hosts regularly retire old PHP versions, and when they do, sites built years ago can stop working overnight. You might see a blank white page, a database connection error or a wall of deprecated function warnings. Often the business still relies on that site, and a rebuild is not something you can arrange this week.
We set up legacy PHP versions, including PHP 5.6 and 7.x, in separate containers so an old site cannot affect anything else on the server. A web application firewall (a filter that blocks common attacks), strict file permissions and Cloudflare in front reduce the risk that comes with software that no longer gets security fixes.
This is a bridge, and we say so plainly. Alongside the hosting we can look at what it would take to bring the code up to PHP 8, or to rebuild the site, and give you a fixed quote for either so you can choose when to act.
It suits you if.
- Your host has told you they are removing an old PHP version
- Your site shows errors after a PHP upgrade
- You rely on a custom PHP system nobody has touched in years
- You need time and budget to plan a proper upgrade
What we do.
Old PHP, kept apart
Each legacy site runs in its own isolated environment with its own PHP version, so outdated code is fenced off from other sites.
Extra protection
Firewall and Cloudflare rules block common attacks aimed at old CMS versions and known PHP flaws.
Honest risk notes
We list the known issues with your PHP version and software, so you can make an informed decision about how long to stay on it.
Old MySQL behaviour matched
Sites that rely on older MySQL settings, such as strict mode being switched off, are configured to match so queries keep working.
A route to PHP 8
When you are ready, we can upgrade the code to PHP 8.3 or rebuild the site, testing on a copy before the live site changes.
How it runs.
- 01
Tell us what broke
On a free call, tell us what the site is, what PHP version it needs and what has stopped working. We check whether it can be hosted safely.
- 02
Copy and match
We copy the site, match the PHP and database settings it expects, and fix any small errors caused by the move.
- 03
Lock it down
Firewall rules, file permissions and Cloudflare are put in place before the site goes live on the new server.
- 04
Plan the upgrade
Once it is stable, we talk through upgrade options and timing, with no pressure to rush.
Questions people ask.
Is it safe to keep running PHP 5?
It carries risk, because PHP 5 stopped receiving security fixes years ago. We reduce that risk with isolation, a firewall and tight permissions, but we cannot remove it. That is why we treat legacy hosting as a stopgap and help you plan a move to a supported version.
How much does legacy hosting cost?
It is priced per site after a free call, because the setup depends on the PHP version, the database and how much protection the site needs. We agree the monthly fee up front, and any upgrade work is quoted separately.
Can you upgrade my site to PHP 8 instead?
Often, yes. We test the code on a copy, fix deprecated functions and old database calls, and check every page and form. For sites built on very old frameworks, a rebuild can work out cheaper, and we will say so if it does.
Do I need to send you the original code?
No. We can copy everything from your current server. If you also have the original source files or a developer's notes, they help, but most legacy sites can be moved from a working server copy alone.
Your next chapter starts with a conversation.
Nottingham & Derby / UK-wideLet’s build
what’s next.
15 minutes with Garreth.
A real conversation about your business.