Migrating a High-Traffic Site With a Maintenance Window

For most sites, a zero-downtime migration with no maintenance window is the right call. But for a high-traffic or e-commerce site where orders or submissions arrive constantly, a brief, planned maintenance window during the final cutover prevents data created between the backup and the switch from being lost. This guide explains when and how to use one.

The problem a maintenance window solves

A migration captures your site at the moment the backup is built. On a quiet site, nothing changes between backup and cutover. On a busy store, orders could be placed on the old site after the backup but before the switch — and those would be missing from the migrated copy. A short maintenance window freezes new activity during that gap.

When a window is worth it

• Active e-commerce where orders arrive continuously
• Sites accepting form submissions, bookings, or user-generated content non-stop
• Any site where losing even a few records between backup and cutover is unacceptable

Planning the window

1. Pick your lowest-traffic time from analytics
2. Lower your DNS TTL the day before for a fast cutover
3. At the window start, put the live site into maintenance mode (a ‘back shortly’ page)
4. Do a final migration so the backup captures the very latest data
5. Verify the migrated copy, then switch DNS to iWebVault
6. Take the site out of maintenance mode once it’s serving from iWebVault

Keeping the window short

The goal is the briefest possible freeze. Doing a first migration in advance (to surface any issues) and then a final, incremental migration during the window keeps it short — you’re only capturing the latest changes, not the whole site, at the critical moment. We can help structure this two-pass approach for a large store.

Communicating the window

Tell customers in advance if the window is during any active period: a brief notice that the site will be briefly unavailable for a planned upgrade at a specific time. For a store, schedule it when orders are lowest, and the impact is minimal.

Zero-downtime versus a maintenance window

For most sites, the zero-downtime approach — migrate, verify, switch DNS, never freeze the site — is ideal. The exception is a site where records are created continuously and losing any is unacceptable: an active store, a busy booking system, a high-volume form. For those, a brief, planned maintenance window during the final cutover closes the gap between the backup and the switch.

The gap a window closes

A migration captures your site as it was when the backup ran. On a busy store, an order placed on the old site after that backup but before cutover would be missing from the migrated copy. A short maintenance window stops new activity during that critical gap, so no record is created in limbo. It’s a small, deliberate pause to protect data integrity.

When a window is justified

• Continuous e-commerce orders
• Live bookings, reservations, or appointments
• Constant form submissions or user-generated content
• Any case where losing a few records between backup and cutover is unacceptable

Planning a tight window

1. Choose your lowest-traffic time from analytics
2. Lower DNS TTL the day before for a fast switch
3. Do a first migration in advance to surface any issues
4. At the window: enable maintenance mode, run a final incremental migration
5. Verify, switch DNS, then disable maintenance mode

Keeping it short with two passes

The trick to a brief window is the two-pass approach: a full migration ahead of time (no freeze), then a quick final pass during the window capturing only the latest changes. You’re not re-moving the whole site at the critical moment — just the recent delta — which keeps the freeze to minutes. For a large store, we can help structure this.

What’s next

• How to Migrate With Zero Downtime
• Migrating a WordPress Site
• Verifying a Migration Was Fully Successful

Still stuck? Our team can run or finish the migration for you — open a support ticket and we’ll take it from there.

Key takeaways

Busy or e-commerce sites benefit from a short maintenance window during the final cutover to avoid losing records created between the backup and the switch. Use a two-pass approach — a full migration in advance, then a quick incremental pass during a brief freeze at a low-traffic time — and test checkout and order emails immediately after going live on iWebVault. Static or quiet sites need no window.

Do all sites need a maintenance window?

No — most don’t. The standard zero-downtime flow loses nothing on a site where little changes between backup and cutover. A window is only worth it for sites with continuous critical activity (orders, bookings, submissions) where missing even a few records is unacceptable.

Common mistakes to avoid

• Adding a maintenance window for a site that doesn’t need one
• Making the window longer than necessary by re-migrating everything in it
• Skipping a test order after going live on iWebVault
• Scheduling the window during a busy period

For the rare site where every record counts, a short, well-planned maintenance window is the difference between a clean move and a handful of lost orders. Use the two-pass approach to keep the freeze to minutes, pick your quietest time, and always test checkout and order emails the moment you’re live — then even a busy store moves without losing a thing.