Header Text - A Complete Website Migration Guide to Maintain SEO

Website migration is the process of moving a site from one environment to another, for example, changing Web Hosting providers, domain names, the CMS platform, or restructuring. Done correctly, it can improve performance, security, and visibility. If done wrong, it can harm search rankings, traffic, and revenue. This website migration guide provides step-by-step instructions on moving a website without losing SEO.

Quick Website Migration Checklist

  1. Plan your migration type and set up a staging environment.
  2. Perform a site audit: pages, URLs, links, crawl stats, and Core Web Vitals.
  3. Backup all files, databases, and media.
  4. Create a URL mapping sheet.
  5. Implement 301 redirects and update internal links.
  6. Apply noindex/robots.txt to your staging site and test links.
  7. Configure hosting and update DNS.
  8. Transfer files, database, and content.
  9. Remove noindex, add sitemap and redirects, verify SSL, and test.
  10. Monitor for errors, rankings, crawl stats, and traffic.

Migration Type Selector (Boxed section on WP)

Not all migrations are the same, so use this selector to find which one you need:

  • Hosting: Both the domain and content stay the same. You are moving the infrastructure on which your site runs. Select this if you have slow load times, frequent downtime, or if you have outgrown your current host. 
  • Domain Name: Your site’s address is changing due to rebranding, consolidating, or altering a domain that no longer fits your business.
  • CMS/Platform: You are moving your content to a new system, such as migrating to WordPress. Choose this if your current platform is limiting.
  • Redesign or Restructure: The site’s architecture is changing (new URL patterns, layouts, navigation, merged pages). Choose this if you are altering your site’s design or structure without switching hosting or domains.

KEY TAKEAWAYS

  • Migration types include hosting, domain name, CMS and structural and need different approaches.
  • Website migrations are done to improve performance, address platform limitations, or accommodate business/branding changes.
  • A website migration checklist reduces the risk of broken pages, lost rankings, and downtime.
  • Migrating a website involves moving files and databases, updating DNS settings and configuring hosting.
  • Following a launch day checklist helps ensure the website goes live with minimal disruption.
  • Post-launch monitoring helps identify problems early and ensures rankings recover quickly.
  • Most migration problems come from poor planning, missing redirects, or incomplete testing.

Types of Website Migration (& What Changes in Each)

Before you start planning, it’s important to understand the different types of migration.

Hosting Migration

Moving your website to a different web hosting provider is one of the most common migrations and involves transferring all your files, databases, and settings to a new server.

Domain Migration

When you transfer your domain or need to register a domain to match your business’s new branding or to consolidate multiple websites.

CMS/Platform

Switching from one CMS (Content Management System) to another, e.g., from Joomla to WordPress, changes the software your site runs on. Page structure and URLs may change, and plugins and custom code may need to be replaced.

Redesign/Structural

A structural migration involves changing your site’s information architecture to a new version, including new URL patterns, reorganized navigation, and merged or removed content.

Here’s a quick reference for each migration type:

Migration TypeWhat ChangesBiggest RiskMust-Do Step
HostingWebsite moves to a new hosting provider while the domain usually stays the same.Downtime, propagation delays, configuration issues that break functionality.Back up the entire site and test before updating DNS.
DomainWebsite moves to a new URL. Content and structure may stay the same.Loss of search rankings and traffic if redirects are not implemented correctly.Set up 301 redirects and notify search engines of the change.
CMS/PlatformSite moves from one CMS or platform to another.Broken pages, missing content, or URL structure changes that affect SEO.Map all URLs and confirm that content, metadata, and links transfer correctly.
Redesign/StructuralLayout, navigation, and page structure are redesigned, often with new internal URLs.Internal linking issues, missing pages, and authority loss.Create a full URL mapping and redirect plan before launch.
Website migration moves your site from one environment to another

When Should You Migrate? Common Reasons

Website migration is sometimes the only choice for businesses, so it’s worth understanding the most common reasons you should migrate:

  • Underperforming Hosting: Slow load times, frequent downtime, or inadequate server resources.
  • Scaling Traffic: If your business is expanding and your site is struggling to handle increased traffic.
  • Outdated Security Stack: Hosting that runs outdated software, has weak security features, or no regular malware scanning is an SEO and trust liability.
  • Rebranding or Domain Change: New branding or consolidating sites requires a domain migration.
  • CMS Upgrade: Moving to a more powerful or manageable platform (such as WordPress) for better tools, plugins, and control.
  • Ecommerce Reliability: Customers have zero tolerance for slow pages and checkouts. Migrating to a host optimized for ecommerce performance protects revenue and visibility.
  • Cost: If you are paying for features you don’t use or overpaying for performance you aren’t getting.
  • Redesign: A major redesign often changes URLs, navigation, and page structure, making migration essential to preserve SEO.

Website Migration Checklist (Pre-Launch)

Cutting corners in the pre-launch phase is the single biggest reason migrations can fail, leading to sites losing rankings, experiencing extended downtime, and having to start over.

Plan & Prepare

Good planning and preparation can prevent most problems and speed up the process with:

  • Migration Type:  Hosting, domain, CMS, or structural (see above).
  • Choosing Launch Window:  Schedule the migration during your lowest-traffic period.
  • A Rollback Plan: Know exactly how you will revert to a previous state if something goes wrong.
  • Staging Environment: An exact offline site copy to test all elements before going live.
  • Realistic Timeline:  A hosting migration can be done in a day. Domain or CMS migrations can take much longer, so plan accordingly.

Backups

Never start any migration without a working, full site backup stored in a separate location. If anything goes wrong, this is your safety net.

The backup must include:

  • Files: Everything in your root file and subdirectories.
  • Database: Export and store a clean copy of your entire database.
  • Content: Images, videos, documents, and any uploaded content.
  • Email: If your email is hosted on the same server, export all mailboxes.
  • Configurations: .htaccess, wp-config.php (WordPress Hosting), and any custom code, features and settings.

Always check backups to ensure everything is there and available as a restore point.

Audit Current Site

A site audit provides a baseline for comparison after the migration and helps find issues before they carry over to the new environment.

Minimum audit list:

  • Top Pages: Export from Google Analytics. These are your highest-value traffic pages; each needs a verified redirect if the URL changes.
  • Full URL crawl: Use Screaming Frog or Sitebulb to export every live URL.
  • Indexation Check: Use Google Search Console to see how many pages are indexed.
  • Existing 404s & Redirect Chains: Fix these so that broken links don’t transfer to the new environment.
  • Internal Link Map: Identify which pages link internally after the migration.
  • Core Web Vitals (CWV):  Note your current CWV scores via PageSpeed Insights to compare after migrating.

For larger sites or domain and CMS migrations, you can also include a backlink profile, structured data/schema markup, analytics and tags.

URL Mapping & Redirects

If you change any URLs, this is the most essential way to move a website without losing SEO.

Build a URL Mapping Sheet

A URL mapping sheet lists every old URL alongside its corresponding new one.

It should include the HTTP status of the old URL, page type, monthly traffic (first prioritize high-traffic pages), and a column to track whether redirects are completed and tested. For large sites, start with your top 20% of URLs by traffic, as these generate most organic visits.

Implement 301 Redirects

Implementing 301 redirects for migration informs search engines and browsers that a page has permanently moved and transfers link equity to the new URL.

To maintain SEO:

  • One Hop: Redirect chains (old – intermediate – final) reduce link equity and slow page loads. Map old URLs directly to their destination.
  • Closest Equivalent: Don’t redirect deleted pages to your homepage/landing page. Instead, find the closest one.
  • Implement in bulk: Add redirect rules to a CSV file and import it rather than adding them individually.

Redirects are not a permanent substitute for accurate internal links and add to page load time; redirect chains add even more.  After implementing, run a full site crawl to find any that still point to old URLs, then update them to point to the new ones and update your XML sitemap accordingly.

Test Redirects at Scale

Don’t assume your redirects are working. Use Screaming Frog or a bulk redirect checker to crawl and test old URLs and check response codes. Look for 301 (correct), 302 (should be 301), 404 (missed) and chains.

When NOT to redirect:

  • 404: For pages with no equivalent and minimal backlink value.
  • 410: Explicitly signal a page has been permanently removed.
  • Consolidate: Redirect near-duplicate pages to the strongest version of the content.

After launch, monitor Google Search Console for sudden spikes in 404 errors.

Moving to a new hosting provider can improve performance & rankings

Migration Steps

With prep done and redirects mapped, you are ready to start migrating. Here are the steps to migrate a website:

Move Files

Use an FTP (File Transfer Protocol) client such as FileZilla to transfer website files from the old server to the new one. Alternatively, you can use your control panel’s file manager.

For large sites, compress your files, download the zip file, then upload and extract on the new server. Take a file count to ensure everything has transferred correctly.

Move Database & Content

Use phpMyAdmin, your CMS’s export tool, or a migration plugin to export your database, content and user credentials. Import to the new server and add the new database name, username, and password to the config file.

If you’re changing domains, run a search-and-replace to update hardcoded URLs. Check all posts, pages, and content display correctly before moving on.

Update DNS

DNS settings point your domain to the new hosting server. You can update them by:

  1. Changing nameservers to point your domain to your new host’s servers; this is the simplest option.
  2. Updating the A record to change just the IP address your domain resolves to.

Propagation can take up to 24 hours; lowering TTL (Time to Live) speeds it up. To reduce downtime, lower your TTL to 300 seconds (five minutes) before migrating. After the changes are complete, restore the TTL to its previous setting.

Configure Hosting Environment

Your new hosting environment must be configured before going live. With cPanel Web Hosting, most of these settings are in your control panel:

  • PHP version: Set the PHP version your CMS requires. Running an outdated version can cause security and performance issues.
  • SSL Certificate: Install and activate your SSL certificate and confirm HTTPS encryption is enforced.
  • Caching: Configure caching (e.g. LiteSpeed Cache) and ensure CMS plugin settings are correct.
  • Security: Enable and configure your firewall and ensure that security features and plugins are active.
  • File Permissions: Set correct permissions: 644 for files, 755 for directories.
  • Email Routing: Confirm that MX records point to the correct mail server and haven’t been affected by DNS changes.

Launch Day Checklist

A launch day SEO website migration checklist helps ensure everything is working as it should before you go live.

  • Remove noindex tags from your live site.
  • Check robots.txt isn’t blocking search engine crawlers.
  • Confirm canonical tags point to the correct live site URLs (not staging).
  • XML sitemap loads correctly. Submit to Google Search Console and Bing Webmaster Tools.
  • Test redirects so every old URL returns a 301 to the correct new URL.
  • Check that the SSL certificate is active and valid, and there are no mixed content warnings.
  • Test forms, checkouts, and conversion tools.
  • Confirm analytics is firing, tracking is active, and events are recording correctly.
  • Check load times using PageSpeed Insights and compare against pre-migration speeds.

Post-Migration Monitoring

Post-migration monitoring during the first 30 days is when problems can be caught early, before they cause major SEO damage.

0 to 24 Hours: Monitor uptime and page speed. Check for 404 and 5xx (500, 502, 503) errors in GSC, confirm that DNS propagation is complete, and verify that your domain resolves correctly.

First Week: Monitor ranking movements (some fluctuation is normal) and indexed pages in GSC; the count should be much the same as the pre-migration count. Check your XML sitemap has been read, and pages are being indexed, and any crawl stats anomalies.

30 Days: Confirm organic traffic has stabilized. Clean up redirect chains (if any), then run a content parity check to confirm that all files and data have transferred correctly. Compare CWV scores against your pre-migration metrics.

Common Challenges & Fixes

Even when following a website migration guide, you might encounter problems. Here are the most common issues, and how to fix them:

Mixed Content After SSL

Your site loads over HTTPS, but the browser displays a “Not Secure” warning, which tells you that images, scripts, or stylesheets still load over HTTP. Run your site through a mixed content checker and update any HTTP URLs in your database/theme files to HTTPS.

Redirect Loops

A URL redirects indefinitely, with browsers showing the ERR_TOO_MANY_REDIRECTS error, usually means conflicting .htaccess rules and a plugin redirect.

Clear your browser cache and check the redirect chain using a tool like Redirect Checker. Review your .htaccess file and redirect rules for conflicts.

Staging Site Indexed

Your staging site gets indexed, causing duplicate content warnings or staging URLs appearing in search results when the noindex tag or robots.txt is incorrectly applied or removed prematurely.

Add a noindex, nofollow directive to robots.txt for all staging pages, submit a GSC removal request, and enable HTTP authentication for staging.

Missing or Broken Image Paths

Missing or broken images, or 404 errors, happen when absolute image paths point to the old domain or server.

Run a database search-and-replace to update old domain references and check your uploads directory to confirm that all media files were transferred correctly.

Broken Internal Links

Visitors or crawlers encounter 404 errors from internal links (despite redirects) because they still point to old URLs.

Run a post-migration crawl (Screaming Frog or similar) for 3xx responses and update links to point directly to the final URLs.

Lost Schema / Structured Data

Rich snippets disappear from search results after migration, indicating that schema markup wasn’t migrated correctly or that structured data contains old domain URLs.

Run Google’s Rich Results Test on key pages, re-implement schema if needed, and update any hardcoded domain references in your markup.

Migrate to Hosted.com®

If you’re migrating because your current host is letting you down (slow speeds, unreliable uptime, or no real security), Hosted.com® can solve the problem at the source.

You receive infrastructure with high-speed servers designed to keep your site loading quickly, with a 99.9% uptime guarantee.

The cPanelcontrol panel makes managing files, databases, email, DNS, and SSL certificates, simplifying every step of the migration process

If you’re using the WordPress CMS, our WordPress Hosting is designed for the platform’s specific performance and security needs and includes a free migration service.

Every hosting plan includes a free SSL preconfigured on the server and enterprise-grade security features, so your site is protected from day one.

Whether you need to register or transfer a domain to consolidate everything under one provider, Hosted.com® handles it all.

Our expert support team is on hand to help you with your migration from start to finish, including configuration and troubleshooting before, during, and after your move.

Quick, easy site and domain migrations with Hosted.com® [Learn More]

How to Choose the Best Web Hosting Plan for Your Site

VIDEO: How to Choose the Best Web Hosting Plan for Your Site

FAQS

What is website migration?

Website migration is the process of moving a site from one environment to another. This can include changing your hosting provider, domain name, CMS platform, or site structure to improve performance, security, or scalability without losing data, rankings, or traffic.

How do you migrate a website without losing SEO?

Audit your site before you start, map every old URL to its new equivalent, implement 301 redirects for all changed URLs, avoid redirect chains, update internal links, block your staging environment from indexing, submit your updated sitemap to Google Search Console on launch day, and monitor rankings, indexed pages, and 404 errors for at least 30 days post-migration.

How long does a website migration take?

A simple hosting migration may take a few hours, while complex migrations involving redesigns or CMS changes can take several days or weeks.

What’s on a website migration checklist?

A complete website migration checklist covers pre-migration audit, full backup, URL mapping, staging setup, redirect implementation, file and database transfer, DNS update, server configuration, SSL verification, launch day checks , and post-migration monitoring.

How long does DNS propagation take?

DNS propagation typically takes between one and 48 hours. To speed this up, lower your TTL (Time to Live) to 300 seconds at least 48 hours before your migration window. With a low TTL, most visitors will be directed to your new server within minutes of the DNS change.

Do I need to migrate my domain when I change hosting providers?

No. Changing hosting providers does not require a domain migration. Just update your DNS settings to point your existing domain at the new server. Changing a domain name is a separate process.

Other Blogs of Interest

Finding Web Hosting For Students

Web Hosting vs Cloud Hosting – How are They Different

Website Performance Optimization Techniques Through cPanel

Web Hosting Vs Website Builder – Key Differences

Web Hosting Statistics – The Latest Insights And Trends