Illustration for migrating WordPress to Cloudways: pages copied from one server to a cloud server

This article contains affiliate links. AutomateWithMNK may earn a commission if you sign up through certain links, at no additional cost to you. This does not influence our editorial assessment.

How to migrate WordPress to Cloudways: overview

There are two official routes. The free Cloudways WordPress Migrator plugin copies your site from your current host into a WordPress application you create on Cloudways. Alternatively, Cloudways’ team runs a managed migration for you, one site free, requested through a support ticket. Either way, your current site stays online during the copy, and visitors only move once you point the domain at Cloudways.

The steps below follow Cloudways’ official pages and the plugin’s WordPress.org listing, . If a menu label in your dashboard differs, follow the dashboard.

Set up a Cloudways server for your site

Still weighing the move? Our Cloudways review covers who it suits.

Plugin or managed migration?

Official migration routes (checked October 21, 2026)
PointCloudways WordPress MigratorManaged migration
CostFree; unlimited sites according to CloudwaysOne free migration per account
Who does itYou, by filling in a few fieldsCloudways’ team, via a support ticket
Advertised duration“Less than an hour” in most cases, per CloudwaysDepends on the support queue
Autonomous trialPlugin availableNot included in the Autonomous trial
Best forStandard WordPress sitesUnusual setups, or if you would rather delegate

Phase 1: prepare the old site

  • Take a full backup at your current host and download it.
  • Check versions: the plugin listing requires WordPress 4.0 and PHP 7.0 or newer.
  • List the redirects and rewrites stored in .htaccess. Cloudways’ NGINX-based Lightning Stack does not read .htaccess files, so those rules must be rebuilt.
  • Decide where your email will live. Mailboxes hosted by your current provider do not travel with the site.

Phase 2: prepare the Cloudways app

  1. Launch a server, or use an existing one, and add a WordPress application.
  2. Leave its default WordPress site untouched; the official guide warns that deleting it makes the migration fail.
  3. In the app’s Access Details tab, note the Application URL, the Public IP and the DB Name.
  4. Create an SFTP user with + Add SFTP User, or use the server’s master credentials, depending on what your dashboard offers.
  5. For a multisite network, enable multisite on the destination app first; Cloudways’ help center describes that choice as permanent.

Phase 3: run the plugin

  1. On the old site, go to Plugins then Add New, search for “Cloudways migrator”, install and activate it (WP-CLI also works: wp plugin install bv-cloudways-automated-migration).
  2. Enter your email address, used for progress updates, and accept the terms.
  3. Select Cloudways Flexible, or Autonomous if that is your product line.
  4. Paste the Application URL without a trailing slash, then the Public IP and the DB Name.
  5. Enter the SFTP username and password.
  6. When asked whether the site is password-protected, answer no unless you protected the whole Cloudways app.
  7. When asked about additional database tables, answer yes so plugin settings come across too.
  8. Start the migration and watch it to completion.

Phase 4: test the copy

Open the Cloudways Application URL; it should look exactly like the original. Then work through this checklist:

Post-migration checks before switching DNS
CheckHowPass when
PagesHome page, an image-heavy page, a postSame content and layout as the original
FormsSend yourself a test messageMessage received
AdminLog in to wp-adminDashboard and plugins load
StoreGo through checkout up to payment, no real orderCart, shipping and taxes as before
RedirectsOpen your key old URLsThey reach the right pages without .htaccess

If links still point to the old address, the official guide suggests a search-and-replace of the old URL in the database, for example with the Better Search Replace plugin.

Phase 5: go live

  1. Add your domain as the primary domain of the Cloudways application.
  2. At your registrar or DNS host, point the domain to the server’s Public IP. Lowering the DNS TTL a few hours beforehand is common practice so the change propagates faster.
  3. Once the domain resolves to Cloudways, install the free Let’s Encrypt certificate from the dashboard.
  4. Keep the old hosting active for a few days while propagation completes and you finish checking.
  5. Run an on-demand backup on Cloudways: your first clean restore point. According to Cloudways’ blog, backups require a paid account, so during a Flexible trial keep the backup you downloaded from your old host.

Known gotchas

  • Deleting the default site on the destination app breaks the migration.
  • Non-standard layouts: on the plugin’s WordPress.org page, a user reports that a Bedrock-based site failed. Use the managed migration for such sites.
  • .htaccess rules are ignored by the Lightning Stack.
  • Email forgotten at DNS switch time.
  • Stacked caching plugins after the move; test before keeping more than one.

Rollback plan

Until DNS changes, nothing has changed for visitors, so you can rerun the migration freely. After the switch, keep the old host and its backup until checks are done; restoring the old DNS records sends visitors back to the old site if something serious goes wrong.

Start on Cloudways with the free trial

FAQ

Is migrating to Cloudways free?

Yes. The Cloudways WordPress Migrator plugin is free and, according to Cloudways, covers unlimited sites. One managed migration by the team is also free.

Will my site go down during the migration?

No. The copy runs while the original site stays online; visitors only reach Cloudways after the DNS change.

Can I migrate during the free trial?

Yes, the trial lets you migrate a site. The managed migration is not part of the Autonomous trial.

Does my email move with the site?

No. Email is not included in the Cloudways server price, so set up an email service before switching DNS.

Sources

Pages checked on .