How Long to Do Website Migration?
A website migration can take anywhere from a few days to several months. That range is not vague; it reflects genuinely different scopes of work. Moving a 20-page site to a new host is a weekend job. Rebuilding a 50,000-product ecommerce store on a new CMS while preserving two years of SEO equity is a four-to-six-month project. The timeline depends on migration type, website size, technical complexity, and how seriously you take SEO. Get those four things clear before you set a launch date. Estimate Your Migration Timeline Based On Migration Type Different migrations require vastly different amounts of work. The first mistake most businesses make is treating all migrations the same. Here is a realistic breakdown by migration type: Domain migration (e.g., rebranding from old-domain.com to new-domain.com): 2 to 6 weeks for a site under 500 pages. The technical work is mostly redirect mapping and DNS cutover. The timeline stretches when there are thousands of inbound links that need redirecting or when the old domain carries significant authority you cannot afford to lose. CMS migration (e.g., moving from WordPress to Webflow, or Joomla to WordPress): 4 to 12 weeks. You are rebuilding templates, migrating content, and replicating functionality. Every custom plugin or feature you relied on needs an equivalent on the new platform. Hosting migration (moving servers without changing the site): 1 to 5 days if executed cleanly. This is the simplest migration type, but it still breaks things when DNS propagation causes downtime, or SSL certificates do not transfer correctly. Full redesign migration (new design, new structure, same or new CMS): 2 to 6 months. The scope expands because you are making URL structure changes, information architecture changes, and design changes simultaneously. Each one creates a new SEO risk. E-commerce migration: 3 to 9 months for large stores. You are migrating products, variants, pricing, customer accounts, order history, payment integrations, and tax configurations. Most e-commerce platforms handle data exports differently, which adds translation work at every step. Complete Pre-Migration Planning Before Touching The Website Most migration delays originate during planning failures, not execution failures. Teams that skip or rush the planning phase consistently end up extending their go-live date by weeks. Pre-migration planning includes five things that are not optional: URL mapping: Document every existing URL and where it will live after migration. For a site with 1,000 pages, this is a spreadsheet project. For a site with 100,000 pages, it requires a crawler and a systematic approach. Missing a URL here means a broken redirect post-launch. Redirect strategy: 301 redirects tell Google where your content has moved. Every page that changes URL needs one. Redirect chains (A redirects to B, which redirects to C) bleed PageRank and slow load times. Map redirects directly from the old URL to the new URL. Analytics backups: Export your Google Analytics historical data before you change anything. After migration, your tracking setup may change, and you will want historical benchmarks to measure recovery against. Crawl inventory: Run a full crawl of the existing site using Screaming Frog or Sitebulb before you touch anything. This gives you a baseline of all pages, their current rankings, their incoming internal links, and their indexed status. You cannot protect what you have not catalogued. Stakeholder approvals: Migrations often stall because someone who had sign-off authority was not consulted during planning. Legal needs to approve the new terms pages. The product owns certain feature pages. Finance has input on pricing structures. Get everyone into the planning phase, not the review phase. Migrate Content, Assets, And Technical Infrastructure Execution time depends largely on site size and technical complexity. A clean migration on a small site is three to five days of work. A messy migration on a large site with legacy technical debt can stretch into months. Here is what execution actually covers: Content migration: Moving page copy, metadata, headings, and structured content from the old platform to the new one. This is manual work when platforms do not have compatible export formats. For 500+ pages, expect to dedicate multiple team members. Media migration: Images, PDFs, video embeds, and downloadable files all have URLs that need to transfer cleanly. Broken image URLs cost you both user experience and SEO. Rename files before migration, not after. Database migration: Most CMS platforms store content in a database. Migrating the database means exporting it from the old environment, transforming it into the format the new environment expects, and importing it without corrupting relational data. E-commerce products: Each product needs its attributes, images, pricing, inventory status, variants, and SEO fields migrated. If you have 10,000 SKUs and each one needs manual review, that is weeks of work. Automated migration tools exist, but rarely produce clean results without human review. Integrations: CRM connections, email marketing platforms, live chat tools, payment gateways, review platforms, and analytics tracking all need to be reconnected and tested in the new environment. Test Everything Before Launch Day Testing prevents expensive post-launch issues. A migration that launches with broken redirects, missing tracking, or non-functional checkout flows can cause immediate revenue losses and SEO setbacks that take months to recover from. Run this before you flip the switch: Redirect testing: Crawl the staging site and confirm every old URL returns a 301 to the correct new URL. Check that no redirect chains exist. Spot-check the highest-traffic pages manually. Internal links: Crawl for internal links pointing to old URLs. Update them to point directly to the new URLs. Internal links that pass through redirects are wasted equity. Forms: Submit every form on the site, including contact forms, quote request forms, newsletter signups, and checkout flows. Confirm submissions are arriving in the correct place and triggering the correct automations. E-commerce flows: Run a test transaction through every payment method you support. Check that order confirmation emails are sent, inventory decrements are correct, and receipts display the right information. Tracking setup: Confirm Google Analytics is firing on every page. Confirm Google Tag Manager tags are loading. Confirm conversion events are recording
