Summarize this blog post with: ChatGPT | Perplexity | Claude | Grok

You already know that switching hosts can improve your website’s infrastructure, but the migration itself can create downtime, missing data, broken URLs, or configuration problems. What many website owners miss is that Cloudways Free Migration follows different rules depending on the application and Cloudways product. In this guide, you’ll learn exactly what is free, who qualifies, how to migrate, and what to verify before changing DNS.

Key Takeaways

• Cloudways Free Migration can move eligible websites to Cloudways without a separate migration charge, but eligibility depends on the application type, migration method, account status, and hosting product. (Cloudways Help Center)
• WordPress and WooCommerce managed migrations are currently listed as free in Cloudways’ March 27, 2026 Help Center guidance. (Cloudways Help Center)
• Cloudways WordPress Migrator supports unlimited free self-service WordPress and WooCommerce migrations. (Cloudways Help Center)
• Non-WordPress managed migrations can cost $99 per application after applicable included allowances; Cloudways currently lists one free non-WordPress migration for Standard and up to five for Agency. (Cloudways Help Center)
• Cloudways Autonomous active-plan users currently qualify for unlimited free managed inbound migrations, while trial users are directed to self-service migration tools. (Cloudways Help Center)
• WordPress Multisite is currently supported by the Migrator workflow on Cloudways Flexible, not Cloudways Autonomous. (Cloudways Help Center)
• A safe migration is not finished when files are copied; you should validate the destination, HTTPS, DNS, forms, redirects, ecommerce functionality, analytics, and other critical workflows before cancelling the old host.

What Is Cloudways Free Migration and How Does It Work?

Cloudways Free Migration is a website-transfer service that moves an existing application from another hosting environment to Cloudways while preserving the website’s files, database, and configuration. Cloudways currently provides both expert-managed migration and self-service migration options, with the applicable cost depending on the application and Cloudways product. (Cloudways Help Center)

A hosting migration normally involves a source server and a destination server. The source is your existing hosting environment, while the destination is the new Cloudways application receiving the website data. Cloudways’ June 2026 documentation describes migration as transferring files, databases, media, plugins, themes, and other application data required for the website. (Cloudways Help Center)

Cloudways offers two primary migration paths:

1. Managed migration: Cloudways specialists perform the transfer using the credentials or backup information you provide.
2. Self-service migration: WordPress and WooCommerce users can use Cloudways WordPress Migrator to perform the transfer themselves. (Cloudways Help Center)

The distinction matters because a claim such as “Cloudways migration is free” is incomplete without identifying what you are migrating and how you are migrating it.

[Insert image: Cloudways migration paths showing managed migration versus WordPress Migrator self-service migration | Alt text: “Compare Cloudways Free Migration methods”]

Why Does Cloudways Free Migration Matter When Switching Hosts?

Cloudways Free Migration matters because it can remove both the technical workload and a separate migration fee from an otherwise complex hosting move. Cloudways says its managed service transfers website files, databases, and settings, then tests the migrated website after the transfer. (Cloudways)

For example, moving a 50-page affiliate WordPress website manually may require exporting a database, copying wp-content, adjusting configuration files, performing URL replacements, checking permissions, and troubleshooting the destination. A managed or automated migration can eliminate much of that manual work.

The migration benefit becomes more significant for dynamic websites. A WooCommerce store can receive new orders while its database is being copied, while a membership website can receive new registrations or profile changes. The operational risk therefore depends on how frequently the source database changes, not simply on the number of pages.

A broader Cloudways review can help you decide whether the platform itself fits your requirements before investing time in migration.

Why free migration does not mean a risk-free migration

Free describes the migration charge, not the operational risk. DNS changes, email routing, plugin compatibility, PHP differences, ecommerce transactions, external APIs, cron jobs, caching, redirects, and custom code can still require validation after the transfer.

Cloudways itself recommends reviewing the migrated website before DNS is changed, particularly important pages and ecommerce workflows such as cart and checkout. (Cloudways Help Center)

→ Explore Cloudways Migration Options

Is Cloudways Website Migration Really Free in 2026?

