My WordPress Migration Checklist: What I Checked Before and After the Move

Before making any big changes, it is always good idea to plan accordingly.   

Before moving anything, create a complete copy of the website, including its WordPress files, database, media library, themes, plugins, and configuration files. Download at least one copy to a location outside the existing hosting account so the backup remains available if the original server becomes inaccessible. Also record the current WordPress and PHP versions, active theme, installed plugins, administrator accounts, permalink structure, and any custom code or redirects. I used Cpanel for complete server backups and just stored files within Dropbox for cloud backup and local use.

A website migration can affect more than WordPress. Record the existing nameservers and DNS records, including A, CNAME, MX, TXT, SPF, DKIM, and DMARC entries. This is especially important when email is hosted separately from the website because replacing nameservers without recreating the mail records can interrupt delivery. Save screenshots or export the DNS zone before changing anything. Documentation for me was key as I use GoDaddy to purchase and direct domains to Hostinger servers.

Set up the destination hosting account before directing the domain toward it. Confirm that the new server supports the required PHP version, database requirements, storage, SSL certificate, and WordPress features. Import or migrate the website, then use a temporary URL, preview domain, or local hosts-file entry to inspect it before the public DNS change. Check that pages, posts, menus, forms, images, plugins, and administrator access work correctly. I was able to restore 3 of 4 websites successfully from backup. Their migrating tool helped me with the last one pretty easily. 

Choose a lower-traffic period for the final cutover and avoid making content changes while the website exists in two locations. Reduce the DNS time-to-live in advance when that option is available, then update the required A record or nameservers. DNS changes may not appear everywhere immediately, so keep both hosting accounts active during the transition and verify which server is responding before troubleshooting an apparent problem.

Once the domain begins reaching the new host, test the website as a visitor and as an administrator. Review important pages, navigation, images, downloads, forms, search, login, mobile layouts, and any ecommerce or membership functions. Confirm that HTTPS works without browser warnings, internal URLs use the correct domain, redirects still function, and no pages return unexpected errors. Re-save WordPress permalinks and clear every caching layer if links or older content behave incorrectly.