Which server-level jobs should I inventory?
Real cron entries may live in cPanel, Plesk, system crontabs or a hosting control panel rather than inside WordPress.
WordPress Cron & Scheduled Task Migration Planner
Score migration risk from WordPress cron jobs, WooCommerce scheduled actions and external server cron dependencies.
- Free, no sign-up
- Runs in your browser
- 100% private — runs in your browser
Planning result
Ready
Adjust the inputs to generate a planning recommendation.
Technical explanation
How do I interpret this tool before a WordPress migration?
Cron jobs are easy to overlook because they can keep working invisibly until a server move changes paths, PHP binaries, timing or network access. E-commerce, LMS, membership and integration-heavy WordPress sites can depend on background processing as much as front-end page loads.
How do I avoid duplicate cron execution?
If the old and new servers run the same jobs simultaneously during overlap, imports, emails or queue processing can duplicate.
Validate queues after cutover
WooCommerce Action Scheduler, webhooks, feeds and scheduled exports should be checked for failures or backlog after launch.
Practical questions
Does WordPress cron migrate with the database?
Scheduled events may, but server-level cron commands and hosting-panel jobs do not automatically move.
Can both servers run cron during DNS propagation?
Yes if not controlled, which can cause duplicate processing.
What should I record before moving?
Command, schedule, PHP path, working directory, environment variables, output handling and what business process the job supports.