A website migration is one of the highest-stakes projects a business can undertake. Whether you are moving to a new domain, switching CMS platforms, overhauling your site architecture, or redesigning from the ground up, the process introduces risk at every layer of your digital presence. Organic traffic that took years to build can evaporate in weeks if the migration is poorly planned. Backlinks that drive authority can break overnight. And the customer experience you have carefully refined can regress in ways that tank conversion rates before anyone notices.
The good news is that none of this is inevitable. A well-executed migration protects your search equity, preserves user experience, and often improves performance when approached with the right strategy. This guide walks through every phase of the process, from pre-migration planning through post-launch monitoring, so your business comes out stronger on the other side.
Why Businesses Migrate (and Why Timing Matters)
Organizations migrate websites for a range of strategic reasons: consolidating multiple properties under a single domain, upgrading from a legacy CMS that can no longer support modern functionality, rebranding after a merger or acquisition, or moving to a platform with better scalability and security. In e-commerce, platform migrations from Magento or WooCommerce to Shopify or BigCommerce have become especially common as merchants seek lower maintenance overhead and native performance advantages.
Timing is critical. Avoid launching a migration during your peak revenue season or immediately after a major algorithm update when search results are volatile. The ideal window is during a historically low-traffic period, giving your team room to troubleshoot issues before demand ramps back up.
Pre-Migration: Building Your Safety Net
The pre-migration phase is where most successful projects are won or lost. Start by creating a complete crawl of your existing site using tools like Screaming Frog or Sitebulb. Document every URL, its status code, canonical tag, meta title, meta description, and internal linking structure. This becomes your baseline — the dataset you will measure everything against after launch.
Next, export your full backlink profile from Ahrefs, Semrush, or Moz. Identify the pages receiving the most external links and ensure those URLs are accounted for in your redirect mapping. A single broken link to a high-authority page can cost you more ranking power than dozens of lower-tier pages combined.
Build your redirect map early and treat it as a living document. Every old URL should point to the most semantically equivalent page on the new site. Avoid redirect chains, never redirect everything to the homepage, and keep the map updated as the new site structure evolves during development.
Finally, benchmark your current performance metrics. Record your Google Search Console impressions, clicks, and average positions for your top 50 keywords. Export your Google Analytics traffic data, conversion rates, and revenue figures for the trailing 90 days. These numbers are what you will compare against to determine whether the migration succeeded.
Core Web Vitals and Page Speed: The SEO Factor Most Migrations Get Wrong
Here is where many migration projects stumble. Teams pour weeks into redirect mapping and content parity but completely overlook page performance. In 2026, Core Web Vitals are firmly embedded in Google’s ranking algorithm and function as a decisive tiebreaker when competing pages offer comparable content quality and authority. The three metrics that matter are Largest Contentful Paint (LCP), which measures how quickly your primary content loads; Interaction to Next Paint (INP), which evaluates responsiveness to user input; and Cumulative Layout Shift (CLS), which tracks visual stability as the page renders.
A migration that introduces heavier page templates, unoptimized images, or bloated JavaScript can push your Core Web Vitals scores from passing to failing — even if your content and URL structure are perfectly preserved. Research shows that pages loading within two seconds maintain bounce rates around nine percent, while pages taking five seconds see bounce rates climb to nearly 40 percent. For ecommerce sites, even 100 milliseconds of additional latency can measurably reduce sales.
Image optimization deserves special attention here. Images are typically the largest contributors to page weight and the primary culprits behind poor LCP scores. During a migration, images often get re-uploaded without compression, exported at incorrect dimensions, or converted to inefficient formats. This is a solvable problem.
Tools like Compresto make this process significantly easier. Compresto is a professional-grade compression application for macOS that handles images, videos, GIFs, and PDFs, reducing file sizes by up to 90 percent without perceptible quality loss. What makes it particularly useful during a migration is its batch processing capability — you can drag entire asset folders into the app and compress everything in a single pass. Its folder monitoring feature can also automate ongoing compression, ensuring that any new assets uploaded after launch are optimized before they ever reach a visitor’s browser. For teams running performance-sensitive migrations, building Compresto into the asset pipeline means one less thing that can silently degrade your Core Web Vitals after go-live.
Beyond images, audit your new site’s JavaScript and CSS delivery. Defer non-critical scripts, inline critical CSS, and verify that your hosting infrastructure supports modern caching and content delivery network (CDN) configurations. Run PageSpeed Insights and Lighthouse audits against your staging environment before launch — not after.
Launch Day: A Controlled Rollout
When launch day arrives, treat it as a controlled deployment rather than a single flip of a switch. If possible, use a staged rollout by migrating a subdirectory or subdomain first, monitoring performance for 48 to 72 hours, and then proceeding with the full site. This limits blast radius if something goes wrong.
On launch, immediately verify that your 301 redirects are firing correctly. Spot-check your highest-traffic and highest-authority URLs manually, then run a crawl against your old URL list to catch any 404 errors or redirect chains. Submit your updated XML sitemap to Google Search Console and request indexing on your most important pages.
If you are changing domains, file a Change of Address request in Search Console. This tells Google to transfer ranking signals from your old domain to the new one and accelerates the re-indexing process.
Post-Migration Monitoring: The First 90 Days
The 90 days following a migration are the most critical monitoring period. Expect some initial fluctuation in rankings — this is normal as Google recrawls and reassesses your site. However, you should be watching for patterns that indicate deeper problems.
Monitor Google Search Console daily during the first two weeks. Watch for spikes in crawl errors, drops in indexed page counts, or sudden declines in impressions for core keywords. If you see a keyword group losing visibility, investigate whether the corresponding pages are properly redirected, fully rendered, and returning 200 status codes.
Track your Core Web Vitals in Search Console’s experience report. Because this data is based on a rolling 28-day average of real user metrics, improvements and regressions surface gradually. If you compressed and optimized your assets pre-launch, you should see your scores hold steady or improve. If scores are declining, investigate which pages are failing and whether unoptimized images or heavy scripts are responsible.
Compare your organic traffic and conversion metrics against the 90-day baseline you established before the migration. Some temporary decline (10 to 20 percent) in the first few weeks is common and recoverable. A sustained decline beyond 30 days signals that something in your redirect strategy, content parity, or technical implementation needs immediate attention.
Common Migration Mistakes That Destroy Rankings
After managing and observing dozens of migrations, certain failure patterns appear consistently. Redirecting all old URLs to the homepage instead of mapping them to equivalent pages is perhaps the most damaging — it tells search engines that your old content no longer exists in any meaningful form, which wipes out the ranking authority those pages accumulated.
Another common error is neglecting internal links. Your redirect map may correctly handle inbound external links, but if the new site’s internal links still point to old URLs, you are creating unnecessary redirect hops that slow crawl efficiency and dilute link equity. Update all internal links to point directly to the new URL structure.
Launching without a robots.txt audit is another frequent mistake. Staging environments are typically blocked from crawling, and those directives sometimes carry over into production. A single disallow rule left in place can prevent Google from indexing your entire site.
Finally, ignoring mobile performance is a critical oversight. Google uses mobile-first indexing, meaning the mobile version of your site is what gets evaluated for rankings. If your new site looks great on desktop but loads slowly or shifts layout on mobile devices, your search visibility will suffer regardless of how well the desktop version performs.
Frequently Asked Questions
How long does it take for SEO to recover after a website migration?
Most well-executed migrations see traffic stabilize within four to eight weeks. Full recovery to pre-migration levels typically takes 60 to 90 days. If rankings have not recovered after 90 days, there is likely an underlying technical issue that needs to be addressed, such as broken redirects, missing content, or degraded page performance.
Do I need to notify Google when I migrate my website?
Yes. Submit your new XML sitemap through Google Search Console as soon as the migration goes live. If you are changing domains, also file a Change of Address request. These steps help Google discover your new site structure faster and transfer ranking signals from the old domain.
Will a website migration hurt my backlinks?
Not if you implement proper 301 redirects from every old URL to its equivalent new URL. A 301 redirect passes the vast majority of link equity to the destination page. The risk arises when URLs are left unmapped, redirected to the homepage, or routed through redirect chains that dilute authority.
How do Core Web Vitals affect my rankings during a migration?
Core Web Vitals are an active Google ranking factor. During a migration, changes to page templates, image assets, hosting infrastructure, and third-party scripts can all impact your LCP, INP, and CLS scores. If your new site delivers worse performance than the old one, you may see ranking declines even if your content and redirects are flawless. Compressing assets before launch using tools like Compresto, auditing JavaScript delivery, and testing on staging before going live are essential steps.
What is the best way to handle images during a site migration?
Export all image assets from the old site, compress them for web delivery using a dedicated tool, and upload the optimized versions to the new platform. Avoid re-uploading raw, uncompressed originals. Use modern formats like WebP or AVIF where your platform supports them, and ensure all images include proper width and height attributes to prevent layout shift.
Can I migrate my website in phases instead of all at once?
Absolutely, and this is often the safer approach. Phased migrations let you move one section at a time — for example, migrating your blog first, then your product pages, then your core landing pages. This limits risk and gives you time to catch and fix issues before they scale across the entire site.
The Bottom Line
A website migration does not have to be a ranking disaster. With thorough pre-migration documentation, airtight redirect mapping, proactive performance optimization, and disciplined post-launch monitoring, your business can preserve its search equity and come out with a faster, more capable digital presence. The organizations that treat migration as a cross-functional project — involving SEO, development, content, and design from day one — are the ones that consistently protect their traffic and accelerate growth on the other side.