Cloudways website migration is currently free for WordPress and WooCommerce through both the self-service WordPress Migrator and expert-managed migration, according to the March 27, 2026 Cloudways Help Center. Non-WordPress applications follow different pricing rules, while Cloudways Autonomous has a separate unlimited managed-migration policy for active plans. (Cloudways Help Center)

Policy verified: August 9, 2026.

Cloudways Free Migration at a glance

Current pricing and eligibility are documented across Cloudways’ managed-migration, Autonomous, and WordPress Migrator documentation. (Cloudways Help Center)

→ Compare Cloudways Migration PlansConclusion

“WordPress and WooCommerce migrations are free, even when handled by Cloudways experts”

— Syed Abuzar Mehdi, Cloudways Help Center author, How to Request a Managed Application Migration to Cloudways, 2026 (Cloudways Help Center)

The quotation is important because older Cloudways messaging can lead readers to believe that only one expert migration is free. The newest migration-specific Help Center guidance provides a more application-specific policy.

Why does Cloudways still mention a “first free migration” elsewhere?

Cloudways currently has conflicting first-party wording. The March 27, 2026 Help Center says managed WordPress and WooCommerce migrations are free, while Cloudways’ public application-migration marketing page still says the first expert migration is free and later PHP-based migrations cost $99. (support.cloudways.com)

For a current purchasing decision, the newer migration-specific Help Center should carry more weight, but you should verify the policy shown inside your Cloudways account before submitting a business-critical migration.

You should also separate migration fees from hosting costs. My Cloudways pricing guide explains the hosting charges that continue after the migration itself.

View Cloudways plans for your migration

What Is the Difference Between Cloudways Managed Migration and WordPress Migrator?

Cloudways Managed Migration is a hands-off service performed by Cloudways specialists, while Cloudways WordPress Migrator is a self-service plugin for WordPress and WooCommerce. Both can currently be free for WordPress and WooCommerce, but the right choice depends more on risk and complexity than price. (Cloudways Help Center)

Cloudways currently accepts managed-migration connection methods including SSH, SFTP, FTP, cPanel, and other hosting access methods. (Cloudways Help Center)

When should you use managed migration?

Choose managed migration when:

• The website generates meaningful revenue.
• You are moving WooCommerce or another frequently changing database.
• The existing host has an unusual configuration.
• You lack confidence with SFTP, databases, or DNS.
• Custom code or integrations increase migration risk.
• You want Cloudways to perform specified functional checks.

When should you use Cloudways WordPress Migrator?

Choose the plugin when:

• You have a standard WordPress installation.
• You can access both WordPress and Cloudways.
• You are comfortable validating the migration yourself.
• You are moving several WordPress websites.
• You want to control the migration schedule directly.

→ Evaluate Cloudways Migration Methods

For hosting-specific considerations, see my planned Cloudways WordPress hosting guide.

How Should You Prepare Your Website Before Migrating to Cloudways?

Preparing for a Cloudways migration means creating a recoverable source state, checking destination compatibility, documenting external dependencies, and deciding how the final traffic cutover will work before copying data. Cloudways specifically recommends checking destination storage and PHP compatibility before an assisted migration. (Cloudways Help Center)

Use this pre-migration checklist

Before starting:

1. Create a fresh independent website backup.
2. Record the current DNS records.
3. Confirm where your email is hosted.
4. Check source-site disk usage.
5. Confirm sufficient destination storage.
6. Record the source PHP version.
7. Review critical plugins, themes, and custom code.
8. Identify scheduled tasks and cron jobs.
9. List third-party integrations and webhooks.
10. Document checkout, login, form, and other critical workflows.
11. Plan a rollback path.
12. Keep the existing hosting account active.

Cloudways’ June 2026 end-to-end migration guide recommends comparing the source and destination PHP environments because incompatible versions can cause plugin, theme, or application problems after migration. (Cloudways Help Center)

“Existing application data on the target will be overwritten.”

— Syed Abuzar Mehdi, Cloudways Help Center author, How to Request a Managed Application Migration to Cloudways, 2026 (Cloudways Help Center)

The warning means you should not treat the destination Cloudways application as permanent storage before migration. Back up anything already present in that destination if you need to retain it.

Use a simple pre-migration risk score

The following framework is an editorial risk assessment rather than a Cloudways policy. Add one point for each condition:

