Server and hosting migration for legacy PHP applications
Move your application to a modern, supported server without a night of crossed fingers.
Old applications are often tied to old servers: unsupported operating systems, outdated databases, shared hosting that's being retired, or a box that one person set up years ago and nobody dares touch. When the host says "we're dropping your PHP version", you have a deadline you didn't choose.
I plan and carry out the move so that the application keeps working on the other side.
When you need this
- Your host is retiring your PHP version, or the whole platform
- Your operating system is end of life. Releases such as CentOS 7 and older Ubuntu LTS versions no longer receive security updates
- Your database is out of support, for example MySQL 5.7
- You're on shared hosting or cPanel and have outgrown it, or it's being switched off
- The server is slow, unstable or full, and nobody knows what's on it
- A server was built by someone who has left, with no documentation
- You want to change provider, for cost, performance, support or data location reasons
- A security review has flagged the server as a risk. PHP security audit
Why migrations go wrong
Most problems come from what nobody knew was there:
- Forgotten cron jobs and scheduled tasks that silently stop
- Hard-coded paths, hostnames and IP addresses in old code
- PHP extensions and server settings the application quietly depends on
- Email sending that breaks when the server's address changes
- DNS and SSL certificates handled by someone else, somewhere else
- File uploads and generated files stored outside the code folder
- Database differences between old and new versions
- Third-party services that allow-list your old IP address
A good migration finds all of these before the switch, not after.
How I migrate safely
1. Inventory
I document what's on the current server: the application, databases, files, scheduled jobs, services, email, DNS, certificates and integrations. AI-assisted analysis helps surface hidden dependencies in the code, checked against the live server. How I use AI
2. Choose the target
I recommend a destination that fits your needs and budget, such as a managed host, VPS or cloud platform, and I'm provider-neutral. For personal data, location matters: I'll help you choose UK or EU hosting where that's relevant to your obligations. Data protection and security
3. Build and configure
The new environment is built on a supported operating system and PHP version, with a secure configuration, backups, monitoring and access controls from day one.
4. Upgrade what has to change
If the application can't run on the new platform as it is, the necessary PHP, framework or database upgrades are done in a controlled way. PHP upgrades
5. Copy and test
The application and data are replicated to the new server without touching the live one. You and your team test the new site, while the old one carries on working.
6. Plan the cutover
We agree a quiet time and a plan: data freeze, final sync, DNS change, checks. DNS timings are lowered in advance so the switch is quick.
7. Switch, with a way back
The cutover is carried out and checked. The old server stays in place, untouched, as a rollback option until you're confident.
8. Monitor and decommission
I watch the new environment, deal with teething issues, and only then help you retire the old server securely, including wiping data.
Database migrations
Moving from an end-of-life database, such as MySQL 5.7, to a supported MySQL or MariaDB version needs care: character sets, SQL modes, deprecated syntax and query behaviour can all differ. I test queries and data against the new version before the switch.
Typical results
- A supported, patched server that satisfies insurers and auditors
- Documented infrastructure, so you're no longer dependent on one person's memory
- Working backups and monitoring
- Often better performance, with modern PHP and database versions
- A clear ownership of accounts and access
What it costs
Hosting costs are separate and paid directly to the provider. My work is quoted as a fixed price once I understand the system, usually following an inventory or a Legacy System Assessment, from £2,500. Open-ended infrastructure work is £950 per day. Urgent migrations, such as a host deadline that's days away, start from £1,300 per day, subject to availability. Pricing
For agencies
Got a client stuck on a host that's dropping support? I can handle the migration white-label or direct. Agency terms
Frequently asked questions
Will the website go down?
Not for the build and testing. The final switch is planned for a quiet time and is typically brief. The old server stays available as a fallback.
Can you migrate us from cPanel or shared hosting to a VPS or cloud?
Yes, that's a common job. I'll tell you honestly whether the extra control is worth the extra responsibility, and I can look after the server afterwards. Ongoing care
Our host says we have two weeks. Is that enough?
It may be. Tell me the exact deadline and the PHP version involved as soon as possible, and I'll say what's realistic. Sometimes a short-term arrangement is needed first.
Which host or cloud should we use?
It depends on your needs, budget and data-location requirements. I'm not tied to any provider and will recommend what fits.
What about email and DNS?
They're part of the inventory. Email in particular is a frequent migration trap, and I plan for it explicitly.
Do you need to upgrade the application as well?
Sometimes. If it can't run on a supported platform as it is, yes. I'll tell you what's essential and what can wait.
Tell me what you've inherited.
Tell me where it's hosted now, what's changing and by when. I'll tell you honestly what the move involves.
Book a free conversationLegacy System Assessment, from £2,500