The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →This guide covers moving an existing WordPress site from another host to Cloudways—the destination described by Cloudways’ migration documentation. If you meant leaving Cloudways for a different provider, this is a different process. The safest move is: prepare a Cloudways application, back up the source, transfer with the free Cloudways WordPress Migrator or a managed migration, test on the temporary URL, then change DNS and enable SSL.
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
What a Cloudways migration actually moves
A WordPress migration is more than copying a theme and a database. A complete move can include the WordPress core files, wp-content, uploads, the database, domain and subdomain configuration, redirects, scheduled tasks, transactional email settings, analytics, payment callbacks and plugin licences. Missing one of these can leave a site that appears functional while forms, orders or background jobs fail.
As an Amazon Associate I earn from qualifying purchases.
Cloudways separates the data transfer from domain cutover. The Migrator or a managed migration copies the site, but your domain’s DNS records still point wherever they pointed before. Visitors continue reaching the old host until you change those records. Plan the move around that distinction.
Plan the move before touching the live site
Build an inventory
Record the current production setup in a document that you can use for post-migration checks:
#1 Best Overall
- Every primary domain, parked domain and subdomain.
- Whether the site uses a subdomain or subdirectory WordPress Multisite network.
- DNS records for the website, mail, verification services and third-party integrations.
- Redirect rules, custom rewrite rules and any special web-server configuration.
- WordPress cron events and server-level cron jobs.
- Forms, SMTP or transactional-mail services, analytics, search, webhooks and payment callbacks.
- WooCommerce products, orders, customer accounts, subscriptions and external fulfilment connections.
- Plugin and theme licences, activation keys and any settings stored outside the database.
This inventory tells you what must be tested after the files and database arrive at Cloudways. It also identifies services, such as email, that may not be hosted with the WordPress site and therefore need separate DNS or account work.
Take a complete, restorable backup
Make a full copy of the source files and database before starting. Keep it outside the source server, and verify that the archive can be opened and the database dump can be read. Do not treat a plugin export or an image folder as a complete backup. Retain the original host while you migrate and test; it is your rollback copy if the cutover exposes a problem.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Choose a change window
A brochure site can often remain editable during the transfer, but a store, membership site or busy publishing site receives new data while the migration runs. Decide in advance whether to pause editing and orders or perform a final synchronization immediately before DNS cutover. If you do neither, orders or comments written to the old database after the copy may be absent from the Cloudways database.
Choose the right migration route
| Route | Best fit | Advantages | Risks and responsibilities |
|---|---|---|---|
| Cloudways WordPress Migrator | Most single-site and WooCommerce moves | Guided, automated transfer; Cloudways documents it as free | Requires source WordPress administrator access and accurate destination SFTP and database details |
| Cloudways managed migration | Owners who want Cloudways staff to perform the move, or sites with unusual arrangements | Cloudways handles the migration after receiving the required access and backup information | You must provide complete access, describe the site, agree on timing and perform acceptance testing |
| Manual SFTP and database transfer | Experienced administrators who need direct control | Direct control over files, database import, search-and-replace and cutover sequencing | More opportunities for URL, permissions, PHP, cron, email and serialized-data errors |
For a conventional single WordPress installation, start with the Migrator. Select managed migration when you cannot safely troubleshoot credentials, unusual paths or a complex network. Use a manual transfer only when you understand the source server, database tooling and WordPress configuration well enough to recover from an incomplete import.
Prepare the Cloudways destination
Launch a WordPress application
- In the Cloudways console, launch a new WordPress application on the server and plan that application as the destination for the existing site.
- Open the application’s Access Details and copy the temporary destination URL, server IP or SFTP host, database name, SFTP username and SFTP password into your migration notes.
- Confirm that you can reach the temporary URL and that the destination credentials are complete before starting a transfer.
Use the destination URL during testing. Do not point the public domain at the new server yet; early DNS changes make it harder to distinguish a migration error from DNS caching.
Check compatibility and capacity
Confirm that the destination application has enough disk space for the source files, uploads and database, and that the PHP and database environment supports your current WordPress version and plugins. If a plugin requires a server extension or a specific PHP release, resolve that requirement before importing the site rather than discovering it after cutover.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Migrate with the Cloudways WordPress Migrator
Install the plugin on the source
- Sign in to the source WordPress dashboard with an account that can install and activate plugins.
- Install and activate the Cloudways WordPress Migrator plugin.
- Open the Migrator settings and select the option to begin a new migration.
The plugin runs from the source site, so the source server must be able to make the outbound connections required for the transfer. If a security layer, maintenance mode or hosting firewall blocks the process, allow the connection or use managed migration instead.
Enter the destination details
Use the values copied from Cloudways Access Details. Supply the destination URL, SFTP host or server IP, SFTP username, SFTP password and the destination database name. Enter the values exactly; a wrong host, username, password or database name is the most common reason a guided transfer cannot start.
When the Migrator asks for paths, select the root directory that contains the WordPress installation. If the site uses custom directories, identify them explicitly rather than assuming the default WordPress layout. Select additional database tables when a plugin stores data outside the standard WordPress tables. If the source is protected by a password at the web-server level, disclose that protection in the migration settings so the destination can be reached during the copy.
Start the copy and monitor it
Start the migration only after the backup is complete. Leave the source online while the plugin transfers files and database data. A successful transfer message means the copy completed; it does not mean every integration, cron event or DNS record is ready for production. Note any warnings in the Migrator output and resolve them before testing.
Recommended Free Tools
Request a managed Cloudways migration
Cloudways also documents a managed-migration route. Submit the migration request through Cloudways and provide the source and destination information the team needs: hosting access or a complete backup, the domains involved, any password protection, the preferred change window and details of special plugins, Multisite, WooCommerce or custom paths.
Agree on what the service includes and when the copy will be ready for review. You still own acceptance testing. Check the migrated application on its temporary URL, report defects while the source remains available and schedule the final synchronization or maintenance window for sites whose data changes continuously.
Manual migration for administrators
Manual transfer is a fallback, not a shorter version of the plugin workflow. The broad sequence is:
- Put the source into a controlled state and create a fresh database dump and file archive.
- Upload the WordPress files to the Cloudways application over SFTP.
- Create or use the destination database and import the dump.
- Update
wp-config.phpwith the destination database credentials and any environment-specific settings. - Perform a careful URL replacement from the old site address to the temporary Cloudways URL. Use a tool that understands serialized WordPress data; a blind text replacement can corrupt serialized options.
- Review file ownership and permissions, confirm the document root and verify that uploads and generated files are readable.
- Recreate cron jobs, mail settings, redirects and server-level rules that were not contained in the WordPress files or database.
Manual work gives you control over the order of operations, but it also makes PHP incompatibilities, broken serialized values, missing extensions and permission errors your responsibility. If you cannot validate each item, use the Migrator or managed migration.
Keep the source stable and perform a final sync
After the initial copy, continue treating the old site as the live source until DNS changes. Ask editors to stop publishing and, for stores, place the site in maintenance mode or otherwise pause order creation for the final synchronization window. Export or copy the newly changed database data and uploads immediately before cutover, then apply that final data to Cloudways.
Cloudways warns that changes made while DNS still points to the old host do not automatically appear on the migrated site. This is why a store should have an explicit order-freeze or final-sync procedure rather than relying on the first migration copy.
Test the Cloudways copy before changing DNS
Use the temporary Cloudways URL or another private pre-cutover method. Test both anonymous and authenticated behavior, and test representative content rather than only the home page.
- URLs and content: Open posts, pages, category archives, search results, media attachments and representative images. Check that internal links do not lead back to the old host.
- Permalinks: Visit a range of pretty URLs and confirm that there are no unexpected 404 responses or redirect loops.
- Accounts: Log in, register a test account if registration is enabled and test password reset.
- Forms: Submit contact, quotation, newsletter and other important forms. Verify delivery at the intended mailbox or service.
- WooCommerce: Add an item to the cart, update quantities, complete checkout in the appropriate test mode, inspect confirmation pages and verify that payment callbacks and transactional messages work.
- Search and filtering: Run site search and any product, directory or faceted filters used by visitors.
- Background work: Confirm scheduled publishing, backups, imports, reports and other cron-driven jobs.
- Integrations: Check analytics, webhooks, marketing connections, licence activation and external API callbacks.
- Performance and logs: Look for PHP errors, failed requests, missing assets and blocked security rules in the destination logs.
Fix failures on Cloudways while the source is still serving visitors. Cloudways recommends reviewing the migrated site before DNS is updated so problems can be found before users reach the new copy.
Change DNS only after acceptance testing
- At your DNS provider, identify the records that serve the website, normally the apex domain and its
wwwhostname. Leave unrelated mail records unchanged unless your mail service is also moving. - Point the website records to the Cloudways server IP shown in the application’s access information.
- Save the DNS changes and monitor both the old and new hosts while resolvers update. DNS changes are not performed automatically by the data transfer.
- Use multiple networks or DNS lookups to confirm that the public domain resolves to Cloudways, then load the site through the real domain.
Propagation is resolver-dependent, so some visitors can continue reaching the old host for a period after the authoritative records change. Keep the old site intact and avoid making content changes on it once the cutover begins.
Install SSL, force HTTPS and clear caches
After the domain resolves to Cloudways, install or upload the SSL certificate required for that domain in the Cloudways application. Test the certificate at the real domain, including every hostname you intend to serve, before forcing HTTPS. Enabling an HTTPS redirect before the certificate is valid can create certificate warnings or redirect failures.
Once HTTPS works, enable the site’s HTTPS redirect if needed, purge Cloudways and WordPress caching layers, and clear any CDN or reverse-proxy cache. Recheck canonical URLs, mixed-content warnings, login, forms and checkout over HTTPS. A cache purge is especially important after URL replacement because stale pages can continue to reference the old host.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Special cases that need extra planning
WordPress Multisite
Cloudways’ Migrator documentation states that WordPress Multisite is currently supported only on Cloudways Flexible. Confirm that the destination uses that offering before attempting the transfer.
Subdomain networks require DNS planning for every mapped hostname and usually a wildcard DNS and wildcard SSL arrangement. Subdirectory networks have different URL and domain requirements. Map the network structure, mapped domains and administrator access before migration, and test the network dashboard plus several subsites before changing DNS.
WooCommerce and other high-change sites
WooCommerce orders, customer accounts, stock and subscriptions can change during a file transfer. Treat the initial copy as a staging snapshot, schedule a maintenance window or freeze order activity, then perform a final database and upload synchronization immediately before DNS. After cutover, reconcile the last order number, inventory and payment notifications against the source records.
Email and DNS services
Moving WordPress does not automatically move mailboxes. Keep mail-related DNS records pointed at the mail provider unless that service is part of your migration. Test both website-generated messages and replies to the sending address after the website records change.
Troubleshoot common failures
The Migrator cannot connect
- Re-copy the SFTP host, username, password and database name from Cloudways Access Details; do not substitute the public domain for the SFTP host.
- Confirm that the source host permits outbound connections and that a password-protection layer is disclosed in the Migrator settings.
- Check that the destination has sufficient storage and that the selected root directory is the one containing WordPress.
- If access remains unreliable, stop retrying against the live site and submit a managed-migration request with the backup and access details.
The home page works but inner URLs fail
Check the site URL and home URL values, review URL replacement, verify the document root and refresh WordPress rewrite rules by saving the permalink settings. Inspect redirects for references to the old hostname and look for web-server rules that were not copied.
Free tools Windows power users keep installed
One-click scans. No signup required.
Images, styles or scripts are missing
Confirm that the uploads and theme/plugin directories were transferred, that file permissions allow them to be read and that generated asset URLs use the current scheme and hostname. Purge caches only after correcting the underlying path or URL problem.
Orders or comments are missing
Identify the last record present on each host and determine whether it was created after the initial copy. Perform the planned final synchronization rather than manually editing production rows. For a store, reconcile orders, stock and payment status before declaring the move complete.
HTTPS redirects or login loops occur
Verify that the certificate is valid for the requested hostname, that the site URL uses the intended scheme, and that only one layer is enforcing HTTPS. Clear application, server and CDN caches, then retest in a private browser session.
Keep a rollback path and close the migration
Do not cancel or delete the old hosting account immediately. Cloudways advises keeping it until the domain points to Cloudways, DNS changes have propagated and the latest website data is confirmed on the new application. During that period, monitor uptime, forms, order notifications, scheduled jobs and error logs on the public domain.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesOnce the new site has served successfully through a complete business cycle and you have a verified backup of the Cloudways application, remove obsolete credentials, revoke temporary access and document the final DNS, cron, SSL and integration settings. Only then should you retire the old hosting environment.
Final decision
Use the Cloudways WordPress Migrator for a normal single-site move, managed migration when access or architecture is complicated, and a manual transfer only when you need—and can safely manage—low-level control. The no-downtime outcome depends less on the copying mechanism than on disciplined sequencing: complete backup, stable source, final synchronization, pre-DNS testing, deliberate DNS change, working SSL and a retained rollback host.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