• Active WooCommerce orders or other live transactions
• Memberships, forums, user-generated content, or frequent account changes
• WordPress Multisite
• Significant custom PHP or application code
• Large databases or media libraries relative to destination capacity
• Email mailboxes hosted with the old hosting account
• Critical external webhooks, APIs, or scheduled processes

0–1 points: Low-risk migration
2–3 points: Moderate-risk migration
4+ points: High-risk migration

For example, a mostly static affiliate blog with no email hosted on the source account may be low risk. An active WooCommerce store with custom payment integrations, customer accounts, webhooks, and source-hosted email should be treated as high risk.

A more detailed website migration checklist can be used as a reusable pre-flight process.

Should you lower DNS TTL before migration?

Lowering DNS TTL before the planned cutover can make a later DNS change easier to reverse or propagate through recursive caches more quickly. The exact timing and TTL value depend on your DNS provider and current configuration, so treat this as a planning recommendation rather than a universal Cloudways requirement.

Most importantly, do not change DNS before you have tested the destination copy.

How Do You Request a Free Managed Migration From Cloudways?

You request a Cloudways managed migration through the Cloudways Platform by opening Integrations, accessing Application Migration, selecting the destination application, providing source-site and connection details, adding special instructions, and submitting the request. Cloudways documents this workflow in both its March and June 2026 migration guides. (Cloudways Help Center)

Step 1: Create your destination application

Launch or select the Cloudways application that should receive the migrated website. The destination matters because Cloudways warns that existing application data can be overwritten during migration. (Cloudways Help Center)

Step 2: Open Application Migration

From the Cloudways Platform:

1. Open Integrations.
2. Locate Application Migration.
3. Review the migration information.
4. Start the application migration request. (Cloudways Help Center)

[Insert image: Cloudways Integrations page with Application Migration highlighted | Alt text: “Request Cloudways Free Migration from Integrations”]

Step 3: Select your destination

Choose:

• The applicable Cloudways product
• The destination application
• Any required subsite information

Cloudways’ current migration form allows users to identify subsites and other application details when relevant. (Cloudways Help Center)

Step 4: Provide source website details

Depending on the application, Cloudways may request:

• Domain name
• Admin or backend URL
• Admin username
• Admin password
• CMS/back-office information
• Subsite details (Cloudways Help Center)

Step 5: Add server connection credentials

Current supported connection choices include:

• SSH
• SFTP
• FTP
• cPanel
• Other Hosting

You may need the username, password, host or IP address, and port. Some SFTP/FTP migration cases can also require database access information. (Cloudways Help Center)

Step 6: Tell Cloudways what to test

Use the request form to identify critical functionality.

For a WooCommerce website, for example, request checks for:

• Add to cart
• Checkout
• Customer login
• Contact forms
• HTTPS redirects

Cloudways explicitly allows users to specify migration tests such as checkout, login, registration, and other important workflows. (Cloudways Help Center)

“Providing complete information at the beginning helps the migration team begin the process faster and reduces the need for repeated follow-ups.”

— Syed Abuzar Mehdi, Cloudways Help Center author, How to Request and Manage an End-to-End Application Migration on Cloudways, 2026 (Cloudways Help Center)

The practical lesson is simple: collect credentials, special requirements, and testing instructions before opening the migration ticket rather than filling the form while still searching for access details.

How long does Cloudways managed migration take?

Cloudways currently publishes more than one timing statement. Its June 29, 2026 end-to-end guide describes a standard migration SLA of 24 hours per site, while its public migration page says migrations are usually completed within 1–2 business days depending on site complexity. The March migration guide separately says a support engineer will reach out within 48 hours regarding scheduling and next steps. (Cloudways Help Center)

These should be treated as Cloudways provider estimates or service-process targets, not a guaranteed completion time for every migration.

How Do You Migrate a WordPress Site to Cloudways for Free?

You can migrate WordPress to Cloudways for free by creating a destination WordPress application, installing Cloudways WordPress Migrator on the source website, entering the destination application and SFTP information, starting the transfer, and testing the migrated copy before pointing the domain to Cloudways. (Cloudways Help Center)

Step 1: Create a destination WordPress application

Create the new WordPress application in Cloudways. The destination should have enough storage for the source website and a compatible PHP environment. (Cloudways Help Center)

