Moving hosts can feel risky when your website needs to stay available. The good news is that you can move your website to a new host without downtime by preparing the new copy first, testing it while your current host stays live, and changing DNS only when you’re ready. A little planning helps avoid broken pages, missing orders and rushed fixes.
# Plan how to move your website to a new host without downtime
Start by listing what your website needs to run. A simple brochure site may only need its files and database. A shop, membership site or blog with frequent updates also needs a plan for changes made during the move.
Before you begin, check:
- Which domain and DNS provider you use, and who can access the account.
- Whether your site uses a database, email accounts, scheduled tasks or external services.
- How you’ll make a fresh backup of files and the database.
- When you can test the new copy and when you can make the final switch.
Keep the old hosting account active during the move. You’ll need it to serve visitors while you prepare the new site, and it gives you somewhere to return if testing uncovers a problem.
# Back up the site and prepare the new host
Take a fresh backup before changing anything. If you can, save the website files and database separately, and keep a copy somewhere outside both hosting accounts. Make sure you know how to restore it; a backup you can’t use won’t help in a hurry.
Next, set up the website on the new host. Create the required database and user if your site needs them, upload the files, and update the site’s configuration with the new database details. Check that PHP or other software requirements are supported by the destination plan before you commit to the move.
For a content-managed site, check that its media files, plugins or extensions, theme and configuration have all come across. Avoid making unrelated design or software updates at the same time. Keeping the migration focused makes it easier to spot the source of a fault.
# Test the new copy before changing DNS
You can often preview the new copy using a temporary address or a hosts-file override. Your host can explain which method it supports. The key is to test the new server without sending normal visitors away from the live site.
Work through the pages and actions people rely on:
- Open the homepage, key landing pages and several older URLs.
- Check images, downloads, forms, navigation and internal links.
- Sign in to the admin area and confirm you can edit content.
- For a shop, test the product pages and checkout flow without placing a real order.
- Check that HTTPS works and that the SSL certificate is in place.
Look for redirects, error messages, missing images and incorrect links. If anything fails, fix it on the new host and test again. Don’t point your domain at a copy you haven’t checked.
# Handle updates and email during the move
A static site is straightforward to copy because its content doesn’t change much. A busy website is different: a customer may place an order or an editor may publish a post while you’re testing the new copy. If you switch to an older database, those changes may be missing from the new site.
Plan a short content freeze for the final move if practical. Otherwise, arrange to copy the latest database changes and uploads across just before the DNS change. For online shops, pause order processing only if your business can manage it; don’t assume that a file copy includes orders created afterwards.
Email needs its own check. If your domain’s email is hosted separately, preserve its existing mail records when updating DNS. If you’re moving email too, set up the mailboxes and records at the new provider and plan that move separately. A web hosting migration should not accidentally interrupt business email.
# Switch DNS and monitor the site
When the new copy passes your checks, update the domain’s DNS records to point visitors to the new host. DNS changes can take time to reach everyone, so some people may still see the old site while others reach the new one. That overlap is why it helps to keep both hosting accounts available and the content in sync.
After the change, check the domain from different devices or networks, open key pages and test important forms. Keep an eye on orders, enquiries and error logs if your hosting panel provides them. Confirm that HTTPS still works and that email records remain correct.
Don’t cancel the old hosting account as soon as your own browser shows the new site. Wait until you’re confident visitors are reaching the new host and any final data has been carried across. If you find a serious problem, you can change DNS back while you investigate, though visitors may continue reaching either host during DNS propagation.
# Choose a host that can help with the move
Migration is easier when the destination has the resources your site needs and a clear process for getting help. AUHost offers free migration, with an extra free month on Grow and Superstar. Grow costs A$4 per month or A$40 per year and includes hosting for three websites, 10 GB NVMe storage, 4 GB RAM, daily backups, CDN and staging. Superstar costs A$10 per month or A$100 per year, with hosting for seven websites, 45 GB NVMe storage, 8 GB RAM, Node.js and WooCommerce.
When you’re ready to move, see the AUHost plans and contact the team about the migration. Keep your existing host active until the new site is tested and the switch is complete.
