← Back to the blog

WordPress Migration Cost & Downtime Estimator

How Long Does a Website Migration Take? Timeline, Time by Task and Downtime

By Hamza IqbalFounder, ToolsForge

Reviewed 6 min readHow we source numbers

Moving truck carrying a server with a stopwatch

How long does a website migration take?

A managed website migration takes about 2–4 working days for a small WordPress site moving hosts, 4–11 days for a business site or a move from Wix or Squarespace, and 11–25 days for a WooCommerce store or custom site. The site itself is usually down for under 15 minutes, because the new site is built and tested on a staging copy while the old one stays live, and the switch is a DNS change.

Those timelines come from our migration cost estimator and count the whole project: setup, content, testing and cutover. A plain file-and-database copy is much faster. Kinsta, for example, says its migration team typically moves 8–10 sites per business day (checked November 2026). The extra days in a managed project go on checking, redirects and a planned switch.

Website migration timeline by site type

Move Project time (working days) Visitor-facing downtime
15-page WordPress site to a new host 2–4 Under 15 minutes
60-page WordPress site to a new host, 5,000 visitors a month 4–7 Under 15 minutes
10-page Squarespace site to WordPress 4–7 Under 15 minutes
40-page Wix site to WordPress, 5,000 visitors a month 6–11 Under 15 minutes
WooCommerce store with 1,000 products to a new host, 20,000 visitors a month 11–20 15–60 minutes with checkout paused
30-page Shopify store with 300 products to WooCommerce, 20,000 visitors a month 13–22 15–60 minutes with checkout paused
120-page custom site with integrations to WordPress, 20,000 visitors a month 14–25 A planned 1–3 hour window
1,000-page WordPress content site, 50,000 visitors a month 20–35 Under 15 minutes
DIY move with no staging copy Hours, if nothing breaks Hours, sometimes longer if errors occur

Project time scales with the size of the site. Downtime depends far more on how the switch is done.

How much time does each task add?

The estimator builds its timeline from the pieces below, then shows a range from 0.8× to 1.4× the total, because real projects vary.

Task or factor Working days the estimator adds
Base move from WordPress (setup, staging copy, QA, cutover) 3
Base move from Squarespace 5
Base move from Wix 6
Base move from Shopify 8
Base move from a custom platform 10
Content beyond the first 20 pages 1 per 50 pages
WooCommerce store setup, orders and payments 3
Products 1 per 200 products
Staged cutover for 1,000–10,000 monthly visitors 1
Staged cutover for 10,000–100,000 monthly visitors 2
Staged cutover for 100,000+ monthly visitors 4
Custom integrations (CRM, booking, APIs) 4

Example: a 60-page WordPress site with 5,000 visitors a month is 3 base days, plus 1 for the 40 extra pages, plus 1 for the traffic tier. That's 5 days, shown as 4–7.

For the SEO side, redirect mapping is part of the per-page time: each changed URL needs an old-to-new entry and a test after launch. A site that keeps its URLs skips most of that work.

What actually causes downtime during a migration?

Only the final cutover touches the live site. Everything before it happens on the new server.

DNS propagation isn't the same as your site being down

When you point your domain at a new server, each DNS resolver keeps its cached copy of the old record until the record's TTL expires. With a long TTL that can take most of a day; a short TTL set in advance cuts it to minutes. Your old site keeps serving visitors during that window, as long as you haven't shut it down.

The real site-down window is short

True downtime happens during the final step: copying the last database changes, updating configuration and switching DNS. For a straightforward WordPress site that's minutes. The unplanned problems (a wrong database connection, a missing plugin, broken permalinks) are what turn a 10-minute switch into a multi-hour scramble.

How to avoid downtime with staging and a DNS switch

  1. Build the new site on a staging URL on the new host, without touching the live site.
  2. Move the database and files to staging and fix any path or URL references there.
  3. Test everything on staging: forms, checkout, plugins and page speed, while the live site runs normally.
  4. Lower your DNS TTL a day or two ahead, so resolvers refresh their copy of your record sooner when you switch.
  5. Do a final content sync for anything published since the first transfer: posts, orders, comments.
  6. Switch DNS during a quiet period, and keep the old server untouched for a few days as a fallback.

What makes a migration take longer?

Custom plugins or code that need reconfiguring, large media libraries, WooCommerce order and inventory syncing, and integrations (payment gateways, CRMs, email tools) that need re-testing. If your site has several of these, add buffer time and rely on staging rather than a live-to-live transfer.

What if you can't avoid a longer downtime window?

A store with live inventory syncing may need a real maintenance window to avoid data conflicts. To limit the damage:

  1. Schedule it for your quietest period, based on your own analytics.
  2. Show a clear maintenance page instead of a raw server error.
  3. Tell customers in advance if checkout will be unavailable for more than a few minutes.
  4. Do all the pre-work before the window: transfers, configuration and testing.
  5. Set a time limit and a fallback plan, so you know in advance whether you'll roll back or keep troubleshooting.

Testing after cutover

Some visitors will still reach the old server until their resolver's cache expires, which produces scattered "it's still down" reports after the new site is live. Check from several networks and use a DNS propagation checker before you start troubleshooting. Then run the post-launch steps in the WordPress migration checklist, and see how much revenue you lose per minute of downtime if you're weighing a maintenance window.

FAQ

No. Propagation is how long resolvers take to pick up your new record as their cached copies expire. The old server keeps serving the site in the meantime, as long as it's still running.
Near-zero, yes, for most sites: staging, thorough testing and a final sync before the DNS switch. Stores with live transactions are harder; the estimator plans for 15–60 minutes with checkout paused.
Usually missing plugin dependencies, broken database connections, or permalink and URL mismatches found only after going live. Testing on staging catches most of them while the live site is unaffected.
Yes. A host-to-host WordPress move relocates the same installation; a move from Shopify or Wix means rebuilding content and structure. In the estimator, the base time is 3 days from WordPress against 6 from Wix and 8 from Shopify.

WordPress Migration Cost & Downtime Estimator

Estimate the cost and downtime of moving your site.

Run the free tool

Written by

Hamza Iqbal

Founder, ToolsForge

Founder of ToolsForge and a WordPress & WooCommerce developer. Builds the free calculators on this site and writes the guides behind them — every guide pairs real, sourced numbers with a tool so you can run your own.