Website migration can be exciting. You may be moving to a faster platform, redesigning your website, changing your domain, or upgrading your CMS.
But migration is also one of the easiest ways to accidentally lose organic traffic.
A page can disappear from search results. URLs can change without redirects. Important content can be removed. Tracking can stop working. Even small technical mistakes can create problems after launch.
The good news is that most migration problems are preventable.
A structured website migration checklist can help you move your website while protecting its SEO, content, performance, and functionality.
What Is a Website Migration?
A website migration is any major change that affects your website's structure, technology, URLs, domain, hosting, or content.
Common examples include:
- Moving from one CMS to another
- Changing your domain name
- Redesigning a website
- Moving to a new hosting provider
- Switching from HTTP to HTTPS
- Changing URL structures
- Moving from one eCommerce platform to another
- Combining multiple websites
- Rebuilding a website with a new technology stack
Not every migration involves every category, but the bigger the change, the more carefully it should be planned.
1. Crawl Your Existing Website First
Before changing anything, create a clear picture of your current website.
You should know:
- Which pages currently exist
- Which pages receive organic traffic
- Which pages generate leads or sales
- Which URLs have backlinks
- Current title tags and meta descriptions
- Existing redirects
- Internal links
- XML sitemap URLs
- Important images and media
- Analytics and tracking setup
This gives you a baseline to compare against after migration.
A website crawl can also identify broken links, duplicate pages, missing metadata, and other technical issues before you start rebuilding.
2. Create a URL Mapping Document
One of the most important parts of a migration is understanding what happens to existing URLs.
Create a spreadsheet containing:
Old URLNew URLRedirect
/old-service
/services
301
/about-us
/about
301
/blog/old-post
/blog/new-post
301
Every important old URL should have a clear destination.
If the URL remains unchanged, you don't need to redirect it.
If the URL changes, map it to the most relevant new page.
Avoid redirecting every old page to the homepage simply because it's convenient. The destination should make sense for the original page.
3. Protect Your Important Content
A redesign is often an opportunity to clean up content.
But don't remove valuable pages without checking their performance first.
Before deleting content, look at:
- Organic traffic
- Search visibility
- Backlinks
- Leads or conversions
- Internal links
- Business importance
A page that looks outdated may still bring valuable visitors.
If content needs improvement, consider updating it rather than deleting it.
4. Set Up 301 Redirects
If your URLs change, redirects tell browsers and search engines where the content has moved.
Use 301 redirects for permanent URL changes.
For example:
example.com/old-page
can redirect to:
example.com/new-page
Avoid creating unnecessary redirect chains.
For example:
Old URL → Temporary URL → New URL
is less efficient than:
Old URL → New URL
Your goal should be a direct redirect whenever possible.
5. Check Your Internal Links
Website migrations can leave hundreds of internal links pointing to old URLs.
Review:
- Navigation menus
- Footer links
- Blog links
- Service pages
- Breadcrumbs
- Related content
- Buttons
- Image links
Update internal links so they point directly to the new URLs.
Don't rely entirely on redirects for internal navigation.
6. Check Technical SEO
Before launch, review the technical foundation of the new website.
Check:
- Robots.txt
- XML sitemap
- Canonical tags
- Meta robots directives
- Title tags
- Meta descriptions
- Heading structure
- Structured data
- 404 pages
- HTTPS
- Mobile responsiveness
One particularly important mistake is accidentally leaving a development site's noindex directive enabled after launch.
The website may look perfect to visitors while search engines are being told not to index it.
7. Test the Staging Website
Before going live, test the new website thoroughly.
Check:
- Forms
- Contact details
- Navigation
- Search
- Checkout
- Login functionality
- CTAs
- Mobile layouts
- Images
- Videos
- Third-party integrations
- Analytics
- Cookie tools
Don't only test the homepage.
Visit important pages individually and test the actions that matter to your business.
8. Check Website Speed
A migration shouldn't create a performance regression.
Compare the old and new websites for:
- Largest Contentful Paint
- Interaction to Next Paint
- Cumulative Layout Shift
- Image sizes
- JavaScript
- CSS
- Font loading
- Server response time
- Mobile performance
A beautiful redesign that becomes significantly slower can create a poor user experience.
Performance should be tested before launch and again after launch.
9. Verify Analytics and Tracking
Your migration can also break your measurement setup.
Check that:
- Google Analytics is working
- Google Search Console is connected
- Conversion tracking works
- Form submissions are recorded
- eCommerce tracking works where applicable
- Advertising pixels are installed
- Events are firing correctly
If tracking breaks during migration, you may lose important business data even if the website itself appears to work.
10. Submit the New Sitemap
After launch, make sure your XML sitemap contains the correct canonical URLs.
Submit the sitemap through your search engine tools and monitor indexing.
Don't assume that everything has been indexed simply because the website is live.
Check important pages individually and monitor the website over the following days and weeks.
11. Monitor the Website After Launch
The migration isn't finished when the new website goes live.
For the first few weeks, monitor:
- Organic traffic
- Search impressions
- Indexed pages
- 404 errors
- Redirect errors
- Rankings
- Conversions
- Page speed
- Server errors
- Crawl issues
Compare these numbers with your pre-migration baseline.
If something drops unexpectedly, investigate quickly.
Website Migration Checklist
Before launching, make sure you've completed the following:
Final Thoughts
A website migration shouldn't be treated as simply moving files from one platform to another.
It's a combination of development, SEO, content, analytics, performance, and quality assurance.
The safest approach is to document what exists before the migration, map important URLs, test everything before launch, and monitor the website after it goes live.
With the right process, you can modernize your website without unnecessarily sacrificing the visibility and traffic you've already built.
Need help planning a website migration? LaunchNest can help with development, technical SEO, QA, performance, and post-launch support.