September 15, 2026 · By Randa Vandenack Schilling

The Complete Website Migration Checklist

A website migration is not one task. It is a coordinated move involving content, URLs, SEO signals, domains, analytics, forms, integrations, and the details visitors never notice unless something breaks. This checklist gives you a practical way to protect all of them.

If you are still deciding how to approach the move, start with Panderr’s complete website migration guide. If organic visibility is your biggest concern, also use our guide to migrating a website without losing SEO.

Before the migration

• Confirm who controls the domain registrar, DNS, hosting account, CMS, analytics, Search Console, business email, and other critical accounts.
• Crawl or inventory the current website and record every indexable URL.
• Identify high-value pages using organic traffic, backlinks, conversions, rankings, and business importance.
• Back up page copy, images, downloadable files, logos, brand assets, forms, structured data, and other content.
• Record current SEO titles, meta descriptions, canonical URLs, headings, robots directives, and schema where they matter.
• Export analytics benchmarks so post-launch performance has a meaningful baseline.
• Document forms, tracking scripts, CRM connections, scheduling tools, payment tools, maps, embeds, and third-party integrations.
• Decide which pages will be preserved, improved, redesigned, consolidated, or intentionally retired.

Build the URL map

URL preservation is one of the simplest ways to reduce migration risk. If a useful page can keep the same path, keep it. When a URL must change, map the old URL to the closest relevant new destination and prepare a permanent 301 redirect.

• Create an old-URL → new-URL spreadsheet or migration map.
• Avoid redirecting unrelated retired pages to the homepage.
• Check for legacy URLs that already redirect and avoid unnecessary redirect chains.
• Preserve important query-independent landing pages and location/service pages when appropriate.

Before launch

• Confirm every expected page exists on the new site.
• Compare important copy and assets against the original.
• Check navigation, internal links, buttons, forms, phone links, email links, downloads, and integrations.
• Verify page titles, descriptions, headings, canonical tags, structured data, and social-sharing metadata.
• Make sure production pages are not accidentally blocked by noindex or robots.txt.
• Generate and validate the production XML sitemap.
• Test the site on mobile and desktop.
• Check accessibility basics, including heading structure, labels, keyboard usability, contrast, and image alternatives.
• Test performance and obvious layout shifts or broken assets.
• Confirm analytics and conversion tracking are ready for production.

Launch day

• Take a final backup or snapshot of the old site before changing DNS or production routing.
• Publish the production site and verify HTTPS.
• Activate and test every required 301 redirect.
• Check the homepage and a representative sample of service, content, contact, and high-traffic pages.
• Submit a test form and verify that the message reaches the correct destination.
• Confirm analytics is receiving production traffic.
• Check canonical URLs and make sure they reference the correct production domain.
• Verify robots.txt and the XML sitemap on the live domain.

Immediately after launch

• Run a fresh crawl and look for 404s, broken internal links, redirect chains, missing metadata, and unexpected indexability changes.
• Use Google Search Console URL Inspection on important pages and request indexing where useful.
• Submit or resubmit the XML sitemap in Search Console.
• Watch Search Console for indexing, crawl, canonical, structured-data, and mobile issues.
• Check analytics for sudden traffic or conversion anomalies.
• Verify third-party services and integrations in their real production environment.

Monitor the migration

A successful launch is the beginning of migration monitoring, not the end. Over the following days and weeks, watch organic traffic, impressions, clicks, indexed pages, crawl errors, rankings, conversions, and server errors. Temporary fluctuations can happen while search engines recrawl a changed site, but unexplained losses should be investigated rather than simply accepted.

Do you need to redesign while you migrate?

No. Migration and redesign are separate decisions. Panderr offers three paths: Preserve retains the existing presentation as faithfully as possible; Improve preserves the source as an editable baseline for deliberate improvements; Panderr Redesign creates a new design direction from existing content and assets. That distinction can make a migration safer because change is intentional instead of automatic.

For businesses that would rather have someone manage the process, PeachSites’ guide to moving a business website to a new provider explains the provider side of the transition.

The simplest migration rule

Know what you have before you move it. Preserve what has value. Map every intentional change. Test before launch. Verify again after launch. A migration becomes much less intimidating when it is treated as a controlled transfer rather than a blind rebuild.