Short answer: "The homepage loads" doesn't mean a migration worked. After moving a WooCommerce store to a new host, I found three problems that a visual check would never show: the page cache was switched off and its drop-in file was missing, an older version of a theme file had come back and undone security fixes, and the upload archive and database dump were still in the public folder. Check settings, file versions and leftover files, not just pages.
The setup
A Bangladeshi stationery store had just moved from cPanel shared hosting to Hostinger, with Cloudflare in front (the migration steps are here). Every page returned 200, checkout worked and test emails arrived. By most standards, the job was done.
I connected to the new server over SSH with WP-CLI and went through it properly. Here's what turned up.
Problem 1: The page cache was off
On the old host, W3 Total Cache's page cache had been switched on a few days earlier to stop a CPU suspension. On the new server:
pgcache.enabledwasfalsein the W3 Total Cache settings;- the URL and cookie exclusions for cart and checkout were gone;
wp-content/advanced-cache.php, the drop-in file that makes page caching work, didn't exist.
The most likely cause: the files used for the migration came from a copy taken before the cache was fixed, and the migration process didn't carry the drop-in over. Without it, every request ran PHP and MySQL again, which is exactly what had caused the suspension.
The fix:
- Copy W3 Total Cache's own drop-in into place:
cp wp-content/plugins/w3-total-cache/wp-content/advanced-cache.php wp-content/ - Re-add the exclusions (cart, checkout, my-account, order tracking, and the WooCommerce cart cookies).
- Turn the page cache on, let the plugin fix its
.htaccessrules, flush. - Test as an anonymous visitor, as a shopper with a cart, and on checkout. The details are in the WooCommerce cache guide.
A WP-CLI gotcha: W3 Total Cache's option set command with --type=array expects comma-separated values, not JSON. Passing a JSON array stored the brackets and quotes as part of each value. This works:
wp w3-total-cache option set pgcache.reject.cookie "woocommerce_items_in_cart,woocommerce_cart_hash,wp_woocommerce_session_" --type=array
Always read the value back with option get after setting it.
Problem 2: An old theme file came back
The site used a custom child theme. To be sure the server had the right code, I compared an MD5 hash of every theme file on the server with the files in my local source folder. Forty files matched. One didn't: functions.php.
The server had the version from before a security audit. It was missing two fixes: cleaning user input in a custom AJAX add-to-cart handler, and hiding the WordPress version from the page source. Nothing looked broken, which is the dangerous part: a regression like this can sit unnoticed for months.
The fix: back up the server copy, upload the correct file, run php -l on it before putting it in place, flush the cache and re-test.
The lesson: compare files, don't eyeball them. If your theme is in Git, check the deployed version against the commit. If not, a hash comparison takes one command on each side.
Full-funnel campaign management, from setup to scaling spend profitably.
Problem 3: Backups left in the public folder
The archive used to upload the site (over 2 GB, including wp-config.php with the database password) and the SQL dump (all customer data) were still in public_html, downloadable by anyone who guessed the name. Cloudflare had even cached a copy of the dump.
That one is serious enough to get its own post: backup files are the easiest way to leak a WordPress site.
Two host limits that changed my commands
Hostinger's shared servers disable PHP's proc_open() function. That breaks some WP-CLI commands that start other programs:
wp db exportfails. Usemysqldumpdirectly, with the credentials in a temporary option file (permissions600, deleted right after) so the password never appears on the command line.wp plugin deletefails. Deactivate the plugin, then call WordPress's owndelete_plugins()function throughwp eval.
Good to know before you need a quick backup in the middle of an update.
My post-migration checklist
I now run this on every move. It takes about 30 minutes.
URLs and access
-
siteurlandhomeare the live URLs (wp option get home) - the non-preferred domain redirects to the preferred one (root to
www, or the other way) - no temporary-domain URLs left in content or settings
- the hidden login page (if you use one) still works
Files and code
- WordPress core checksums verify (
wp core verify-checksums) - plugin checksums verify (
wp plugin verify-checksums --all) - custom theme files match your source (hash comparison)
- no
.zip,.tar,.gz,.sqlor.wpressfiles in the public folder
Performance
- page cache enabled and its drop-in present
- exclusions for cart, checkout and account pages in place
- three-state cache test passes (anonymous, shopper with cart, checkout)
Shop functions
- add to cart, cart, checkout and each payment method
- order emails send (test from the new server)
- scheduled tasks run (
wp cron event list)
Security and DNS
- SSL valid for every hostname, and Cloudflare on Full (strict)
- security plugin reads the visitor IP correctly behind Cloudflare
- old host kept for a week, then old DNS records cleaned up
FAQ
What should I check after migrating a WordPress site?
Beyond loading pages: correct site URLs, file integrity (core, plugin and theme), page cache status, checkout and emails, scheduled tasks, SSL, and leftover backup files in the public folder.
Why is my cache not working after migration?
Cache plugins rely on files outside their own folder, such as advanced-cache.php and .htaccess rules, and on settings stored in files. Migrations often skip or overwrite these. Re-save the cache settings or restore the drop-in, then test.
How do I know my theme files weren't changed during migration?
Compare file hashes between the server and your source, or compare against your Git repository. A quick md5sum on both sides shows any difference.
Why does wp db export fail on my host?
Some shared hosts disable PHP functions such as proc_open(), which WP-CLI uses to run mysqldump. Run mysqldump directly instead, using a protected option file for the credentials.
Found and fixed on a live Bangladeshi stationery e-commerce store, the day after its migration. If you've just moved hosts and want a second pair of eyes, see my web development service.
Clean, accurate tracking infrastructure that reports numbers you can trust.

