Moving your website to a new host without the stress
A step by step plan for moving your website to a new host, covering preparation, copying, testing, the switch itself and keeping email working.
Moving a website between hosts has a bad reputation, mostly earned by people who did it in the wrong order. Done properly, visitors should not notice a thing. The old site keeps running until the new one is ready, the switch takes moments, and you have a way back if something is off.
Treat it like moving house with an overlap on the leases. You do not hand back the old keys until the furniture is in and the lights work.
Before you touch anything
Most migration trouble is caused by something nobody knew was there. Spend an hour finding out what you have.
Gather your logins
You will need access to the current hosting account, the website's admin area, the domain registrar, and wherever the DNS is managed. If any of those are held by a former designer or a staff member who has left, sort that out first. It can take days.
List what the current host is doing for you
The website is the obvious one. Look for the less obvious:
- Email. Are your mailboxes with the same company as the website? This is the single most important question in the whole move.
- DNS. Is the old host also managing your domain's records?
- The security certificate. The new host will need to issue its own.
- Form delivery. How does the contact form send its emails?
- Extras. Automatic backups, a staff login area, redirects set up years ago.
Take a full backup and a snapshot of the DNS
Back up the files and the database, and save a copy somewhere that is neither the old host nor the new one. Then take a screenshot or export of every current DNS record. If email breaks later, that snapshot is how you put it right in five minutes.
Then choose a quiet time for the switch. Avoid Friday afternoons, when help is hard to find if you need it.
The move, step by step
- Set up the new hosting. Create the account and prepare the space, but leave your domain pointing at the old host for now.
- Freeze changes. From this point until the switch, do not edit the old site. Anything added after the copy is taken will be left behind. For an online shop, plan the copy and the switch close together so no orders fall in the gap.
- Copy everything across. Files, database, settings. Many hosts offer a migration tool or will do this for you.
- Test on a temporary address. The new host can give you a private preview address. Go through the site there as a customer would, using the checklist below.
- Lower the DNS timing. A day or two before the switch, reduce the time to live on your domain's records so the change spreads quickly once you make it.
- Switch. Update the DNS record that points your domain to the website so it now leads to the new host. Change only that. Leave the email records alone.
- Check the certificate. Once the domain reaches the new host, confirm the padlock appears on both the www and non www versions.
- Test again on the real address. Including a form submission.
- Keep the old hosting running. For a couple of weeks at least.
What to test before and after the switch
- Every main page loads and looks right on a phone and on a desktop.
- Images, downloads and videos appear.
- The contact form sends, and the message arrives in the right inbox.
- Booking, payment or shop functions work from start to finish.
- Old addresses still redirect where they should.
- Analytics is still recording visits.
Do not skip the form test. A form that sent mail through the old host's system will often fail silently on the new one, and nobody realises until enquiries have been vanishing for a month.
Keeping email working
Email is where website moves most often go wrong, and it is nearly always for one of two reasons.
The email was hosted with the old website host. If so, moving the website does not move the mailboxes. You either leave email where it is for now and move only the site, or you plan a separate email migration to a dedicated email service. We would do the second, but as its own project, not on the same day as the website.
The DNS was replaced wholesale. If the move involves pointing your domain at the new host's nameservers, every record has to be recreated there, including the ones for email. Miss the mail records and messages stop arriving. The safer approach is usually to leave the nameservers where they are and change only the single record for the website.
After the switch, send a test message from an outside account to your business address, and reply to it.
Do not cancel the old host too soon
Because of the way DNS answers are remembered around the internet, some visitors will keep reaching the old server for a while after the switch. If the old site is still there, they see a working website and nothing is lost.
The overlap also gives you a fallback. If a serious problem turns up, you can point the domain back while it is fixed.
When you do cancel, check three things first: you have a final backup, nothing else (email, DNS, the domain registration itself) is still living in that account, and auto renew is switched off so you are not billed for another year.