"Our host is ending support for our PHP version"
Don't change the version on the live site. Find the date, take a backup and plan the move.
A message from your host about PHP is easy to ignore and expensive to ignore. When the date arrives, your host may switch your site to a newer PHP version for you, or stop serving it altogether. Old code often breaks on newer PHP, and the first you hear of it can be a white screen.
The good news is that a notice gives you a deadline, and a deadline is something you can plan around.
Book a free conversationLegacy System Assessment, from £2,500
What the notice usually means
Hosts differ, so read yours carefully. The common versions are:
- "We'll upgrade your PHP version automatically on [date]." Your site starts running on newer PHP whether it's ready or not.
- "The version will no longer be available after [date]." It may stop working, or you may be forced to pick a newer option.
- "We're retiring this platform or plan." A bigger move than PHP alone. Your whole hosting setup may be changing.
- "Older versions are still available at extra cost." A bridge, not a fix.
The exact wording and date matter more than anything else. If it isn't clear, ask.
Do these first
- Get the date and the details in writing. Which PHP version are you on, what will it change to, and when?
- Take a full backup now: files and database. Check that you can actually restore from it.
- Don't flip the PHP version on the live site to "see what happens". If the site breaks, your customers see it.
- Find out who built the site and who can change it. If nobody knows, that's a takeover job.
- Check what else depends on the old setup: scheduled jobs, email sending, integrations and plugins.
Questions to ask your host
- Exactly which PHP version is my site running on today?
- What date will it change, and to which version?
- Will you upgrade it automatically, or will I have to choose?
- Can I test a newer PHP version on a copy before the deadline?
- Can I stay on the old version for longer, and what does it cost?
- Does the host still provide security fixes for the old version while it's available?
- Will you keep a backup, and how do I restore it?
Your options
| Option | What it is | Best when | Watch out for |
|---|---|---|---|
| Upgrade the application | Make the code work on a supported PHP version, then switch | You want a lasting fix | Needs testing first. The larger the jump, the more work |
| Pay for extended support | Keep the old version a little longer | You need time to plan | Costs money every month, doesn't fix the problem, and may still fail insurer or audit checks |
| Move to another host | Find a host that still offers the old version | Almost never | Same security problem in a new place. It's a delay, not a solution |
| Replace the system | Move to a different product | The application no longer fits the business | Larger project. Rewrite vs refactor vs upgrade |
| Do nothing | Wait for the deadline | Never | The site may break, at a time you didn't choose |
For most businesses the answer is a staged upgrade, with a short-term bridge if the deadline is too close. PHP upgrade service
How much time do you have?
| Time left | What I'd do |
|---|---|
| Months | Assessment first, then a planned upgrade on a copy, tested properly, switched at a quiet time |
| A few weeks | Fast assessment, fix the blockers that would stop the site working, upgrade on a copy and test. Consider a short extension if your host offers one |
| Days | Triage. Backup, test what breaks on the new version, fix the critical issues, and put a bridge in place if you can. Tell me the exact deadline straight away |
Urgent work is charged at the urgent rate, from £1,300 per day, subject to availability. Planned work is cheaper and calmer. Pricing
What usually breaks
- Removed database functions (
mysql_*) - Language changes that old code relied on
- Abandoned plugins, themes and libraries
- Framework and CMS versions that don't run on newer PHP
- Server extensions, settings and scheduled jobs
You can find most of these before the deadline by testing the site on a copy. What breaks in a PHP upgrade
Not sure which version you're on?
Is my PHP version safe? How to check
Frequently asked questions
Will my site stop working on the date?
It might. It depends on what your host does and whether your code runs on the newer version. The way to know is to test on a copy before the date.
Can I just ask my host to keep the old version?
Sometimes, for a limited time, and often at a cost. Ask what the exact terms are and for how long.
Is it safe to stay on an old version for now?
Not for long. Old versions stop receiving security fixes, and attackers scan for them. A short, planned bridge is reasonable. Staying put indefinitely isn't.
How long does an upgrade take?
It depends on the size, age and complexity of the application. I'll give you a timeline with the quote. The earlier you start, the more choices you have.
Do I need a new host?
Usually not. The usual answer is to make the application work on a supported PHP version, on your existing host or a modern one. Hosting migration
Tell me what you've inherited.
Tell me your PHP version and the date your host gave you. I'll tell you honestly what's realistic.
Book a free conversationLegacy System Assessment, from £2,500