How to Migrate a WordPress Site to a New Host
A WordPress migration is successful only when the new site behaves correctly after DNS changes—not when the files merely arrive.
Updated September 9, 2026
Inventory first
Record DNS, domains, SSL, mail routing, cron jobs, PHP version, plugins, mu-plugins, redirects, webhooks, analytics and external integrations. Hidden dependencies cause most migration surprises.
Create a recoverable copy
Take a fresh backup and verify that you can access it independently of the old hosting account. Keep the old site available until the new environment is proven.
Test before DNS cutover
Use a staging URL or local hosts-file override to test login, forms, checkout, search, scheduled jobs, media and redirects on the new environment.
Cut over and verify
Change DNS, monitor TLS and error logs, re-test business-critical flows and confirm search-engine directives/canonicals. Avoid changing application code at the same time unless necessary.
See whether Cloudways fits your workload
Compare the current Cloudways plans, included features and billing details directly before making a hosting decision.
View Cloudways plans