Step 2: Install Cloudways WordPress Migrator

On your existing WordPress website:

1. Go to Plugins → Add New.
2. Search for Cloudways WordPress Migrator.
3. Install the plugin.
4. Activate it. (Cloudways Help Center)

[Insert image: WordPress plugin screen showing Cloudways WordPress Migrator installation | Alt text: “Install Cloudways WordPress Migrator in WordPress”]

See How the WordPress Migration Process Works

This walkthrough shows the Cloudways WordPress Migrator workflow in action, helping you visualize the migration process before entering the destination and SFTP details covered in the next step.

Video: “How to Migrate Your WordPress Site to Cloudways | Cloudways 101” by Cloudways.

Step 3: Enter the migration information

Cloudways’ current plugin documentation identifies information including:

• Cloudways product
• Destination Site URL
• SFTP host/server address
• Database name
• SFTP username
• SFTP password
• HTTP authentication details when applicable
• Optional root directories
• Optional additional database tables (Cloudways Help Center)

The exact interface may change, so use the fields displayed by the current plugin rather than following an outdated screenshot literally.

Step 4: Start the migration

After validating the details, initiate the migration from the plugin. Cloudways says migration time depends on the amount of data being transferred. (Cloudways Help Center)

Step 5: Test the destination

Open the Cloudways-hosted copy and check the website before updating the live domain. Cloudways specifically tells users to test the migrated site after the plugin completes. (Cloudways Help Center)

For WordPress infrastructure selection, see the planned Cloudways WordPress hosting guide.

Can You Migrate WooCommerce to Cloudways for Free?

WooCommerce can currently be migrated to Cloudways for free using either Cloudways WordPress Migrator or Cloudways’ expert-managed migration service. Cloudways lists WooCommerce alongside WordPress for free managed migration and supports WooCommerce with its free self-service Migrator. (Cloudways Help Center)

The migration mechanics are only part of a WooCommerce move. The more important issue is database change during the migration window.

For example, imagine Cloudways copies your store database at 10:00 AM while customers continue ordering on your old server until DNS cutover at 2:00 PM. Orders created after the copied database state can require reconciliation if they are not included in the final migration process.

WooCommerce cutover checklist

For a live store, consider this operational procedure:

1. Choose a low-activity migration window.
2. Take a fresh backup immediately before migration.
3. Record the order number at the beginning of the cutover window.
4. Minimize content, inventory, and customer-account changes where practical.
5. Test add-to-cart and checkout on the Cloudways copy.
6. Test at least one payment workflow appropriate to your environment.
7. Verify customer login and account pages.
8. Check transactional email delivery.
9. Verify webhooks, cron jobs, subscriptions, and external integrations.
10. Reconcile any orders or database changes created during the transition.
11. Change DNS only after the destination passes the checks.

Cloudways’ migration form allows ecommerce owners to request specific tests such as add-to-cart and checkout validation. (Cloudways Help Center)

For store-specific infrastructure considerations, see the planned Cloudways WooCommerce hosting guide.

Can You Migrate WordPress Multisite Using Cloudways Migrator?

WordPress Multisite can currently be migrated with Cloudways WordPress Migrator when the destination uses Cloudways Flexible, but Multisite is not currently supported on Cloudways Autonomous. Cloudways’ June 29, 2026 Migrator documentation explicitly separates the two products for this purpose. (Cloudways Help Center)

“WordPress Multisite is currently supported only on Cloudways Flexible. It is not available on Cloudways Autonomous.”

— Syed Abuzar Mehdi, Cloudways Help Center author, How to Use the Cloudways WordPress Migrator Plugin for Single Site and Multisite Migration, 2026 (Cloudways Help Center)

Multisite owners should therefore select the Cloudways product before beginning migration rather than assuming a destination can be changed later without additional work.

Cloudways also instructs Multisite users to enable Multisite mode on the destination Flexible application and configure the destination to match the source network structure. (Cloudways Help Center)

What Should You Check After Migrating a Website to Cloudways?

Post-migration validation is the process of confirming that the Cloudways copy is functionally, technically, and commercially equivalent to the source website before sending live traffic to it. Cloudways recommends checking the website and important functionality before updating DNS records. (Cloudways Help Center)

Functional checks

