Disclosure: This content is reader-supported, which means if you click on some of our links that we may earn a commission.
Migrating WordPress to Cloudways is one of the highest-ROI hosting moves you can make. A typical shared hosting site running at 400โ800ms TTFB will land at 72ms after migration โ a 5โ10x improvement in raw server response time. This guide covers the exact steps using the free Cloudways Migrator plugin for zero-downtime migration.
Total time: 30โ60 minutes of active work. Most of that is waiting for file transfers.

Cloudways Pros
- Free Cloudways Migrator plugin โ handles migration automatically
- 72ms TTFB on Vultr HF after migration
- 1-click staging โ test your migrated site before DNS cutover
- Zero-downtime migration via staging URL workflow
- 5 cloud providers: Vultr HF, DigitalOcean, AWS, GCE, Linode
- Pre-configured Nginx + Redis + Memcached stack
Cloudways Cons
- No email hosting โ set up Zoho or Google Workspace separately
- $14/mo minimum โ shared hosting users will see a price increase
Speed Benchmarks
- TTFB: 78ms
- Load Time: 0.6s
- Uptime: 99.99%
Start Cloudways โ Code CLOUDS2022 = $30 Free Credit โฆ
Before You Migrate: Checklist
Pre-Migration Checklist
- โ Back up your current WordPress site (files + database)
- โ Note your current host's nameservers and DNS settings (screenshot or export)
- โ Lower your domain's DNS TTL to 300 seconds โ do this 24 hours before migration
- โ Create a Cloudways account (use code CLOUDS2022 for $30 credit)
- โ Choose your cloud provider and server size (Vultr HF 1c/1GB = $14/mo recommended for start)
- โ Plan your email strategy โ Cloudways does not include email hosting
- โ Confirm your site's database size (wp-admin โ Tools โ Site Health for rough estimate)
Email planning is the most overlooked step. Decide before you touch DNS: will you keep email on your current host (just update the A record, leave MX), use Google Workspace, or set up Zoho Mail? Getting this wrong can cause email outages during cutover.
Step 1: Create Your Cloudways Server
- Log in to Cloudways โ click Add Server
- Select Application: WordPress (latest)
- Enter an application name (e.g., your domain name)
- Select Server: Vultr High Frequency (recommended)
- Select Server Size: 1GB RAM ($14/mo) for under 30k monthly visitors; 4GB RAM ($50/mo) for WooCommerce or higher traffic
- Select Location: closest to your primary audience
- Click Launch Now
Server spin-up takes approximately 60 seconds. You'll see the server status change from "Deploying" to "Running" in the dashboard.
Which Server Size to Choose
- 1c/1GB ($14/mo) โ blogs, brochure sites, under 30k visits/month
- 2c/4GB ($50/mo) โ WooCommerce, membership sites, 30kโ150k visits/month
- 4c/8GB ($118/mo) โ high-traffic sites, multiple applications, agencies
You can scale up in seconds from the Cloudways dashboard โ no migration needed. Start at 1c/1GB and upgrade if needed.
Step 2: Note Your Cloudways Server Credentials
You'll need these credentials for the Migrator plugin:
- In Cloudways dashboard โ go to your server โ click SFTP/SSH tab (or Master Credentials)
- Note: Server IP, SFTP Username, SFTP Password, Port (22)
- Also note your application's MySQL details under Application โ Access Details โ Database
Alternatively, the Cloudways Migrator plugin uses an API-based connection โ you can authenticate with your Cloudways email and API key instead of SFTP credentials, which is simpler. Get your API key from Cloudways โ Account โ API Access.
Step 3: Migrate Using the Cloudways Migrator Plugin
This is the easiest migration path for most WordPress sites.
- On your current (old) WordPress site, go to Plugins โ Add New
- Search for "Cloudways WordPress Migrator" โ Install โ Activate
- Go to Cloudways Migrator in the left menu
- Enter your Cloudways email address and API key
- Select your target Server and Application from the dropdowns
- Choose whether to migrate with or without the uploads folder (always include unless you've moved media to S3/CDN)
- Click Migrate
The plugin copies your WordPress files and database to Cloudways. Your old site stays live throughout. Migration time depends on site size:
- Under 500MB: 5โ15 minutes
- 500MBโ2GB: 15โ30 minutes
- 2GB+: 30โ60+ minutes
Alternative Migration Methods
| Cloudways Migrator Plugin,Most sites โ 1-click automated,10โ30 minutes,None โ guided wizard | All-in-One WP Migration,Sites under 512MB,15โ45 minutes,Low | Manual FTP + phpMyAdmin,Custom setups, large databases,1โ3 hours,Intermediate | WP CLI (SSH),Developers, large sites,30โ60 minutes,Advanced | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| M | e | t | h | o | d | |||||||||
| B | e | s | t | F | o | r | ||||||||
| T | i | m | e | R | e | q | u | i | r | e | d | |||
| T | e | c | h | n | i | c | a | l | S | k | i | l | l |
Step 4: Test on the Cloudways Staging URL
Before touching DNS, test everything on Cloudways' temporary URL.
- In Cloudways dashboard โ Application โ Access Details
- Copy the Application URL (format:
something.cloudwaysapps.com) - Visit this URL โ your migrated site is live here without affecting your live domain
- Test: homepage, posts, pages, contact forms, WooCommerce checkout (if applicable)
- Check: images load, menus work, SSL is active, no broken links
- Log in to wp-admin at the staging URL and verify all plugins/settings
Common Issues to Check Before DNS Cutover
- Hardcoded URLs in theme or plugin code (use Better Search Replace to update)
- SSL certificate not yet provisioned (Cloudways โ SSL โ provision free Let's Encrypt cert)
- WooCommerce payment gateway settings โ re-enter API keys if needed
- Contact form email delivery โ configure SMTP plugin since Cloudways doesn't include email
- Redis cache not yet enabled (configure in Step 6 before going live)
Step 5: Configure Email
Cloudways has no built-in email. Solve this before DNS cutover or you'll lose incoming email.
Option A โ Keep email on your current host (simplest):
- Only change your domain's A record to point to Cloudways
- Leave MX records unchanged โ they keep pointing to your current host's email
- Your website moves to Cloudways; email stays on old host
Option B โ Zoho Mail (free, 1 domain, 5 users):
- Sign up at zoho.com/mail โ choose the free Forever plan
- Verify domain ownership, add Zoho's MX records to DNS
- Do this before DNS cutover so email works immediately after
Option C โ Google Workspace ($6/mo per user):
Most reliable for business use. Set up Workspace first, verify domain, add MX records, then do DNS cutover.
For WordPress transactional email (contact forms, WooCommerce order notifications), install WP Mail SMTP with SendGrid (free up to 100 emails/day) or Gmail SMTP.
Step 6: Enable Redis and Configure Caching
This step is what makes Cloudways significantly faster than most hosts โ and it's the most commonly skipped.
Enable Redis Object Cache:
- Cloudways dashboard โ Server โ Settings & Packages โ Packages tab
- Toggle Redis to ON โ click Save Changes
- In WordPress โ install WP Redis plugin (or Redis Object Cache) โ activate
- wp-admin โ Settings โ Redis โ verify "Connected" status
Configure Breeze Cache Plugin (Cloudways' free cache plugin):
- wp-admin โ Plugins โ search "Breeze" โ install โ activate
- Settings โ Breeze โ enable: File Minification, Gzip, Browser Cache, CDN (if using Cloudflare)
- Purge cache after saving settings
What Redis Does for Your TTFB
Without Redis: every WordPress page request runs 40โ80 database queries. With Redis: repeat page requests serve from in-memory cache โ 0 database queries. This is the primary reason Cloudways (72ms TTFB) outperforms stock server installs (~145ms+) on the same hardware. Enable Redis before going live.
Step 7: Lower Your DNS TTL
This step must be done 24 hours before you plan to change DNS โ not immediately before.
- Log into your domain registrar (Namecheap, GoDaddy, Cloudflare, etc.)
- Find the A record for your root domain (@) and www subdomain
- Change the TTL to 300 (5 minutes) or the lowest value allowed
- Save โ wait 24 hours for this change to propagate
With a 5-minute TTL, your DNS cutover in Step 8 will be fully propagated within 5โ15 minutes for most visitors. Without this step, propagation could take up to 48 hours, during which some visitors still hit your old server.
Step 8: Final DNS Cutover
You've tested the migrated site. Email is configured. Redis is active. TTL is 300 seconds. Time to go live.
- Get your Cloudways server IP: dashboard โ Server โ right side panel shows the Public IP
- Log into your domain registrar โ DNS management
- Update the A record for
@(root domain) to your Cloudways server IP - Update the A record for
wwwto the same Cloudways server IP - Save changes
- Wait 5โ15 minutes (or up to a few hours depending on your ISP's DNS cache)
- Visit your domain โ you should now be live on Cloudways
Verify the switch: Use DNSChecker.org to see real-time propagation status across global DNS servers. Green checkmarks = your IP has propagated in that region.
Once confirmed live: add your real domain in Cloudways (Application โ Domain Management โ Add Domain), provision your SSL certificate (SSL โ Let's Encrypt), and update WordPress to use HTTPS if not already set.
Performance After Migration
What to expect after a successful Cloudways migration with Redis configured:
| TTFB (idle),400โ800ms,72ms,5โ10x faster | Load Test: 50 Users,Often 1000ms+,85ms,10x+ faster | Load Test: 100 Users,Timeout / Error,98ms,No more crashes | WooCommerce Checkout,500msโ2s,156ms @ 100 users,3โ13x faster | Uptime,99.5โ99.9%,99.981%,+0.08โ0.48% | PHP Workers,1โ2 (shared),30+ (dedicated),15x+ capacity | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| M | e | t | r | i | c | ||||||||||||||||||||
| S | h | a | r | e | d | H | o | s | t | i | n | g | ( | B | e | f | o | r | e | ) | |||||
| C | l | o | u | d | w | a | y | s | V | u | l | t | r | H | F | ( | A | f | t | e | r | ) | |||
| I | m | p | r | o | v | e | m | e | n | t |
The performance gain is most dramatic if you're migrating from shared hosting. If you're migrating from another managed cloud platform, the improvement will be smaller โ but you'll gain Cloudways' specific stack optimizations and provider flexibility.
For maximum performance after migration, see the full Cloudways performance setup guide. For current discount codes, check the Cloudways promo code page.
Troubleshooting Common Migration Issues
Migration plugin fails / times out
Cause: Your current host limits outbound connections or PHP execution time. Solution: Use All-in-One WP Migration plugin (manual export/import) or WP CLI via SSH. Alternative: pay $49 for Cloudways' manual migration service.
Site shows old host's content after DNS change
Cause: Your browser or ISP has cached the old DNS. Solution: Test in a new incognito window or use a mobile connection (different DNS cache). DNSChecker.org will show if propagation is complete globally.
SSL certificate error after going live
Cause: SSL was provisioned on the staging URL, not the real domain. Solution: In Cloudways โ Application โ SSL โ delete the staging certificate โ add your real domain โ provision Let's Encrypt.
WooCommerce orders not processing
Cause: Payment gateway API keys often need re-entry after migration (some are stored in options table with hashed values). Solution: WooCommerce โ Settings โ Payments โ re-enter your live API keys for each gateway.
Contact forms not sending email
Cause: Cloudways has no outbound email server. Solution: Install WP Mail SMTP โ configure with SendGrid (free) or your Google Workspace SMTP. Test by submitting the form after setup.
If you want a managed migration where their team handles it, ScalaHosting includes free migration as part of their managed VPS onboarding โ and delivers 28ms TTFB post-migration.

Why We Like It
- 28ms TTFB โ 61% faster than Cloudways post-migration
- Free migration service โ their team does it for you
- Email included โ no extra setup needed
- $29.95/mo for 2c/4GB โ cheaper than Cloudways Year 1
Drawbacks
- Renewal jumps to ~$82/mo after intro term
- No Git deployment workflow
Performance Specs
- Port Speed: 1Gbps (Dedicated)
- Throughput: High (Stable)
- Traffic: Unmetered
Cloudways Migration FAQ
How long does it take to migrate WordPress to Cloudways?
Most migrations take 10โ30 minutes using the Cloudways Migrator plugin. The automated plugin handles file transfer and database export/import. Larger sites (10GB+) take longer depending on your current host's upload speed. DNS propagation after the final cutover takes 1โ48 hours (typically under 4 hours with a low TTL). The active migration window โ where your site might show stale content โ is just the DNS propagation period, not the migration itself.
Is the Cloudways Migrator plugin free?
Yes โ the Cloudways Migrator plugin is free. Install it on your existing WordPress site, enter your Cloudways server credentials, and it handles the migration automatically. There's no per-migration charge. Cloudways also offers a paid manual migration service ($49) for complex setups, but for standard WordPress sites the free plugin covers it.
Can I migrate without downtime?
Yes โ this guide uses a zero-downtime workflow. The Cloudways Migrator copies your site to the new server while your old site stays live. You test everything on the Cloudways staging URL. Only when you're satisfied do you change DNS. During DNS propagation (1โ48 hours), some visitors hit the old server and some hit the new one โ both have identical content since you don't update the old site after migration. Zero downtime, zero data loss.
What happens to my email after migrating to Cloudways?
Cloudways does not include email hosting. Before changing DNS, you must migrate your email separately. Options: (1) Google Workspace โ $6/mo per user, most reliable; (2) Zoho Mail โ free for 1 domain, 5 users; (3) Keep email with your old host โ only change your A record for the website, leave MX records pointing to the original host. Option 3 is the easiest if your current host is just slow for WordPress but fine for email.
How do I set a low DNS TTL before migration?
Log into your domain registrar or DNS provider and find the A record for your domain. Change the TTL (Time To Live) to 300 seconds (5 minutes) at least 24 hours before your migration. This means when you update the A record during cutover, 95% of visitors will see the new server within 5 minutes instead of up to 48 hours. After migration is confirmed working, you can raise TTL back to 3600 (1 hour) or higher.
What if the Cloudways Migrator plugin doesn't work?
Common failure causes: (1) Your old host blocks outbound connections โ use All-in-One WP Migration plugin as a fallback; (2) Site is over the plugin's size limit โ use WP CLI via SSH instead; (3) Incorrect Cloudways credentials โ double-check SFTP username, password, and server IP from the Cloudways dashboard under Server Management > Master Credentials. If all else fails, Cloudways' paid migration service ($49) is available, and ScalaHosting includes free migration done by their team.
Do I need to reconfigure WordPress after migrating to Cloudways?
Minimal reconfiguration. The Migrator plugin handles the database (updating site URLs automatically). You'll need to: (1) Add your domain in Cloudways under Application > Domain Management; (2) Provision SSL (1-click in Cloudways); (3) Configure Redis object caching in Cloudways and install WP Redis plugin; (4) Install and configure Breeze (Cloudways' free cache plugin) or your existing cache plugin. Most plugin/theme settings carry over automatically since they're stored in the database.
What's the best Cloudways plan for a newly migrated site?
Start with Vultr HF 1c/1GB at $14/mo for sites under 30,000 monthly visitors. If you run WooCommerce or have consistent traffic above 10,000 sessions/month, go directly to 2c/4GB ($50/mo on Vultr HF). You can scale up in seconds in the Cloudways dashboard with no migration needed. Use the promo code CLOUDS2022 for $30 free credit โ effectively free for the first 2 months on the starter plan.
Migrate to Cloudways โ Code CLOUDS2022 = $30 Free Credit โฆ
Related: Cloudways promo code ยท Cloudways performance setup guide ยท Cloudways full review



