Moving a live site off an end-of-life server

The short answer: don't upgrade the old server in place. Build a new one alongside it, copy everything across, match the settings, test every site on the new one, then switch over in a minute or two and keep the old server ready to switch back. Done that way, customers don't notice.

When a server's operating system runs out

Like PHP, every server operating system gets security updates for a set time, then stops. These are the ones we still find running business sites:

Operating systemStandard updates ended
CentOS 7June 2024
Ubuntu 16.04April 2021
Ubuntu 18.04May 2023
Ubuntu 20.04May 2025

Ubuntu sells extended security updates for older releases through Ubuntu Pro, which buys time. CentOS 7 has nothing comparable.

An old operating system usually means old PHP and an old database too, because they come as a set. So moving the server is often the moment to upgrade the PHP as well.

How we move a live server

Switch-over checklistHow we did it in October 2026
  1. Snapshot the old server, so there's a copy of exactly how it was.
  2. Build the new one alongside it, on a supported operating system and PHP.
  3. Copy every site and database, and match the old database settings so nothing behaves differently.
  4. Move the scheduled jobs, but never run them on both servers at once.
  5. Test every site on the new server privately, before anyone else sees it.
  6. Do a final copy of anything that changed, then switch: move the server's address, or the DNS.
  7. Fully restart the web server after any PHP update, not just reload it.
  8. Keep the old server stopped, not deleted, until everyone's happy.

The bits that catch people out

Database settings. A newer database can be stricter about dates, text encoding and capital letters in table names. Match the old settings first, tighten them later.

Scheduled jobs. If both servers run the nightly invoice run, customers get two invoices. Turn them on in one place only.

Email. Sites that send mail from the server itself need the new server set up to send it properly, or the emails land in spam.

The restart. One server we moved reported itself patched and wasn't: its web server had only reloaded, so it kept running the old PHP in memory. A full restart sorted it.

If you can move the server's address instead of waiting for DNS, the switch takes a minute and the way back takes another.

That's how we moved a whole estate onto supported servers in one night when a critical PHP flaw left no other option. The full story is here. If yours needs moving, a System Review tells you what's on it and what it would take, at a fixed price.

← Old software nobody will touch: keep, fix or replace

Server out of support?

Tell us what's on it and we'll tell you what moving it takes.

Which server or host, roughly what runs on it, and whether you know its operating system. If you don't, that's fine: finding out is step one.

What we will cover:

  • What's on it and what it runs
  • A switch-over plan with a way back
  • A fixed price before anything starts

Rather talk now? Book a call or ring 01474 639 089.

We reply within one working day.

Get in touch