WordPress Hosting Migration Guide

A host switch is safer when you treat it as a controlled cutover rather than copying files and hoping DNS catches up.

Updated September 9, 2026

Before the move

1. Take a fresh independent backup and verify how it would be restored.
2. Inventory the domain, DNS records, email, SSL, redirects, cron jobs, analytics, forms, payment integrations, and external APIs.
3. Record the current PHP version and any unusual server requirements.
4. Choose a low-risk migration window if the site changes frequently.

Build and test the destination

Copy the site to the new host, then test it before public DNS changes. Check pages, media, login, forms, search, checkout, scheduled jobs, redirects, email delivery, and tracking. For a store or membership site, plan how to prevent orders or user changes from being split across two copies.

Cut over DNS

When the destination is verified, update the relevant DNS records or nameservers. Keep the old hosting active during propagation. Confirm HTTPS, canonical URLs, redirects, robots directives, sitemap access, and that the public site is actually resolving to the new environment.

After the move

• Monitor uptime and server errors.
• Test forms and transactional email again.
• Check analytics and conversion tracking.
• Inspect important URLs in Search Console once the production site is stable.
• Keep the old account until you are confident nothing is missing.

Want the host to help?

See WordPress hosting with migration assistance. WPX currently offers a standard migration service subject to its migration policy.