What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
To move a WordPress site to Cloudways, launch the destination WordPress application, back up the existing site, transfer it with the free Cloudways WordPress Migrator or a managed migration, test the copy on its temporary URL, and only then point DNS to the Cloudways server. DNS is a separate cutover step: moving files and the database does not change where your domain resolves.
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
This guide covers migration to Cloudways. If you meant moving a site away from Cloudways, the destination-host and DNS steps are different.
As an Amazon Associate I earn from qualifying purchases.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteChoose the migration route before you touch the live site
Cloudways documents three practical approaches. The first choice is usually the WordPress Migrator plugin; managed migration is useful when you want Cloudways staff to handle the transfer; a manual SFTP/database move is a fallback for administrators who need direct control over every file, table and search-and-replace operation.
| Route | Best fit | Strengths | Watch-outs |
|---|---|---|---|
| Cloudways WordPress Migrator | Most single-site and WooCommerce moves | Guided, automated transfer; Cloudways describes it as free | Requires WordPress administrator access on the source and accurate destination SFTP and database details |
| Cloudways managed migration | Owners who prefer expert handling or have an unusual setup | Cloudways staff perform the migration after receiving the necessary access or backup information | Provide complete access, technical details and testing instructions; agree on timing and scope before work starts |
| Manual SFTP and database transfer | Experienced administrators who need direct control | Control over files, database import, URL replacement and the cutover sequence | More opportunities for URL, permissions, PHP, cron, email and serialized-data errors |
The Migrator and end-to-end migration guides were published by Cloudways on June 29, 2026; its onboarding guide was published July 24, 2026. Interface labels can change, so use the labels shown in your current Cloudways console.
#1 Best Overall
What to collect and record first
A migration fails most often because an overlooked dependency remains on the old host. Make an inventory before creating the transfer.
Domains and DNS
- Primary domain, www variant, subdomains and any parked or redirected domains.
- Current DNS provider, A records, CNAMEs, mail records and any third-party records that must remain untouched.
- Redirect rules, canonical-domain settings and hard-coded URLs in configuration files or plugins.
Application services
- WordPress administrator accounts and the email address used for recovery.
- Scheduled tasks, server cron jobs, background queues and external webhooks.
- Transactional email provider, SMTP credentials, analytics, advertising tags, search-console verification and payment callbacks.
- Plugin and theme licenses, private repositories, API keys and integrations that bind to the old domain or server IP.
Commerce and frequently changing content
For WooCommerce, record the order, customer, product and subscription data that must be present at cutover. A blog can often tolerate a short content freeze; a busy store cannot safely accept orders on two unsynchronized databases. Plan either a maintenance window or a final synchronization immediately before changing DNS.
Make a complete, restorable backup
Keep a full copy of the WordPress files and database before the first transfer attempt. Store it somewhere independent of both hosts and verify that the archive can be opened and the database can be read. Include uploads, the active theme, plugins, wp-config.php, custom files and any non-standard directories. Keep the source account active until the new site is serving the latest data and DNS propagation is complete.
Prepare the Cloudways destination
- In Cloudways, launch a WordPress application on the server and account you intend to use.
- Open the application’s Access Details and copy the temporary destination URL, server IP or SFTP host, database name, SFTP username and SFTP password. Paste these values into a secure password manager rather than an unencrypted note.
- Confirm that the destination has enough storage for the current files and database, and that the selected PHP and application settings are compatible with your theme and plugins. If a plugin requires a particular PHP version or extension, resolve that before importing.
- Do not point the public domain yet. The temporary Cloudways URL gives you a place to inspect the migrated copy while visitors still reach the old host.
The destination URL and credentials are transfer inputs, not permanent public settings. Treat the SFTP password as sensitive and rotate it if it has been shared outside the migration team.
Method 1: migrate with the Cloudways WordPress Migrator
The Migrator is the normal path for a single WordPress site and is also suitable for many WooCommerce moves when you plan the final data sync correctly.
Install the plugin on the source
- Sign in to the existing WordPress dashboard with an administrator account.
- Install and activate the Cloudways WordPress Migrator plugin.
- Open the plugin’s migration form and keep the Cloudways application’s Access Details visible in a separate secure window.
Enter the destination details
Enter the Cloudways destination URL, SFTP host or server IP, SFTP username, SFTP password and destination database name exactly as shown in Access Details. A single character error in the host, database name or password can cause a connection failure.
Select the source’s root directory when the site is installed in a non-standard path. If the installation uses custom database tables, select the additional tables required by the site. Disclose password protection on the source if the staging or production site is protected; the transfer service must be able to reach the files and database.
Start and monitor the transfer
- Start the migration from the plugin and leave the source available while it runs.
- Do not update WordPress, install plugins, publish posts or process orders during the copy unless you have explicitly planned a final synchronization.
- Wait for the plugin to report completion. If it reports an error, record the exact message, correct the relevant credential, path or access restriction, and restart only after confirming the destination has not been partially configured in a way that would duplicate data.
The transfer copies the site; it does not change DNS. Visitors continue to use the old host until you perform the cutover.
Method 2: request a Cloudways managed migration
Managed migration is appropriate when you do not want to operate the transfer yourself, when the site has an unusual directory or database layout, or when a business needs an agreed migration window. Submit the request through Cloudways’ migration process and provide the source access or a complete backup, the destination application details, the domain names, special directories, custom tables, password protection and a list of tests that must pass.
Before work begins, confirm what the service includes: the applications and databases being copied, whether email or DNS is outside scope, the expected start window, how a final synchronization will be handled, and who approves the cutover. Cloudways documentation describes managed migration but does not establish a universal price, completion time or success-rate figure, so obtain those terms for your specific request.
Free tools Windows power users keep installed
One-click scans. No signup required.
Method 3: manual files-and-database migration
Use a manual move only if you are comfortable with SFTP, database exports and WordPress URL handling. The broad sequence is:
- Put the source in a controlled state and create a verified file and database backup.
- Export the complete WordPress database from the source and transfer the files, including uploads and configuration files, to the Cloudways application over SFTP.
- Import the database into the Cloudways database. Use the destination database name and credentials from Access Details rather than copying the old host’s values blindly.
- Update
wp-config.phpwith the destination database host, name, user and password. Preserve salts and other site-specific settings unless you have a documented reason to change them. - Replace the old site URL with the temporary Cloudways URL only where required for testing, using a WordPress-aware search-and-replace method that understands serialized data. A raw text replacement can corrupt serialized options.
- Check file ownership and permissions, PHP compatibility, rewrite rules, scheduled tasks and any server-level configuration that was not inside the WordPress directory.
- Log in to the destination, save permalinks once, and run the same functional checks listed below before changing DNS.
Manual migration gives you control, but it also leaves you responsible for details the plugin normally handles. If you cannot explain how you will restore the original database and reverse a URL replacement, use the Migrator or request managed assistance instead.
Keep the source stable and plan the final synchronization
A completed copy can become stale while you are testing it. Freeze publishing and administrative changes during the final window. For WooCommerce or any site with frequent registrations, comments, bookings or orders, schedule the final synchronization immediately before DNS cutover, or place the site in maintenance mode long enough to prevent writes during the last copy.
Cloudways warns that changes made while DNS still points to the old host do not automatically appear on the migrated site. That means an order placed on the old server after your first transfer can be absent from the Cloudways database. Decide which system is authoritative for the final window, record the time of the last export or synchronization, and verify that the newest order or post is present on the destination before releasing the domain.
Recommended Free Tools
Test the Cloudways copy before changing DNS
Use the temporary Cloudways URL or another pre-cutover testing method. Do not rely on the home page alone; test the paths that create data, send messages or call outside services.
Content and navigation
- Open representative posts, pages, categories, author archives and custom post types.
- Load images, galleries, downloadable files and responsive variants.
- Check navigation menus, widgets, internal links, pagination and search.
- Confirm that permalinks return the intended pages rather than 404 errors.
Accounts, forms and commerce
- Sign in and sign out with a normal user and an administrator account.
- Submit contact, registration and password-reset forms, and verify delivery of the expected messages.
- For WooCommerce, add an item to the cart, change quantities, apply a coupon if used, proceed through checkout in a safe test mode, and inspect order creation.
- Check payment callbacks and webhooks without charging a customer. Confirm that the callback endpoint uses the correct domain and HTTPS scheme.
Operations and integrations
- Run or inspect scheduled jobs, backups, queues and import tasks.
- Confirm analytics, tag managers, advertising pixels, API integrations and license activations.
- Check redirects, robots directives, XML sitemaps, canonical URLs and any security or cache plugin settings.
- Inspect PHP and application logs for fatal errors, missing extensions, permission errors and blocked requests.
Cloudways specifically recommends reviewing the migrated website before DNS is updated so problems can be found while the old site still serves visitors. Record each test result and fix failures on the destination rather than trying to patch both hosts at once.
Change DNS only after the copy is ready
- Lowering DNS TTL before migration can reduce the time some resolvers retain the old address, but TTL behavior is controlled by the DNS provider and does not guarantee instant worldwide change.
- At the agreed cutover time, update the domain’s relevant DNS record or records to the Cloudways server IP shown in Access Details. DNS changes are not performed automatically by the data transfer.
- Leave unrelated mail and third-party records unchanged unless your documented design requires a change.
- Watch resolution from more than one network and verify that the public domain loads the Cloudways copy. Some visitors and recursive resolvers will continue using cached answers during propagation.
- Keep the source online and unchanged while propagation occurs. Do not accept new orders or publish conflicting content on both hosts.
If the domain uses a subdomain network, include the required subdomain records and wildcard planning before this step. Multisite has additional DNS and certificate considerations described below.
Install SSL, enforce HTTPS and clear caches
After the domain resolves to Cloudways, install or upload the SSL certificate required by your setup. Confirm that the certificate covers the primary domain and every hostname visitors use. Test both the bare domain and the www variant, then verify that login, forms, images, API callbacks and payment return URLs use HTTPS.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallRank #4
Only force HTTPS after the certificate works on the public hostname. Enabling a redirect too early can create a loop or make the dashboard inaccessible. Once HTTPS is confirmed, purge the relevant application, page, CDN and browser caches so an old redirect or page is not masking the new site. Recheck mixed-content warnings and any hard-coded HTTP URLs.
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 guide states that WordPress Multisite is currently supported only on Cloudways Flexible. A subdomain network needs DNS entries for the mapped subdomains and wildcard SSL planning; a subdirectory network has different domain and path requirements. Inventory every site in the network, its mapped domains and upload paths before starting. Test network administration, each mapped domain, media, login and site-specific plugins on the temporary destination. Do not assume that a single primary-domain DNS change completes a multisite cutover.
WooCommerce and other high-change sites
Orders, customer accounts, subscriptions, bookings and comments can be written while a migration is running. Schedule a maintenance window or perform a final database and file synchronization immediately before DNS. Compare the newest records on both hosts, verify payment and email callbacks, and keep the old site available as a rollback source until the new site is confirmed.
Large uploads or custom directories
Tell the Migrator or managed-migration team about media stored outside the usual uploads directory, custom table prefixes, protected staging paths and server-generated files. Omitting a custom directory can produce a site that appears complete while downloads, image processing or a plugin silently fails.
Troubleshoot common migration failures
The Migrator cannot connect
- Re-copy the SFTP host, username, password and database name from the current Cloudways Access Details panel; do not rely on an old screenshot.
- Check that the source permits the connection and that password protection is disclosed.
- Confirm the source root directory and database settings, then retry after removing any temporary network restriction.
The site loads but links or images point to the old domain
Complete a WordPress-aware URL search and replace, including serialized options, then regenerate caches and retest internal links, media and canonical URLs. Avoid editing serialized values with a plain text tool.
Permalinks return 404 errors
Save the permalink settings on the destination, inspect rewrite configuration and verify that the active web server and PHP setup match the application’s requirements. Test a post, page, archive and custom post type rather than only the front page.
Best Value
Forms or email do not arrive
Check the SMTP or transactional-email configuration, sender domain, DNS authentication and plugin logs. Send a controlled test and confirm that the destination is not still calling an old hostname or callback URL.
Orders or recent posts are missing
Identify the last synchronization time, compare the source and destination databases, and repeat the final sync while writes are paused. Do not simply point DNS back and forth while both sites continue accepting changes.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →HTTPS redirects loop or show certificate warnings
Verify that the certificate is installed for the public hostname, that the domain resolves to Cloudways, and that proxy or cache settings are not forcing conflicting schemes. Remove forced HTTPS temporarily if needed, correct the certificate or proxy setting, then enable the redirect again.
Rollback and retirement of the old host
Keep the old hosting account, files and final database backup until DNS propagation is complete and the latest website data is confirmed on Cloudways. Cloudways explicitly advises not deleting or canceling the old account until the domain has been pointed, DNS changes have propagated and the latest data is available on Cloudways.
If a serious defect appears during propagation, stop writes, document which host contains the newest data, and restore service from the known-good host rather than allowing two divergent databases to continue. After the Cloudways copy has remained stable through the agreed observation period, archive the old backup, remove obsolete credentials and cancel the old service only after checking that email, cron jobs, redirects and every required subdomain are independent of it.
Quick Recap
A practical cutover checklist
- Complete files-and-database backup is stored independently and can be opened.
- Domains, subdomains, email, cron, redirects, integrations, licenses and custom paths are inventoried.
- Cloudways WordPress application is launched and Access Details are recorded securely.
- Chosen migration route and maintenance window are confirmed.
- Destination copy is tested for content, media, permalinks, login, search, forms, checkout, email, cron, redirects, analytics and callbacks.
- Final synchronization is complete, with no unaccounted-for orders or content on the old host.
- DNS records point to the Cloudways server IP and propagation is being monitored.
- SSL works on every public hostname before HTTPS enforcement and cache purges.
- Old hosting remains available until the latest data and public-domain behavior are verified.
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.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →
