The Ultimate Website Migration Checklist for a Safe and SEO-Friendly Site Transfer

Key highlights

• Follow this website migration checklist to plan a smooth site transfer with minimal downtime.
• Back up your website and test the new environment before going live.
• Choose a migration method that fits your platform, site complexity and technical resources.
• Use URL mapping and 301 redirects when URLs change to help preserve search visibility.
• Verify links, forms, mobile usability and page speed after launch.
• Check sitemaps, indexing settings and other SEO elements once the new site is live.
• Monitor traffic, rankings, conversions and security after migration.

Website migration is the process of moving a website, or a key part of it, to a new host, domain, platform or site structure. When planned and executed properly, migration can improve performance, scalability and user experience. However, even small oversights can result in broken links, downtime, indexing issues and lost organic traffic. 

That’s why a website migration checklist is useful. It gives you a structured way to plan the move, protect important pages and confirm that everything still works once the new site goes live.

This guide covers the practical steps to take before, during and after migration so you can protect your content, search visibility and website functionality.

In this guide, you’ll find:

• A clear, step-by-step site transfer checklist
• Pre- and post-migration tips to help protect SEO performance
• Best practices for maintaining site functionality during the move
• Tools and resources to support a smoother transition

Whether you’re changing hosts, domains, platforms or site structure, careful planning can reduce avoidable problems during the move.

What is website migration and why does it matter?

Website migration is the process of moving your entire website or significant parts of it to a new domain, server, platform or site structure.

The scope can range from changing hosting providers while keeping the same URLs to a larger domain, CMS or redesign migration that changes the site’s structure and URLs.

A successful migration keeps your website accessible while preserving important content, functionality and search signals. Without proper planning, a site move can cause ranking drops, broken links, data loss, indexing issues and downtime.

Common website migration scenarios

• Moving to a new domain: This often happens during a rebrand or domain-name change. Existing pages need to be mapped carefully to their new locations.
• Switching hosting providers: Moving to another host can improve speed, security or scalability while keeping most of the site unchanged.
• Redesigning or restructuring a website: Navigation, templates, content and URLs may change during a major redesign.
• Moving to a different CMS: Changing content management systems can affect URLs, metadata, media and site functionality.
• Migrating an eCommerce store: Product pages, category URLs, structured data and checkout functionality may all be affected.
• Migrating a large or enterprise site: Larger sites typically require more detailed URL mapping, testing and coordination.

Risks of migrating without a proper plan

• Ranking drops: Search engines may need time to process changed URLs and site signals. Incorrect redirects or indexing settings can make the problem worse.
• Broken links: Old or incorrectly mapped URLs can send visitors to 404 pages.
• Data loss: Without a full backup, content, media or database information may be lost.
• Downtime: DNS, server or configuration problems can temporarily make the site unavailable.
• Conversion problems: Forms, checkout flows or tracking can stop working even when the website appears visually correct.

Understanding what is changing before the move helps you determine which risks need the most attention.

Quick website migration checklist: 13 key steps

Having a clear checklist reduces the risk of missing an important technical, content or SEO task.

Use this website migration checklist as a high-level roadmap before moving into the detailed steps below.

Migration stage	Site transfer checklist
Pre-migration planning	1. Define the purpose and scope
	2. Choose the right hosting provider
	3. Benchmark current site performance
	4. Communicate with stakeholders
Pre-execution	5. Back up website files and databases
	6. Set up and test a staging environment
Migration	7. Choose the right migration method
	8. Update DNS and domain settings
	9. Configure website settings and SSL
Post-migration	10. Verify site functionality
	11. Implement and test redirects
	12. Verify SEO and indexing settings
	13. Monitor performance and security

Next, let’s walk through the essential pre-site migration steps to prepare your site and avoid the above common pitfalls.

Pre-website move checklist: Planning for success 

Before transferring files or changing DNS settings, define exactly what is changing and how you will validate the new site.

A little preparation can prevent much larger problems later.

1. Define the purpose and scope of migration

Start by clearly defining why you are moving the website.

You may be:

• Moving to a better hosting environment
• Changing domains
• Switching to a different CMS
• Redesigning the site
• Replatforming an online store
• Restructuring a larger website

Your reason for migrating determines the scope of your migration plan.

Document what will change, which pages are most important and who is responsible for each part of the move. If URLs will change, create an old-to-new URL map before migration begins.

Key considerations include:

• Maintaining critical website functionality throughout the move
• Keeping downtime as low as possible
• Identifying pages that generate significant traffic, backlinks or conversions
• Documenting URL changes and required redirects
• Planning changes to internal links, metadata and other important page elements
• Preparing a rollback or contingency plan if major issues appear

For larger migrations, assign clear owners for development, SEO, content, analytics and final launch validation.

2. Choose the right hosting platform

If you are moving to a new hosting provider, the new environment should be able to support both your current needs and future growth.

Key features to look for

• Speed and performance: Look for infrastructure, caching and CDN support suited to your site.
• Security: Check for SSL certificates, backups, malware protection and other security features.
• Scalability: Make sure your hosting environment can accommodate future traffic and resource requirements.
• Support: Reliable technical support can make migration troubleshooting easier.
• Migration options: Check whether the provider offers tools or assistance that fit your website.

Bluehost offers migration options designed to simplify the process for eligible websites.

Planning to move your website to Bluehost? Explore our hosting plans to start your journey.

3. Benchmark your current website

Before migrating, record your current website performance and SEO status.

This gives you a baseline for identifying meaningful changes after launch.

Useful tools include:

• Google Analytics for traffic, engagement and conversions
• Google Search Console for search performance, crawl issues and indexing
• Ahrefs for keyword rankings, backlinks and important organic pages
• Lighthouse or PageSpeed Insights for performance
• A website crawler for documenting URLs, metadata and internal links

Record:

• Organic traffic
• Top landing pages
• Keyword rankings
• Indexed URLs
• Important backlinks
• Conversion rates
• Lead or eCommerce activity
• Page speed and Core Web Vitals
• Existing crawl errors

If URLs will change, make sure pages with valuable backlinks, traffic or conversions are included in the redirect plan.

4. Communicate with stakeholders 

Make sure everyone involved understands the migration timeline, responsibilities and potential impact.

Depending on the site, that may include:

• Developers
• SEO teams
• Content teams
• Designers
• Analytics teams
• Customer support
• Sales or eCommerce teams
• Clients or customers

Schedule the migration during a lower-traffic period where practical.

If brief downtime is expected, notify users through appropriate channels such as email, social media or an on-site message.

For example:

“We’ll be migrating our website on [date and time]. You may experience brief interruptions while we complete the move.”

Once the plan, benchmarks and responsibilities are documented, you can move into technical preparation.

Pre-execution phase: Secure your website

Once you clear the pre-website migration checklist box, it’s time for the next step. This phase ensures that your data is protected and gives you a safe space to test your new setup without impacting your live site.

5. Create a full site backup

Create a complete backup of your website files and databases before starting the move.

Your backup should include:

• Website files
• Databases
• Media
• Configuration files
• Themes or templates
• Plugins or extensions where applicable
• Important custom code

Ways to back up your site

• Use your hosting provider’s backup system.
• Download files manually through cPanel or FTP.
• Export the database through a tool such as phpMyAdmin.

Store at least one copy separately from the hosting environment you are leaving.

Read more: 5 WordPress Website Backup Methods to Protect Your Site

6. Set up a staging environment 

A staging environment is a copy of your live site that allows you to test the migrated version without affecting visitors.

Use it to check:

• Page templates
• Navigation
• Forms
• eCommerce functionality
• URLs
• Redirects
• Internal links
• Analytics
• Mobile responsiveness
• Page performance

If the staging environment is publicly accessible, prevent it from being indexed by search engines.

Just as importantly, make sure temporary indexing restrictions are removed from the production site before launch.

Read more: How to Create a Staging WordPress Site

Once your site is backed up and the new environment has been tested, you can begin the actual transfer.

Website migration execution phase 

The execution phase is where you move the website to its new host, domain or platform.

Follow the plan created earlier so that files, data, URLs and important site functionality remain consistent wherever possible.

7. Choose the right migration method with Bluehost

The best method depends on your site’s platform, size, complexity and available technical resources.

Depending on your setup, migration options may include:

• A supported Bluehost migration tool
• cPanel migration
• A migration plugin
• Manual FTP and database transfer
• Assisted migration

Follow these steps during the transfer

1. Prepare your site: Remove unnecessary files or outdated components and confirm your backups are complete.
2. Choose the appropriate migration method: Select the approach that fits your platform and technical requirements.
3. Transfer files and databases: Move all required content, media, databases and configuration files.
4. Check file and database integrity: Confirm that content, images and database connections transferred correctly.
5. Review permissions and configuration: Check file permissions, credentials and server settings.
6. Test before changing DNS: Confirm that key pages, forms and database-driven functionality work in the new environment.
7. Compare the new site with your migration plan: Make sure important URLs and content have not been missed.

For more complex websites, a manual transfer can provide additional control. Standard websites may be easier to move with a supported migration tool.

Learn more with a clear step by step video to migrate your website

8. Update DNS and domain settings

Once your files and databases have been moved and tested, update your DNS settings so your domain points to the new hosting environment.

Typical steps

1. Confirm that the new production environment is ready.
2. Log in to the account managing your DNS.
3. Update the required nameserver or DNS records.
4. Verify that the domain resolves to the new server.
5. Monitor propagation and availability.

DNS changes can take time to propagate.

Where practical, keep the old hosting environment available during the transition so users and crawlers are less likely to encounter downtime.

9. Configure website settings and SSL

After the move, confirm that the production configuration matches your migration plan.

Check:

• Permalinks and URL structure: Make sure URLs follow the intended format.
• SSL certificate: Confirm the certificate is active and important pages load securely.
• HTTP-to-HTTPS redirects: Make sure insecure URLs redirect correctly.
• Mixed content: Update images, scripts or stylesheets that still use insecure URLs.
• Preferred site version: Confirm HTTPS and www/non-www versions are handled consistently.
• Site settings: Remove references to the previous server, domain or staging environment.
• Internal URLs: Check navigation and content for outdated links.

Read more: How to Get a Free SSL Certificate

Now that your website is successfully migrated and configured, it’s essential to optimize your site post-migration. The next phase focuses on verifying functionality, setting up redirects and monitoring your SEO performance to ensure a seamless user experience and maintain your search rankings.

Post-migration checks: SEO, performance and functionality

Completing the technical transfer does not mean the migration is finished.

Search engines still need to crawl and process the changes, while users need to reach the correct pages and complete important actions without errors.

10. Verify site functionality

Test the live website thoroughly.

Broken links and missing files

Crawl the site and look for:

• 404 errors
• Broken internal links
• Missing images
• Incorrect resource paths
• Broken scripts
• Pages linking to staging URLs

Fix critical issues as quickly as possible.

Navigation and interactive features

Test:

• Menus
• Search
• Forms
• Login areas
• Shopping carts
• Checkout
• Payment integrations
• Email signups
• Calls to action

A migration can be technically successful while still damaging conversions if these elements stop working.

Mobile responsiveness and performance

Check important templates on mobile and desktop.

Use PageSpeed Insights or Lighthouse to identify performance issues introduced during the move.

11. Implement and test 301 redirects

Redirects are essential when URLs change.

Create a clear mapping from each valuable old URL to the most relevant new destination.

Redirect best practices

• Use permanent redirects: Use 301 redirects or another appropriate permanent server-side redirect for pages that have permanently moved.
• Map URLs individually: Redirect old pages to their closest relevant replacements.
• Avoid sending everything to the homepage: This creates a poor user experience and can weaken the value of the redirect.
• Avoid redirect chains: Old URLs should point as directly as possible to their final destinations.
• Avoid redirect loops: Test redirects before and after launch.
• Update internal links: Internal links should point directly to the final URLs instead of relying on redirects.
• Prioritize important pages: Pay special attention to URLs with traffic, backlinks or conversions.
• Keep permanent redirects in place: Do not remove important migration redirects immediately after search engines discover the new URLs.

12. Update SEO and indexing elements

Review the technical SEO settings on the live site.

Meta titles and descriptions

Confirm that important pages retained their correct titles and descriptions.

Watch for default CMS values accidentally replacing optimized metadata.

Canonical tags

Make sure canonical tags reference the correct production URLs.

Look for:

• Old-domain canonicals
• Staging URLs
• Incorrect HTTP versions
• Canonicals pointing to redirected URLs

Internal links

Update important internal links so they point directly to the final URLs.

Pay particular attention to:

• Navigation
• Footer links
• Breadcrumbs
• High-authority content
• Important commercial pages

XML sitemap

Generate an updated sitemap containing your preferred URLs and submit it through the relevant webmaster tools.

Read more: How to Create a Sitemap

Robots.txt and indexing controls

Verify that important production pages are crawlable.

Look for temporary migration controls such as:

• noindex directives
• Blocked directories
• Staging restrictions
• Password protection
• Incorrect robots.txt rules

Google Search Console

Verify the correct site properties and monitor indexing after launch. If you have changed domains, follow the appropriate domain-move process and monitor both old and new properties during the transition.

Structured data

Validate important schema markup after migration, particularly where URLs or page templates have changed.

Hreflang

For international or multilingual websites, confirm that hreflang annotations point to the correct production URLs.

13. Monitor performance, conversions and security

Migration issues do not always appear immediately. Monitor the new site closely after launch.

Traffic and rankings

Track:

• Organic traffic
• Search impressions
• Clicks
• Keyword rankings
• Top landing pages
• Indexed URLs

Some fluctuation can happen after a significant site move. Use the benchmarks collected before launch to identify meaningful changes rather than reacting to normal day-to-day movement.

Conversions

Do not judge migration success on traffic alone.

Track:

• Lead submissions
• Signups
• Checkout completion
• Revenue
• Important CTA clicks
• Landing-page conversion rates

If traffic remains stable but conversions decline, investigate forms, checkout flows, page speed, CTA destinations and tracking before treating it as an SEO problem.

Site speed and uptime

Monitor availability, page speed and Core Web Vitals. A new hosting environment may behave differently from the previous one.

Security

Check:

• SSL certificates
• Malware scans
• User permissions
• Firewall settings
• Outdated components
• Unexpected file changes

User feedback

Ask customers and internal teams to report problems. Real users can uncover issues that automated testing misses.

Pro tip: Schedule post-migration reviews

Do not stop monitoring on launch day.

Schedule reviews approximately:

• Immediately after launch
• One week after migration
• One month after migration
• Three months after migration

Compare each review with your pre-migration benchmarks to identify genuine performance changes.

While you have the checklist in place, facing some technical errors can be common. Knowing how to troubleshoot the issues can keep you updated with your migrated website. 

Troubleshooting common website migration issues

Even with careful preparation, issues can appear after launch.

1. Broken links and missing pages

Issue: Visitors or search engines reach 404 pages.

Fix:

• Crawl the site using Screaming Frog, Ahrefs or a similar tool.
• Compare your old and new URL lists.
• Implement missing redirects.
• Update broken internal links.
• Monitor indexing reports for new errors.

2. Organic traffic or rankings drop after migration

Issue: Search visibility declines following the move.

Fix:

• Verify that important redirects point to the correct replacement pages.
• Check canonical tags.
• Confirm important pages are indexable.
• Look for accidental noindex directives or robots.txt blocks.
• Submit the updated XML sitemap.
• Compare migrated pages with the previous versions for missing content or metadata.
• Review internal linking to important pages.
• Monitor Search Console for URL-specific changes.

Avoid making large reactive changes based only on a few days of ranking movement.

3. SSL or HTTPS errors

Issue: The website displays security warnings or some resources do not load securely.

Fix:

• Confirm that the SSL certificate is active.
• Redirect HTTP URLs to HTTPS.
• Update internal links and resources to use HTTPS.
• Fix mixed-content errors.
• Verify HTTPS settings in your CMS and server configuration.

4. Website is inaccessible or showing old content

Issue: Visitors still see the previous website or cannot reach the new one.

Fix:

• Confirm DNS records.
• Check DNS propagation.
• Clear browser, application and server caches.
• Verify that the new server is responding correctly.
• Check file permissions and database connections.

5. Tracking and analytics are not working

Issue: Analytics stops recording traffic or conversions.

Fix:

• Confirm analytics and tag-manager scripts transferred correctly.
• Verify property and measurement IDs.
• Test important events and conversions.
• Check consent or cookie-management integrations.
• Use a debugging tool such as Google Tag Assistant.

6. Conversions fall even though traffic is stable

Issue: Your site continues to receive visitors, but fewer users submit forms, start checkout or complete other important actions.

Fix:

• Test forms, buttons, checkout and payment flows manually.
• Compare conversion rates by landing page before and after migration.
• Confirm analytics events are firing correctly.
• Check mobile usability and page speed.
• Review whether CTA copy, placement or destination URLs changed.
• Make sure important commercial pages remain easy to reach.

Addressing these issues early can help protect search performance, user experience and revenue after the move.

Final thoughts 

Migrating your website can be a simple and straightforward process. With careful planning, you can make the migration process smooth and stress-free. By following the steps outlined in this website migration checklist, you can minimize any negative impact on your organic search rankings. You can also ensure a good user experience while you transition. 

Bluehost helps streamline the migration process, so you don’t have to worry about missing any points from the checklist mentioned above. Our hosting service provides the best tools and features that together will ensure your lasting digital success. 

Boost your online presence and reach your business goals today with Bluehost.

FAQs