A WooCommerce store moves without downtime if the old host keeps running until the very end: you lower the TTL of the DNS records, copy files, database and email, test the copy on the new server through your hosts file, and switch the address only once everything works. The things that break most often are email, the object cache, the PHP version and duplicated cron jobs.
The rule: switch the address last
A zero-downtime migration means customers keep buying from the current host the whole time, while the new copy of the store is built alongside it. DNS records change only once the copy responds correctly. If something is wrong, the old server is still handling traffic and nobody loses anything.
Step by step
Lower the TTL of your domain records
A day or two in advance, set the TTL of the A, AAAA and MX records to 300 seconds. After the switch, the rest of the internet will reach the new server sooner.
List what is on the old account
Domains and subdomains, databases, mailboxes (and how many), cron jobs, the PHP version for each domain, certificates and rules in
.htaccess.Copy files and the database
Files over SSH (rsync) or via a panel backup, the database with
mysqldump. Check that the size and the number of tables match.Move email separately
Mailboxes usually live outside the site directory. Copy them over IMAP and compare the number of messages on both sides.
Pause cron on the new server
Otherwise the same jobs (emails, syncs, recurring payments) will run on two servers at once.
Test through the hosts file
Point the store’s domain at the new server’s IP address in your computer’s hosts file and walk the whole path: product, cart, checkout, admin.
Do a final sync and switch DNS
Copy the database once more (orders from the last few hours), change the DNS records, and switch cron on on the new server.
Check after the switch, then wait
Compare the site’s responses from both servers. Cancel the old hosting only after a few days without problems.
Five things that break most often
| Problem | Symptom | How to prevent it |
|---|---|---|
| Email left on the old server | Empty mailboxes or some accounts missing | Compare the number of mailboxes and messages before switching |
| Object cache points to the old address | The site works, but slowly | Recreate Redis and check the number of keys |
| Different PHP version or a missing extension | HTTP 403 or 500 with no message | Confirm the PHP version of every domain before switching |
| Cron runs on both servers | Duplicate emails and card charges | Pause cron on the new server until the switch |
| A script reports “all OK” | Accounts or large files missing | Compare the state of both servers, not the tool’s report |
Migrating to Aderlo Cloud
Aderlo Cloud moves your store for free on every plan, together with email and every message, following the procedure above. All it needs is access to your current hosting, or just the domain. The most recent move covered 406 accounts, 1,665 mailboxes and 610 databases in a single night; afterwards the team compared the responses of all 753 domains from the old and the new server.
How migration to Aderlo Cloud works →Frequently asked questions
- How long does it take to move a WooCommerce store?
- Copying a typical store takes anywhere from a quarter of an hour to a few hours, depending on the size of the files and the database. With testing and the TTL change, it is worth spreading the whole job over 2–3 days — and the store keeps selling throughout.
- Will I lose orders placed during the migration?
- Not if you do a final database sync just before changing DNS. Orders from the last few hours will then reach the new server.
- Does migration affect Google rankings?
- Not if page addresses, content and redirects stay the same and the new server responds as fast or faster. Only the server’s IP address changes.