Website migration checklist and risk guide for WordPress, Shopify, and custom sites

What a migration changes, and why risk shows up

For WordPress, Shopify, and custom builds, the same risk buckets apply. Search engines may lose crawl paths. Visitors may hit broken pages. Analytics may stop recording conversions correctly.

The main risks fall into four groups. SEO risk affects rankings, indexing, and traffic. UX risk affects page access and navigation. Tracking risk affects analytics, pixels, and events. Operational risk affects hosting, DNS, and handoff timing.

A good migration checklist reduces uncertainty before launch and gives a clear order of work. If you change URLs before mapping redirects, you create avoidable errors. If you forget tracking, you lose visibility right when you need it most.

A WordPress migration to a new theme may keep the same domain but still break templates and metadata. A Shopify migration may change collections, product URLs, or app behavior. A custom site can introduce more routing and API dependencies. In each case, the risk comes from changes in structure, not just appearance.

• List every migration change: domain, platform, hosting, URL structure, templates, content, and tracking.
• Group each change by risk type: SEO, UX, analytics, or operations.
• Assign one owner to each area: content, development, SEO, and launch.
• Freeze scope: decide what moves now and what waits.

Migration risk register

Build a four-column migration register before anyone touches code. Every major page type, tracking tag, and platform change should appear in it.

Pre-migration planning checklist

Planning prevents the most common migration mistakes. Start with inventory, then mapping, then approval. A practical plan covers every visible page and every invisible dependency: landing pages, blog posts, collections, products, forms, scripts, and backups. It also includes managed hosting access, maintenance access, and DNS.

For WordPress, inventory may include posts, pages, categories, and plugins. For Shopify, products, collections, navigation, and apps. For a custom site, routes, APIs, dashboards, and templates.

Once you have inventory, create a redirect map with old URLs and new URLs in one sheet. This is the core document for the migration. Do not skip backups or access checks. If you cannot log in to DNS, analytics, or hosting, you cannot fix problems quickly.

• Export the current page inventory: pages, posts, products, collections, landing pages, and forms.
• Note each page’s purpose: traffic driver, conversion, support, or informational.
• Create the redirect map: old URL, new URL, redirect type, and notes.
• Confirm access to registrar, DNS, hosting, analytics, search tools, and CMS admin.
• Back up site files and settings before launch.

Technical SEO checks before launch

Technical SEO keeps search engines and users on the right path. A page can look fine and still lose visibility if metadata, canonicals, redirects, or index controls break.

Start with URL structure. Keep important pages easy to find. Then verify metadata, headings, canonical tags, and robots settings. Check internal links too. A page with a correct redirect can still suffer if the new site links to the wrong destination internally.

For WordPress, watch plugin-driven changes: a theme switch may alter titles, headings, or page templates. For Shopify, check collection and product paths carefully. For custom sites, routing and rendered content need extra scrutiny because templates and APIs may control what search engines see.

The new site should preserve the intent of the old site. If a page used to target a specific topic, the new page should still support that purpose. If a page earned links or traffic, it needs a valid home. Pair this work with technical SEO and performance when templates change.

• Compare old and new URLs; keep key URLs stable where possible; map every changed URL to a redirect.
• Review index controls: pages that should index can index; pages that should not stay excluded.
• Check title tags, meta descriptions, heading structure, and canonicals.
• Audit navigation, footer, and in-content internal links.
• Verify structured paths for blog, collections, products, and service pages.

Launch-day validation checklist

Launch day needs speed and discipline. Confirm the site behaves correctly under real traffic. Catch broken redirects, missing scripts, and unexpected page errors before you scale promotion.

Run validation in a fixed order. First, verify the domain resolves to the new site. Next, test redirects from the most important old URLs. Then check the homepage, service pages, product pages, and forms. Finally, confirm analytics and conversion events.

If a form stops sending submissions, you need to know immediately. If tags fail, you still launch, but you lose measurement. That is why validation comes before promotion. A website maintenance and support process helps because launch day often reveals small issues under time pressure.

• Open the live domain: confirm DNS and homepage load.
• Test old-to-new redirects for blog, service, product, and landing pages.
• Test user actions: form submission, add to cart, checkout path, contact click.
• Check analytics tags, conversion events, paid ads tags, and pixel firing.
• Review visible errors: layout, images, navigation, and 404 pages.

