Plan and verify a WordPress migration

Gather the migration details

Identify the current domain, file location, database, PHP requirements and any licenses. Check where email is hosted separately: moving the website must not accidentally change working mail services.

Back up the original website files and database. The XML from Tools > Export alone does not move the complete installation, all settings or plugin files. For a store or frequently changing site, agree on a point after which no new data is written to the original.

Transfer and test

1. Add the destination domain to cPanel and confirm a compatible PHP version and enough disk space.
2. Transfer files into the correct document root using the agreed migration tool or File Manager.
3. Create a separate database and user. Import the original database and update the database connection in wp-config.php for the destination.
4. If the address changes, use a migration method that understands WordPress data structures. A plain text replacement in an SQL file can corrupt serialized data.
5. Test the destination using the agreed preview method: pages, images, administration, forms and payments. Disable real customer emails and payments in the test destination.
6. Change only the planned DNS records after testing and any required final data synchronization. Preserve email records if mail is not moving.

Verify after launch

Check HTTPS, addresses and the latest data. Clear caches. Use Scan in WP Toolkit if the installation is missing from its list.

Keep the original service and backup available until DNS caches have expired and the destination is confirmed working. For migration assistance, give support the domain and scope; arrange a secure method for supplying credentials separately.