Why migrations go wrong

Most hosting migrations cause disruption because people change DNS before the new host is ready, or forget to migrate email accounts, or do not test the site before switching DNS. The result is downtime, lost email, or a site that appears to work but has broken email behind it.

The correct migration sequence

  1. Set up your account at the new host first. Do not touch DNS yet.
  2. Transfer your website files and database. Copy everything — WordPress uploads, themes, plugins, and all database tables.
  3. Update database connection settings (wp-config.php for WordPress) to match the new host credentials.
  4. Test the site on the new host using a temporary URL before any DNS changes. Confirm everything loads correctly.
  5. Set up email accounts at the new host before changing MX records. Test that they work.
  6. Set up SSL at the new host so HTTPS works after the switch.
  7. Lower your DNS TTL 24-48 hours in advance if possible. This speeds up propagation later.
  8. Change MX records first when you are ready to switch. This prevents email loss.
  9. Change A records and nameservers. Propagation typically takes 1-4 hours with a low TTL.
  10. Monitor both hosts during propagation. Do not cancel old hosting until everything is confirmed working.

How to avoid breaking email

Email breaks when nameservers are changed before email accounts exist at the new host. The fix is simple: set up email at the new host and test it before touching MX records or nameservers.

WordPress-specific steps

For WordPress migrations, update the database connection in wp-config.php, and update siteurl and home values in the database if the URL changes. Tools like WP-CLI or Better Search Replace help with URL changes in the database.

Getting migration help from 0724 Hosting

0724 Hosting provides website and email migration support including WordPress, Laravel, and PHP migrations from cPanel, Plesk, and other DirectAdmin hosts. Contact us before you start if you want help planning the move.