
Most WordPress migration guides focus on the mechanics: export the database, tar the files, point the DNS. But the harder problem shows up three days after cutover, when a contact form stops working, a redirect vanishes, or your transactional email queue goes silent.
The issue isn’t usually the migration itself—it’s that you never recorded what was running before you flipped the switch. Here’s what to snapshot before you move hosts, so you can verify the new environment matches the old one (or debug when it doesn’t).
Active cron jobs and their schedules
WordPress runs scheduled tasks through WP-Cron: post publication, backup jobs, plugin update checks, and any custom automation you’ve layered in. Most operators assume these migrate automatically. They don’t always.
Before you move, install WP Crontrol (free plugin, checked November 2026 via WordPress.org) and export a list of every registered cron event. Note the hook name, recurrence interval, and next scheduled run time. Compare this list on the new host two hours after migration—missing or stalled cron jobs often explain silent failures in backup plugins, membership renewals, or scheduled email sends.
If your old host used server-level cron (some managed WordPress hosts replace WP-Cron with a true system cron for reliability), check whether the new host does the same. A switch from server cron back to WP-Cron can delay or skip tasks if traffic is low.
Email transport method and sending domain
WordPress sends email through wp_mail(), but how it sends—PHP mail, SMTP relay, or API—depends on server config and any SMTP plugins you’ve installed. If you’re using an SMTP plugin (WP Mail SMTP, Post SMTP, FluentSMTP), export its settings before migration. If you’re relying on server-default PHP mail, check your old host’s mail logs or send a test and inspect headers to see which MTA and sending IP it uses.
On the new host, verify that transactional email works and that SPF/DKIM records still align. If your old host sent from mail.oldhost.com and the new one sends from mail.newhost.com, your SPF record may need updating—or you’ll land in spam. For operators sending any volume of transactional mail (password resets, form notifications, order confirmations), this is the moment to switch to a dedicated service like Postmark rather than relying on server-default mail.
Redirect rules outside WordPress
If you’ve added redirects via .htaccess, nginx config, or your host’s control panel (cPanel redirects, Plesk forwarding rules), those won’t migrate with your WordPress files. Before you move, download your .htaccess file and screenshot any redirects configured in your hosting dashboard.
After migration, test a sample of your most-trafficked legacy URLs. A missing 301 can cost you search visibility and inbound referral traffic immediately. If your new host runs nginx instead of Apache, .htaccess rules won’t apply at all—you’ll need to translate them into nginx location blocks or use a plugin like Redirection to handle them at the application layer.
PHP version, memory limit, and execution timeouts
Even if both hosts claim to run PHP 8.2, the php.ini settings often differ. Before migration, check your current environment’s memory_limit, max_execution_time, and upload_max_filesize by installing the free PHP Info plugin or adding a temporary phpinfo() page.
If your old host allowed 512 MB memory and the new one defaults to 256 MB, resource-heavy plugins (page builders, import tools, backup generators) may fail silently or throw white-screen errors. Document your old limits and request matching (or higher) values from the new host’s support team before you migrate—most managed WordPress hosts will adjust these on request.
One thing to do the day after migration
Set a calendar reminder to revisit the site 24 hours post-migration and run through every user-facing form: contact forms, newsletter signups, checkout flows, login and password-reset flows. Test one of each. Silent breakage in form delivery or email notifications is the most common post-migration failure, and it only shows up when a real user (or you) tries the workflow.
If you’ve documented cron schedules, email transport, redirects, and PHP config before the move, you’ll have a reference to compare against—and you’ll spend minutes instead of hours figuring out what changed.
Want operator-focused deep dives like this in your inbox? Subscribe to One Two Three Send—one article daily, no fluff.
