Before you move
- Take a complete backup and confirm you can restore it.
- Inventory DNS records, transactional email, cron jobs, webhooks, payment integrations and external storage.
- Lower DNS TTL ahead of the cutover if your DNS provider and timing allow it.
- Create the destination site and test it on a temporary URL or hosts-file override.
During the cutover
Freeze content changes if the site can tolerate it. For WooCommerce or membership sites, plan how to avoid losing orders, registrations or form submissions between the last data copy and DNS propagation. Move the database/files, verify application configuration, then switch DNS only after the destination behaves correctly.
After DNS changes
- Verify the home page, admin, login, forms and key conversion pages.
- Test HTTPS, redirects, canonical tags and robots directives.
- Check transactional email and external API/webhook callbacks.
- For ecommerce, place a real low-value test order if operationally appropriate.
- Keep the old host available long enough to roll back if a critical issue appears.
Migrating to Cloudways
Cloudways documents a WordPress Migrator workflow for single-site and multisite migrations and also promotes managed migration options. WordPress Multisite support differs by Cloudways product, so verify the destination model before starting the transfer.
If migration is part of a larger host decision, read the Cloudways WordPress guide and managed WordPress comparison first.