Move work out of the live window
Backups, bulk file transfer, destination configuration and most testing should happen before maintenance begins.
← All tools
Free WordPress Tool
WordPress Migration Maintenance Window Planner
Estimate how cautious a production maintenance window should be from write activity, DNS, database sync and site type.
Free to useNo account requiredRuns in your browser
Planning result
Ready
Adjust the inputs to generate a planning recommendation.
Technical explanation
How to interpret this tool before a WordPress migration
A maintenance window is not the same thing as total migration time. Most data can be copied and tested in advance. The production window should contain only the operations that require controlling live writes, final synchronization, routing changes and verification.
Match the window to data volatility
A brochure site and an active store have very different tolerance for database drift during the final cutover.
Define exit criteria
Know which checks must pass before reopening the site and which failures trigger rollback rather than more live troubleshooting.
Practical questions
Does DNS TTL equal downtime?
No. TTL affects cache duration, but downtime is mainly controlled by how the old and new origins are handled.
Should WooCommerce be put in maintenance mode?
Often some form of write control is useful during the final sync, but the method depends on order volume and migration approach.
What belongs in a rollback plan?
Old origin availability, database state, DNS reversal steps, SSL status and a decision point for aborting the cutover.