Inventory First
Before touching anything, we write down every site, subdomain, database, mailbox, cron job and DNS record on the old host. The forgotten ones cause the trouble.
People put off changing hosts for years, even when the current one is slow and support never answers. The worry is always the same. What if the site goes down for two days? What if a month of email disappears? It's a fair worry. We've been called in after DIY migrations where the website moved fine but nobody remembered the MX records.
A migration is mostly planning. We list everything that needs to move, test it on the new server, and only then switch. If something goes wrong, the old setup is still there to fall back on.
The order matters more than the speed.
Before touching anything, we write down every site, subdomain, database, mailbox, cron job and DNS record on the old host. The forgotten ones cause the trouble.
Files and databases copied to the new server, PHP version matched, and paths and settings corrected so the site behaves exactly as it did.
A day or two before the switch, we shorten the DNS cache time so the change spreads in minutes instead of hours.
Mailboxes created on the new server, old mail copied across, MX switched at a quiet hour, then a final sync to catch anything that arrived in between.
Forms, logins, payment pages, search and image uploads checked on the new server before a single visitor is sent there.
The old hosting stays active until everything is confirmed. If something is wrong, we point DNS back and you're where you started.
Nothing switches until it's tested.
The old server stays on as a safety net.
We've seen this many times. The website moves, looks fine, everyone celebrates. Then a week later someone notices the enquiry form emails stopped, because the old server was sending them and the new one has no mail settings. Or the accounts team's mailbox was never created. These are small things, but they cost leads, and they only get caught with a proper checklist.
Timing matters too. We don't switch an eCommerce site in the middle of a Diwali sale or a college site during admissions week. We pick a quiet evening or weekend, and someone from our team stays on it until the switch is confirmed.
Switch scheduled around your business calendar, never in the middle of a sale or campaign.
A final sync after the MX change picks up messages that landed on the old server during the changeover.
URLs, redirects and SSL carried over so Google sees the same site at the same address, and rankings don't wobble.
We deal with the old provider's support and the new one, so you aren't stuck relaying technical messages between them.
Written into the proposal before we start, so nothing is left to memory later.
Plan My MigrationNo surprises midway. You always know what stage the work is in.
We get access to the old host and list everything on it, including the email accounts, subdomains and scheduled tasks that nobody remembers until they break.
We agree a cut-over date and time, decide what moves first, and confirm the old hosting won't expire before the migration is fully done.
The new server is prepared with matching PHP, database and mail settings. DNS TTL is lowered a day or two ahead of the switch.
Everything is copied and tested on a temporary link. Forms, payments and logins are checked, and old email is synced into the new mailboxes.
DNS and MX are switched at the planned time, a final mail sync runs, and we watch the site closely for the next few days before signing off.
Straight answers to what clients ask us in the first meeting.
All FAQsUsually not at all, from a visitor's point of view. The new server is fully ready before DNS changes, so people reach either the old copy or the new one. The only rule is to avoid publishing new content or taking orders on the old site during the changeover window, which we keep short by lowering TTL in advance.
TTL is how long internet providers cache your DNS records before checking again. If it's set to a day, some visitors may keep reaching the old server for a day after the switch. Lowering it to a few minutes beforehand means the change takes effect much faster, and a rollback is just as quick.
Yes. We create the mailboxes on the new platform, copy old emails and folders, switch the MX records and then run a final sync. Staff phones and Outlook need their settings updated, and we help with that on the day, or share simple steps over WhatsApp.
It happens, especially when an old vendor managed everything. If you have the domain under your control, we can usually still rebuild from a backup or a copy of the site. If the domain itself is stuck, we work on that first. Bring whatever logins you have and we'll work out the route.
No. Many clients move to our hosting, but we also migrate sites to AWS, to a VPS your developers manage, or between two other providers. The planning and testing are the same either way.
Tell us what's on it. We'll plan a move that doesn't cost you emails or enquiries.
Prefer email? Write to hello@m9itcs.com