A website migration can improve speed, usability, security, and conversion rates. It can also erase years of organic visibility and break lead tracking in a single launch if redirects, indexation, and forms are treated as afterthoughts. This website migration checklist is designed for businesses that need a better site without sacrificing the qualified leads, rankings, and revenue their current site already produces.
A migration is more than moving pages from one platform to another. It may involve a new domain, redesigned URLs, a platform change, HTTPS updates, a new navigation structure, or a full rebuild. Each change introduces risk. The right process starts with a clear baseline, protects high-value assets during the move, and verifies performance after launch.
Start With Business and SEO Baselines
Before anyone changes a template or publishes a staging site, document what the existing website contributes to the business. A migration should be measured against lead quality, sales, booked appointments, calls, and revenue where possible – not just whether the new design looks better.
Export historical organic traffic, keyword visibility, top landing pages, conversions, assisted conversions, and backlinks. Identify the pages that generate the most form submissions, phone calls, product sales, quote requests, and local discovery. For a California service company, that may include location pages, service pages, financing pages, and Google Business Profile landing pages. For an e-commerce brand, it may include category pages, best-selling product pages, and high-performing educational content.
Also record current technical conditions. Crawl the live site to capture URLs, page titles, meta descriptions, heading structure, canonical tags, status codes, internal links, image files, and indexability. This inventory becomes the reference point when diagnosing a traffic drop later. Without it, teams are left guessing whether a lost page was redirected, deleted, deindexed, or simply overlooked.
Define What Is Actually Changing
Migration scope determines the level of risk. A visual refresh on the same platform and URL structure is different from moving from WordPress to Shopify, consolidating multiple websites, changing domains, or reorganizing hundreds of service and blog pages.
Write down every planned change, including domain names, URL patterns, navigation, CMS, hosting, tracking tools, forms, checkout flow, language versions, and structured data. This creates accountability across developers, marketers, and leadership. It also prevents a common failure: an SEO team preparing redirects for one URL structure while developers publish a different one.
Website Migration Checklist Before Launch
The pre-launch phase is where most preventable losses are avoided. Do not treat staging as a visual approval environment only. It needs technical, marketing, and conversion testing.
First, map every meaningful old URL to its most relevant new destination. A one-to-one redirect is ideal when an equivalent page exists. If a page has been consolidated, redirect it to the closest category, service, or replacement page. Do not send every retired page to the homepage. That creates a poor visitor experience and can weaken the relevance signals search engines receive.
Use permanent 301 redirects for pages that have moved. Avoid redirect chains, where an old URL redirects through multiple intermediate pages before reaching the final destination. They slow crawling, waste processing, and make troubleshooting harder. Every redirect should lead directly to a live, relevant page that returns a 200 status code.
Before launch, verify these core areas:
- The staging site is blocked from search indexing through access controls or noindex settings, while the future live site is prepared to be crawlable.
- Every priority page has a final URL, unique title tag, relevant H1, descriptive meta description, and indexable status where appropriate.
- Canonical tags point to the preferred live URLs, not staging addresses, development paths, or retired pages.
- XML sitemaps include only final, indexable URLs, and the robots.txt file does not block essential pages, scripts, or resources.
- Structured data is retained or improved for relevant page types, such as local business, service, product, review, FAQ, and breadcrumb markup.
- Images are compressed, descriptive alt text is preserved where useful, and core templates are tested for mobile speed and usability.
Content deserves the same discipline. A redesign often trims copy to make pages feel cleaner, but removing service details, location relevance, comparison content, or trust signals can reduce rankings and conversion confidence. Shorter content can work when it is more focused, but it should not remove the information prospects and search engines use to understand what the business offers.
Protect Tracking and Lead Sources
A site that ranks well but cannot measure leads is still underperforming. Confirm that analytics, tag management, conversion tracking, call tracking, CRM integrations, paid advertising pixels, and consent settings are present on the staging environment and ready for production.
Test each meaningful conversion action. Submit every form, call every tracked number, request an appointment, complete a test purchase if applicable, and confirm that data reaches the intended platform. Check autoresponders, thank-you pages, calendar integrations, payment processing, and internal notification emails. A form that looks functional but fails to create a sales follow-up is a direct revenue leak.
Paid media needs special attention. Preserve landing-page relevance, final URLs, UTM handling, audience tags, and conversion actions before campaigns point to the new site. A migration that disrupts Google Ads tracking can distort bidding decisions and waste spend at the exact time the business needs clean performance data.
Launch Day: Control the Change
Launch during a period when the right people can monitor it. For many businesses, that means avoiding a major campaign period, a seasonal rush, or the evening before a holiday weekend. The best time depends on the business, but the team should have developer access, analytics access, and a defined escalation path.
As soon as the new website is live, crawl it again. Confirm that priority URLs load correctly, redirects work, canonical tags are correct, and noindex directives have been removed from pages meant to rank. Review the homepage, highest-value service pages, location pages, contact page, forms, checkout, login areas, and primary mobile templates manually.
Then submit the new XML sitemap through the relevant search platform and request indexing for the most valuable pages where appropriate. Do not expect rankings to remain perfectly still. Search engines need time to crawl redirects, process new URLs, and reassess content. The goal is not zero movement. The goal is to avoid preventable losses and quickly address real issues.
Monitor the First 30 Days After Migration
The first month is not a waiting period. It is a validation period. Review crawl errors, indexed page counts, redirect behavior, organic landing-page traffic, keyword movement, conversion volume, and form or call data frequently. Compare performance to the baseline, accounting for seasonality, promotions, and normal fluctuations.
Watch for 404 errors that indicate missed redirects, soft 404s where a page appears empty or irrelevant, unexpected noindex tags, duplicate pages, and pages that have dropped out of the index. Fix these issues at the source instead of applying temporary patches. For example, if internal links still point to old URLs, update the links rather than relying on redirects indefinitely.
Backlink recovery may also be necessary. High-authority websites will not always update their links immediately, but redirects should preserve value. Where a valuable partner, directory, publication, or supplier links to an obsolete page, request an update when practical. This is especially useful after a domain change.
Judge Results by Revenue Impact
A technically correct migration is only part of the outcome. The new site should also support stronger business performance. Review whether visitors can find core services faster, whether mobile users complete forms more easily, whether calls are being captured correctly, and whether key landing pages convert at the same rate or better than before.
If rankings remain stable but conversions fall, the problem may be page messaging, form friction, call-to-action placement, trust elements, or page speed. If conversions increase but tracking changes, make sure the improvement is real before using it to guide budget decisions. Clean measurement is what turns a migration from a design project into a growth decision.
A successful migration is not defined by a launch date. It is defined by whether the business retains its visibility, preserves its lead flow, and gives customers a clearer path to take action. Treat the move as a controlled performance project, and the new website can become a stronger foundation for sustainable growth.