Post-migration smoke test:
Homepage
Key pages
Login/admin save
Media upload
Forms
Checkout/lead capture
Transactional email
Scheduled jobs
SSL redirects
Cache/CDN purge
Search for old domain
Analytics/Search Console
Do it before the team moves on.
Before any risky WordPress change, define rollback in concrete terms.
Not “we have backups.”
Which archive? Stored where? Restored how? Who can access it? How long will it take? What data will be lost if we roll back?
A rollback plan is specific or it is a wish.
A migrated WooCommerce site can look fine while Action Scheduler is stalled.
Pages load. Admin works. But renewals, webhooks, cleanup jobs, and emails stop running.
After migration, check pending/failed scheduled actions and confirm wp-cron or server cron is actually firing.
A backup folder with 400 old archives is not a strategy. It is delayed cleanup.
Good retention answers three questions:
How often do we back up?
How long do we keep copies?
How many restore points can we afford to store and test?
Backups need policy, not hoarding.