Migration
WordPress migration steps for a controlled host move
A WordPress migration is safest when the new site is working before public DNS changes. That turns cutover into a traffic switch instead of a moment when you discover whether the copied site can start.
Inventory the source
Record WordPress and PHP versions, database size, uploads, active theme and plugins, scheduled jobs, mail setup, DNS records, redirects, caching, CDN configuration, SSL, and any server-specific rules.
Build and test the destination privately
Copy files and the database, adjust environment-specific configuration, and test through a temporary hostname or local hosts-file mapping. Verify administrator login, forms, media, links, and integrations.
Plan the final data sync
For a changing site, decide how orders, form entries, comments, accounts, or other writes will be handled between the first copy and cutover. A content freeze or final database sync may be necessary.
Cut DNS only after the new copy is ready
Lower TTL ahead of the move when appropriate, switch the required records, monitor both old and new environments during cache expiry, and keep the source available until traffic and data have been verified.