Post-launch monitoring and fixes

Migration work does not end at launch. Search engines need time to recrawl. Users may still reach old URLs. Tracking can drift. Post-launch monitoring catches these issues while they are still small.

Monitor the pages that matter most: homepage, top landing pages, top product pages, and top blog posts. Check search visibility, crawl status, and broken links. Review analytics for sudden drops in sessions or conversions. Then inspect error pages and redirected paths.

A custom site may need extra review because APIs, dashboards, or dynamic content can fail in ways static pages do not. A Shopify store may need closer monitoring around collections, product templates, and apps. A WordPress site may need checks around plugins, caching, and page templates.

Compare old patterns with new ones. If one page type behaves differently, isolate that type first. Do not chase the whole site at once.

• Review indexing signals: pages indexed, crawl errors, and active redirects.
• Compare analytics before and after: sessions, conversions, landing pages, and referrals.
• Check priority pages daily at first.
• Log issues and fixes: broken redirects, missing tags, incorrect links, rendering issues.

Platform-specific risk notes

Each platform needs its own careful review. The checklist stays similar, but the risk surface changes.

Seven migration strategies

Choosing the right migration strategy balances downtime, SEO protection, and fallback options. Pick based on traffic, complexity, and business tolerance for change.

• Big bang: switch everything at once for a single, fast cutover.
• Phased rollout: migrate pages or sections incrementally to limit scope.
• Blue-green / parallel: run old and new sites simultaneously and flip traffic when stable.
• Hybrid: combine phased and parallel tactics to prioritize high-risk areas.
• Replatform / lift-and-shift: move infrastructure or CMS with minimal code changes for speed.
• Rebuild / refactor: redesign architecture during migration for longer-term performance and scalability.
• Content-first / SEO-first: migrate URLs, metadata, and redirects early to safeguard search rankings.

How to migrate without losing SEO

Begin with a pre-migration audit: crawl the site, export all URLs, identify top-performing pages and backlinks, and capture metadata and structured data. Create a detailed URL mapping and implement 301 redirects for every old-to-new path.

Preserve title tags, meta descriptions, canonical tags, XML sitemap, and robots.txt. Build and test on a staging environment. Validate mobile and page-speed performance. Verify internal links and structured data remain intact.

Use WordPress redirect plugins or server rules for Apache/Nginx, Shopify’s URL redirect tool for stores, and server-side redirects for custom sites. Deploy redirects and verify analytics and Search Console ownership before switching DNS. Monitor traffic, crawl errors, and index coverage after launch.

Expect brief rank volatility. With careful mapping, testing, and continuous monitoring, you protect organic visibility. For hands-on scope, see platform migration.

Troubleshooting guide

• If old pages still load, you probably missed a redirect: check the redirect map, then test the exact old URL.
• If traffic drops suddenly, check indexing and internal links: look for pages blocked from indexing, then confirm the new site links to the correct URLs.
• If conversions stop recording, test analytics tags and events on key pages, forms, and checkout paths.
• If product or service pages look wrong, check templates and theme files by page type, not only the homepage.
• If custom pages load with no data, inspect APIs and route logic separately from the visual layer.

Migration cheat sheet

One-line rule: if a page mattered before migration, it needs a verified home after migration.

• Before: inventory URLs and page types; build the redirect map; confirm hosting, DNS, analytics, and admin access; back up files and settings.
• Technical SEO: review titles and headings; confirm canonicals; check index settings; audit internal links; verify key page paths.
• Launch day: test the live domain, redirects, forms and conversions, analytics tags, and visible errors.
• After launch: monitor search and traffic; review top pages daily; log issues and fixes; re-test redirects and tracking; compare old and new page behavior.

What to do next

Start a URL inventory and redirect map today. That document is the migration.

If you are comparing stacks as part of the move, read Next.js vs WordPress for a service website or Shopify vs WooCommerce for growing product brands before you commit.

For redirect implementation, staging QA, and Search Console monitoring, see platform migration.

Request a free website audit on your current URL for a priority list before replatforming, or contact us with your timeline and platform targets.