• Confirm control of both domains and the DNS zones, and record their current records.
• Arrange the new domain in the hosting account and ensure its HTTPS certificate can be issued.
• Create a current files-and-database backup and agree how changes made during the move will be handled.
• List payment callbacks, sign-in providers, forms, analytics, licences and other integrations that recognise the website URL.
• Export important old URLs so you can map them to equivalent new pages.

1. Test a copy using the proposed domain and hosting route before changing public traffic where possible.
2. Update the WordPress Address and Site Address using the method appropriate to the installation. Check for WP_HOME or WP_SITEURL constants that override database settings.
3. Update stored internal URLs using a serialisation-aware migration tool and review its scope before writing.
4. Enable the planned DNS change and valid HTTPS configuration, then test the public site and administration area.
5. Redirect old URLs to their corresponding new URLs and update sitemaps, canonical settings and integration callbacks.

No. Website routing and email routing are separate. Preserve the intended MX and email authentication records unless email migration is part of the plan. Changing nameservers without copying the full zone can disrupt mail even when the website appears healthy.

Check configuration constants, stored links, page-builder data and caches. A CDN redirect, hosting redirect or SEO setting may also force the old domain. Identify the source before adding another redirect, because competing rules can create loops.

Test login, password reset, forms, downloads, checkout and scheduled jobs as applicable. Keep the old domain registered and its redirects maintained for the planned transition. If you roll back after new orders or registrations have arrived, preserve those records rather than blindly restoring the old database. Record the final DNS values and the location of the tested backup.

• Performing a serialisation-safe WordPress search and replace
• Preserving redirects when replacing a WordPress website
• Checking WordPress canonical URLs after migration
• Planning WordPress backups and staging before a change
• Moving WordPress from a subdirectory to the domain root

• WordPress: Migrating
• WordPress: WP Config
• Google Search Central