Skip to content

Home  /  Blog  /  Hosting and migration

How to Move a WordPress Website to a New Host: A Safe Migration Checklist

A safe WordPress migration verifies backups, copies the website and database to the new host, tests everything there, then changes DNS at a planned time and monitors the switch. Planning email, DNS and rollback matters as much as moving the files.

5 min readHosting and migrationWritten by WP Mate, Warrnambool VIC
WP Mate koala mascot beside a laptop, representing Australian WordPress support
01

Why migrations go wrong

Moving the files is the easy part. Problems usually come from forgotten dependencies, DNS timing, broken email or untested functions. A website is connected to a domain, email, third-party services and sometimes licensed plugins, all of which need to keep working.

02

Before you start: audit dependencies

  • Where the domain and its DNS are managed
  • Whether business email is hosted with the old provider
  • Plugin and theme licences tied to a domain or server
  • Third-party services such as payment, mapping and email
  • Any redirects, SSL certificates or special server rules
  • Current PHP version and requirements

Not sure what is going on with your website?

Tell us what you are seeing and we will outline the next step before any chargeable work.

03

The migration checklist

StageTasks
PrepareFull backup, verified; lower DNS time-to-live in advance; choose a quiet time
CopyTransfer files and database; update configuration for the new environment
TestPreview the website on the new host; test forms, login, checkout and email
SwitchUpdate DNS; keep the old host running during the changeover
VerifyCheck the live site, SSL, redirects and monitoring
Clean upRetire the old host only after everything is confirmed
04

DNS and downtime

DNS changes spread over time, so for a short while some visitors see the old site and some the new. Planning for that, and avoiding content or order changes during the switch, keeps it smooth. Zero downtime cannot be guaranteed in every environment, but careful planning keeps disruption small.

05

Email during a move

If your domain email is tied to the old host, moving the website without handling email can interrupt it. Identify where email lives before you touch DNS.

06

Planning the timing

Choose a quiet period for the switch, avoid sales or campaigns and tell anyone who edits the website to pause changes during the move. For stores, plan how to handle orders placed during the changeover. A calm, well-timed move is far less stressful than one rushed on a Friday afternoon.

07

What to test on the new host before switching

  • Home page, key service pages and the blog
  • Contact forms and email delivery
  • Login, user accounts and permissions
  • Checkout and payments for stores
  • Redirects, SSL certificate and sitemap
  • Scheduled tasks and any connected services
08

After the move

Monitor closely for a few days: errors, uptime, search console warnings and form delivery. Keep the old host available until you are sure everything works, then retire it. Update any documentation and re-check backups on the new host, because backup routines do not move automatically. WP Mate can plan and run the whole process, see WordPress hosting and migration or talk to us.

09

Common migration mistakes

  • Cancelling the old hosting before confirming everything works on the new one
  • Forgetting that email is hosted with the old provider
  • Not lowering DNS time-to-live in advance, which slows the switch
  • Changing content during the move, so some updates are lost
  • Skipping tests of forms, login and checkout on the new host
  • Leaving old backups and access with the previous provider
10

What a smooth migration feels like

For the owner, a good migration is almost boring: a plan, a short window of care, then a message saying it is done and tested. Behind that sits careful preparation: dependency checks, verified backups, a rehearsal on the new host and a rollback option. If a provider cannot describe their migration process clearly, ask more questions. Ours is described on the hosting and migration page.

11

Communicating a move to your team and customers

Tell anyone who edits the website when the move will happen so they avoid changes during the switch. If you run a store, consider a short notice or holding period for orders. Make sure whoever manages email knows if mailboxes are affected. After the switch, confirm that forms, emails and checkout work and watch your monitoring closely for a few days. Clear communication prevents duplicate work, lost content and confusion, and it turns a technical project into a smooth change that customers barely notice.

12

Let us handle it

WP Mate plans, performs and tests migrations. Moving a website to our WordPress-optimised hosting is quoted separately once it has been assessed. See WordPress hosting and migration, or talk to us about a move.

Want this looked after for you?

WP Mate maintenance plans cover managed updates, daily offsite backups, security scanning and 24/7 uptime monitoring.

Thinking about moving? Let's plan it properly.

How we can help

Services related to this guide

Hosting and migration

Plan a safe move or review your hosting.Discuss My Hosting →

WordPress support

Friendly Australian support for your WordPress website.Get WordPress Help →

Talk to WP Mate

Not sure which service fits? Ask us and we will point you the right way.Contact us →

Frequently asked questions

The copy can be quick, but planning, testing and DNS timing take longer. A realistic estimate follows an assessment.

A clean migration with the same URLs normally has little effect. Problems come from broken redirects or downtime.

It is possible, but plugins for migration have limits, and it is easy to miss email, DNS and licence issues.

Ready to get your website sorted?

Based in Warrnambool, Victoria, helping Australian businesses online. Tell us what is happening.

Get WordPress help

Tell your mate what's going wrong.

Send us a few details and we’ll work out the next step. Please don’t include passwords or payment details.

  • Australian support in plain English
  • Clear scope and next steps before chargeable work
  • Backup and recovery plan before live changes

Please don't include passwords, payment card numbers or private customer data. If we need access, we'll arrange a secure way to share it.