Test:

• Homepage
• Main landing pages
• Blog posts
• Images and downloadable files
• Navigation
• WordPress admin
• Contact forms
• Search
• Registration
• Login/logout
• Ecommerce cart and checkout
• Account pages

SEO checks

Compare the source and destination for:

• HTTP status codes
• Canonical URLs
• Redirects
• robots.txt
• XML sitemaps
• Meta robots directives
• Internal links
• HTTPS behavior
• Mixed-content errors
• Analytics tags
• Search Console verification

A hosting migration normally should not intentionally change your URL architecture. Keeping URLs stable reduces the number of SEO variables you must troubleshoot after the server move.

DNS and SSL checks

Confirm:

• Correct A/CNAME records
• Required www behavior
• HTTPS certificate status
• HTTP-to-HTTPS redirects
• DNS provider configuration
• Any CDN or proxy configuration
• MX and other mail-related records

Does Cloudways Free Migration include email accounts?

You should not assume that a Cloudways website migration automatically moves your email mailboxes. Cloudways’ current migration documentation describes website/application data such as files, databases, media, plugins, themes, and related application information; it does not document mailbox transfer as a standard component of the website-migration scope. (Cloudways Help Center)

That is an inference from the documented migration scope rather than a claim that Cloudways can never assist with email. If your mailboxes are hosted by the old web host, confirm the email migration and MX-record plan separately before cancelling that account.

Performance checks

Run the same basic tests before and after migration:

• Server response behavior
• Key page load tests
• Core Web Vitals where sufficient real-user data exists
• PHP/application errors
• Database-heavy workflows
• Logged-in performance
• Checkout performance

Do not claim that Cloudways improved speed merely because the website was moved. A meaningful before-and-after comparison should use comparable pages, test locations, cache states, and traffic conditions.

[Insert image: Google PageSpeed Insights comparison for a migrated site before and after moving hosts | Alt text: “Compare website performance after Cloudways migration”]

[Insert image: Google Search Console indexing and page experience reports after migration | Alt text: “Verify SEO health after Cloudways migration”]

What Tools and Troubleshooting Steps Help With Cloudways Migration?

Cloudways migration troubleshooting should begin by identifying whether the failure comes from the data transfer, destination environment, domain/DNS layer, HTTPS configuration, application code, or post-migration cache. Separating those layers prevents a DNS problem from being treated as a plugin problem or a PHP incompatibility from being mistaken for a failed copy.

Practical migration toolkit

[Insert image: Cloudways destination application URL being used to test a migrated site before DNS cutover | Alt text: “Test Cloudways migrated website before DNS change”]

Common Cloudways migration problems

Cloudways specifically recommends sufficient destination disk space and compatible PHP versions before migration. (Cloudways Help Center)

Real-world migration scenarios

Affiliate WordPress site: A relatively static content website is usually a good candidate for the WordPress Migrator because database changes are limited.

WooCommerce store: Managed migration is attractive because Cloudways can perform the transfer and accept requested checks, but the owner should still control the final order/data cutover.

Agency with 20 WordPress sites: Unlimited self-service WordPress migrations can make bulk moves economical, while agencies can use managed migration for the highest-risk client properties. Cloudways currently provides unlimited free self-service WordPress/WooCommerce migrations. (Cloudways Help Center) For broader agency considerations, see Cloudways for agencies.

WordPress Multisite: Use a Flexible destination and validate network configuration before migration because Autonomous currently does not support Multisite. (Cloudways Help Center)

Laravel or custom PHP application: Check the non-WordPress allowance before submitting the request because additional managed migrations can currently cost $99 per application. (Cloudways Help Center)

[Insert image: Custom migration decision tree separating WordPress, WooCommerce, Multisite, and non-WordPress applications | Alt text: “Choose the right Cloudways Free Migration method”]

What Should You Do Next After Migrating to Cloudways?

The next step after a Cloudways migration is to validate the destination completely before switching DNS, then monitor the live site before cancelling the previous hosting account. Cloudways’ current guidance explicitly recommends reviewing the migrated site before updating DNS. (Cloudways Help Center)

Use this order:

