Shopify's ease of use is real — quick store setup, a mature plugin ecosystem, payment processing that largely runs itself. But it's ultimately someone else's platform. Store rules, review standards, and risk control logic aren't in your hands. Whether it's a flagged product category, a business model that triggers review, or simply a misidentification by an automated system — any of these can result in a store being frozen or permanently banned. When that happens, the backend is inaccessible, products can't be managed, orders can't be processed, and customer data stops accumulating. Whether recovery is possible depends almost entirely on whether data was backed up beforehand. Setting up a WooCommerce self-hosted store as a backup — or as the primary operation — is the kind of preparation that pays off precisely when you don't expect to need it.
One prerequisite to establish upfront: if a Shopify store is already completely inaccessible, how much can be recovered depends entirely on what was exported before. This guide is primarily useful when the backend is still accessible, or when data was backed up in advance. There's no way to reconstruct data that was never exported.
Why WooCommerce, Why Cloudways
WooCommerce is open source — the site's codebase, database, server, and domain are all under your direct control. That's the most fundamental difference from Shopify. Shopify sells a managed service. WooCommerce gives you an actual asset. That autonomy comes with the responsibility of managing a server, configuring the environment, and maintaining security — setting up a bare VPS with Linux, Nginx, MySQL, and PHP from scratch has a real learning curve for most e-commerce operators.
Cloudways addresses that gap. Some context on its background: Cloudways was acquired by DigitalOcean in 2022 and currently operates as an independent brand — essentially a managed control panel layered over DigitalOcean, Vultr, Linode, AWS, and Google Cloud. You don't manage the underlying Linux environment. WordPress and WooCommerce deploy with a single click, free SSL is included, backups are automated, Cloudflare CDN integration is built in, Redis object caching and staging environments are available, and server resources can be scaled on demand. For an e-commerce store that can't afford extended technical downtime, it hits a practical middle ground.
Before Migration: Gather These First
Shopify admin access, domain management access, a Cloudways account, original product image files, the product CSV export, customer data, order data, and DNS management access — get all of this together before starting. If the Shopify account is already locked out, only what was previously exported can be recovered. Regardless of whether migration is being planned, regularly exporting Shopify data and keeping independent backups is something worth doing now, not after the fact.
Step One: Choose a Server
For a new store, a 2GB RAM configuration on DigitalOcean or Vultr High Frequency is typically adequate as a starting point. If daily order volume is already in the thousands, go directly to 4GB or above — saving on server cost at the expense of performance during high-traffic periods isn't a good trade. Choose a data center closest to the primary customer base: New York, Chicago, or San Francisco for US-heavy audiences; Frankfurt or London for Europe. Cloudways pricing changes frequently and varies across sources — check the current rates on Cloudways' official site before ordering, not any article's figures including this one.
Steps Two and Three: Deploy WordPress, Install WooCommerce
In the Cloudways dashboard, click Launch Server and select the WordPress + WooCommerce pre-configured image as the application type. Deployment completes within a few minutes, with no SSH or Linux command line required. If a plain WordPress image is used instead, install WooCommerce from the Plugins menu in the WordPress admin — both paths reach the same destination.
Step Four: Move Products From Shopify
Export from Shopify via Products → Export to get the CSV file. Import into WooCommerce via Products → Import. Title, SKU, price, categories, and inventory fields generally map across, but description formatting often needs manual cleanup. Review each product after import — check images, variant configurations, and categories — before going live. Discovering a variant with an incorrect price after launch is far more disruptive than catching it during review.
Step Five: Customer Data Migration
Same process: export from Shopify, import into WooCommerce, or use a customer import plugin. One thing customers must be told in advance: the password encryption methods are different between platforms. Migrated accounts cannot be accessed using the original passwords — customers will need to reset their password on first login. Prepare a notification email to send out on launch day to reduce confusion and support volume.
Step Six: Order Migration
Order data can technically be moved via CSV export and import, but if the goal is migrating products, categories, images, customers, and SEO URLs all together in one complete transfer, tools like Cart2Cart or LitExtension handle the cross-referencing work that manual migration can't do efficiently at scale. For stores with meaningful order history, a dedicated migration tool is the more practical choice.
Step Seven: Configure Payments
Installing the Stripe and PayPal plugins for WooCommerce covers most payment scenarios. One frequently missed point: if the Shopify store was using Shopify Payments, that payment channel is Shopify-exclusive and cannot transfer over. A new Stripe account or other gateway account needs to be applied for separately. After setup, run a complete test of the payment flow, refund process, and email notifications before going live.
Step Eight: Shipping Configuration
Set up shipping zones in WooCommerce → Shipping, organized by region (US, Europe, Asia, etc.), with rate rules for each. For dropshipping operations, connect the appropriate fulfillment plugin to maintain the existing fulfillment workflow.
Step Nine: Email Delivery — Don't Use PHP Mail
Order confirmations, shipping notifications, and other transactional emails sent through WordPress's default PHP mail function frequently get flagged as spam or fail to deliver entirely. Configure a dedicated SMTP service — Brevo, Amazon SES, Mailgun, or Resend are common choices. A typical wp-config.php configuration using a generic SMTP plugin looks roughly like this (specific constant names depend on the plugin you're using — consult that plugin's documentation):
// Add to wp-config.php — example using generic SMTP plugin constants
define('WPMS_ON', true);
define('WPMS_MAIL_FROM', '[email protected]');
define('WPMS_MAILER', 'smtp');
define('WPMS_SMTP_HOST', 'smtp-relay.brevo.com');
define('WPMS_SMTP_PORT', 587);
define('WPMS_SMTP_AUTH', true);
define('WPMS_SSL', 'tls');
Step Ten: SEO — Don't Lose Existing Rankings
Install Rank Math or a comparable SEO plugin and configure sitemap, robots.txt, meta titles, and schema. The genuinely critical task is preserving the existing Shopify URL structure where possible — paths like /products/iphone-case. Where the new site's URL structure can't be made identical, 301 redirects are essential to preserve accumulated search rankings and inbound link equity. A single Nginx redirect looks like this:
# Redirect old path to new path
location = /products/iphone-case {
return 301 /shop/iphone-case;
}
If there are many old URLs to redirect, build a mapping table of old-to-new URLs and handle them in batch rather than one at a time.
Step Eleven: Switch the Domain
Connect the domain in the Cloudways dashboard, then update the DNS A record at the domain registrar to the server IP Cloudways assigns. At least 24 hours before the planned switch, reduce the DNS TTL to around 300 seconds so that when the switch happens, DNS caches around the world refresh quickly, minimizing the window during which visitors still reach the old server.
Step Twelve: Pre-Launch and Post-Launch Checklist
Work through each of these before restoring ad spend: homepage, product pages, image display, payment flow, email notifications, SSL certificate, mobile responsiveness, Google Analytics 4, Search Console, sitemap submission, and 404 page handling. Don't run advertising while the site is still being tested.
After Migration: Avoiding the Same Scramble Next Time
The real lesson from a migration like this isn't "is Cloudways good" — it's "had a backup plan been in place all along?" The habits that prevent this situation from recurring: automated weekly website backups, regular product and order data exports, customer data kept in secure storage (in compliance with applicable privacy regulations), original product image files retained, consistent use of an independent domain rather than a platform subdomain, Google Analytics and Search Console history exported periodically, and Cloudways automated backups supplemented by a local copy as a second layer. With those in place, whether the next transition is a host change, a platform migration, or another account risk event, the data needed to rebuild quickly is always available — no starting over from zero.