Before you start
- Access to both hosting accounts and DNS management.
- A complete backup and planned switchover window.
Inventory the website and its services
Migration must transfer files and database while preserving email, scheduled tasks and connected services. Record the domain, PHP and WordPress versions, plugins, certificates and current DNS. Identify whether the server, address or both will change.
- Identify the DNS provider and the service receiving email.
- Preserve settings and necessary licences.
- For stores, plan a switchover window and a consistent recovery point.
Prepare a backup and destination
Keep a complete files-and-database backup. Confirm the destination can run the website and has sufficient storage. Prepare databases, certificates and access without deleting the source website.
- Check PHP versions and options required by plugins.
- Verify the backup is readable and restorable.
- Keep the source available for checks and the planned rollback.
Copy and adapt the data
Choose a suitable method: compatible migration software, an available Installatron import or assisted transfer. Check destination database credentials. Address changes may require URL replacement that understands serialized data.
- Do not improvise global text replacement in SQL files.
- Never expose wp-config.php or database credentials.
- For stores, avoid two active copies accepting orders in parallel.
Test before changing DNS
Use an appropriate preview method to check the destination. Temporary URLs may not reproduce the final domain's behaviour exactly. Check login, media, links, forms and HTTPS, then store functions in a controlled environment.
- Check email and services that authorize the domain or server.
- Confirm scheduled tasks and payment notifications.
- Resolve errors before directing visitors to the new hosting.
Coordinate switchover and recent changes
Yesterday's copy lacks this morning's orders and posts. Arrange final synchronization and suitable temporary restrictions where needed. Change only relevant DNS records; moving the website does not necessarily mean moving email.
- Preserve MX and sending records when email remains with the existing provider.
- Record switchover time and watch both destinations during propagation.
- Avoid concurrent edits during the final transfer.
Verify and keep a controlled rollback
After switching, check pages, HTTPS, orders and notifications on the destination. Review redirects if the address changed. Retain old hosting until functionality and data consistency are confirmed.
- Monitor initial orders and integration status.
- Do not return to an old database without preserving data created since switching.
- Remove obsolete copies and access once the transfer is confirmed.
Official documentation
Labels and options vary with versions, plugins and your account. Refer to publisher documentation for your configuration.