1. Confirm the migration completed.
2. Open the destination copy.
3. Test important URLs and workflows.
4. Check HTTPS and redirects.
5. Confirm your latest required data exists.
6. Confirm the email plan.
7. Take or confirm a Cloudways backup.
8. Update DNS.
9. Monitor application errors and real transactions.
10. Recheck forms, checkout, login, analytics, and indexing.
11. Keep the old hosting environment available until the new environment is proven stable.

Do not cancel your old host immediately after the files finish copying. The old environment is your fastest operational rollback option if a DNS, email, ecommerce, or application problem appears after cutover.

If you are still deciding whether to move, compare the current Cloudways pricing and Cloudways free trial before committing. If you plan to sign up, you can also check the latest Cloudways coupon before completing the purchase.

→ Start Your Cloudways Migration

Conclusion

Cloudways Free Migration is most valuable when you match the migration method to the application’s technical and operational risk rather than simply choosing whatever is free. WordPress and WooCommerce currently have particularly favorable migration options, while non-WordPress applications and Cloudways Autonomous follow their own eligibility rules. (Cloudways Help Center)

For a standard WordPress website, Cloudways WordPress Migrator provides a practical unlimited self-service option. For a valuable WooCommerce store, unfamiliar environment, or complicated application, expert-managed migration can remove much of the transfer work.

Regardless of the method, use the same safe sequence: back up the source, migrate, test the destination, verify critical data and functionality, change DNS, monitor the live website, and cancel the old host only after the new environment is stable.

Frequently Asked Questions About Cloudways Free Migration

How many websites can you migrate to Cloudways for free?

Cloudways currently documents unlimited free self-service migrations for WordPress and WooCommerce through Cloudways WordPress Migrator. It also says expert-managed WordPress and WooCommerce migrations are free, while Autonomous users on active plans can request unlimited free managed migrations. (Cloudways Help Center)

How much does Cloudways charge for non-WordPress migrations?

Cloudways currently lists managed non-WordPress migrations at $99 per application after applicable included allowances. The Standard plan receives one included non-WordPress migration, while Agency receives up to five. (Cloudways Help Center)

Does Cloudways migration cause website downtime?

Cloudways describes managed migration as providing minimal or little-to-no downtime and its marketing page uses zero-downtime language. However, website owners should separately plan DNS cutover and synchronization of rapidly changing data such as ecommerce orders. (support.cloudways.com)

Can you migrate a cPanel website to Cloudways?

Yes. Cloudways currently lists cPanel as one of the connection methods that can be supplied for managed migration, alongside SSH, SFTP, FTP, and other hosting access. (Cloudways Help Center)

Can you migrate WordPress during a Cloudways trial?

Cloudways’ current documentation directs trial users toward self-service migration tools rather than managed migration. The general migration guide says managed migration is unavailable during the trial period. (Cloudways Help Center)

What information does Cloudways need to migrate a website?

Depending on the migration, Cloudways may require the domain, CMS/backend credentials, source-server access through SSH, SFTP, FTP, cPanel, or another hosting method, plus relevant application instructions and tests. (Cloudways Help Center)

What should you do if Cloudways migration fails?

First determine whether the failure involves source access, destination storage, PHP compatibility, the copied application, DNS, SSL, or caching. Keep the source website and backup intact, avoid destructive changes, and use the Cloudways migration ticket or support channel when Cloudways is performing the migration.

When can you cancel your old hosting account?

Cancel the old hosting account only after the Cloudways-hosted site is live and you have verified DNS, HTTPS, forms, ecommerce transactions, logins, redirects, email routing, analytics, scheduled tasks, and other business-critical functions.

References

Cloudways. (2026, March 6). How free managed migrations to Cloudways Autonomous work. Cloudways Help Center. (Cloudways Help Center)

Cloudways. (2026, March 27). How to request a managed application migration to Cloudways. Cloudways Help Center. (Cloudways Help Center)

Cloudways. (2026, June 29). How to request and manage an end-to-end application migration on Cloudways. Cloudways Help Center. (Cloudways Help Center)

Cloudways. (2026, June 29). How to use the Cloudways WordPress Migrator Plugin for single site and Multisite migration. Cloudways Help Center. (Cloudways Help Center)

Cloudways. (n.d.). Expert website migration with zero downtime. Cloudways. Retrieved August 9, 2026. (Cloudways)