Hosting Migrations, With a Way Back.
Moving hosts means dozens of sites, databases, email, DNS and scheduled jobs, and nobody wants to find out what breaks. I plan the move, rehearse it on the new servers, and switch over once everything has been checked. The old host keeps running until you're happy.
- Moves
- Between providers, off managed hosting, onto fewer servers
- Method
- Inventory, rehearsal, switch-over, two weeks' stabilisation
- Downtime
- Usually none: a DNS switch after testing
- Price
- A fixed quote, in writing
The Usual Moves
For agencies whose per-site bill has grown with every client they win. The sites move onto servers you own, patched and monitored by me.
Apps and databases moved to servers or containers you control, with deploys still running from your own pipeline.
Steady workloads moved to where they cost least, or several accounts brought into one.
Sites, mail and databases moved off an old box onto a current, supported one. Upgrades in place →
Servers set up one at a time over the years, brought onto a standard build that is easier to patch and cheaper to run.
Dozens of client sites moved a few at a time, each one checked and signed off before the next.
How a Move Runs
- Inventory
Every site, database, scheduled job, mailbox, DNS record and integration listed, so nothing turns up missing afterwards. You get a written scope and a fixed quote.
- The new servers
Built, secured, monitored and backed up before anything moves onto them.
- Rehearsal
The data copied across and every site tested on the new servers through a preview address, before any DNS changes.
- The switch
DNS timings shortened in advance, a final sync, then the switch at a time you agree. The old host keeps running, so going back is one change.
- Two weeks' stabilisation
Anything that turns up is fixed as part of the job. The old host is cancelled only when you're happy.
Moving to Save Money
Often the reason to move is the bill.
Per-site and per-app pricing makes sense for a handful of sites. Past that, your own servers, run properly, usually cost less, even with someone looking after them. Before quoting a move, I compare what you pay now with what the new setup would cost, my fee included, so you see the saving in writing before you decide.
Questions
Will our sites go down?
Most sites don't. They're tested on the new servers first and switched over by DNS, with both hosts running during the change. A busy database may need a short read-only window, agreed in advance.
What happens to email?
If email lives on the same server, it moves too, or I move it to a dedicated email provider, which is usually the better home for it. Mailboxes are copied before the switch, so nothing is lost.
Do we lose what our managed host gave us?
No. Staging sites, daily backups, caching, SSL and a CDN are all part of the new setup, and the servers are patched and monitored from day one.
Who looks after the servers afterwards?
Your own team, with the runbooks I write as part of the move, or me, on an Oversight or Managed plan.
We have dozens of client sites. Do they all move at once?
No. They move in batches on a schedule you agree, and each batch is checked and signed off before the next one starts.
How is a move priced?
A fixed quote in writing after the inventory, so you know the cost before anything starts.
Where Are Your Sites Hosted Now?
Tell me the host and roughly what you pay. I'll tell you what a move would involve and whether it would save you money.