Website migration is any significant change to where your website lives, what it runs on, or how its addresses are structured: moving to a new host, switching domains, changing platforms (say, Squarespace to WordPress), or reorganising URLs. If you are wondering what is website migration and why people treat it carefully, it is because these changes affect how search engines find your pages, how visitors reach them, and whether things like forms, email and tracking keep working.
Done well, a migration is invisible to visitors. Done badly, it can mean lost traffic, broken links and a few stressful weeks. This guide explains the types, the risks and how a migration is normally run.
What is website migration, in practice?
In plain terms, a migration is moving your site from a “before” state to an “after” state while keeping everything that matters intact: content, URLs (or redirects for them), search visibility, integrations and data.
What makes something a migration rather than a normal update is scale and risk. Editing a page is an update. Changing the server every page is served from, or the address every page lives at, is a migration. The test is simple: if something going wrong could take the whole site offline or change many URLs at once, treat it as a migration and plan it.
The main types of website migration
Most projects are one of these, or a combination. The combination is where the risk climbs.
Hosting migration
The site moves to a new server or hosting provider, but the domain, platform and URLs stay the same. This is the lowest-risk type for search, because from the outside nothing changes except the server that answers. The main risks are technical: missing files, database problems, email records lost when DNS moves, and downtime during the switch.
Domain migration
The site moves to a new domain name, for example after a rebrand or when consolidating several sites into one. Every URL changes, so every old URL needs a permanent redirect to its new equivalent. Search engines have to re-learn the site at its new address, which is why Google offers a Change of Address tool in Search Console for this case.
Platform migration
The site moves from one system to another: a website builder to WordPress, WordPress to Shopify, a custom build to a CMS. Content has to be exported, transformed and imported, templates rebuilt, and URLs often change because each platform structures them differently. Our walkthrough on migrating from Squarespace to WordPress shows what this looks like for one common move.
URL structure or architecture migration
The platform and domain stay the same, but page addresses change: merging sections, removing dates from blog URLs, renaming categories. This is easy to underestimate because “it’s just the same site”. Search engines see every changed URL as a new page until redirects tell them otherwise.
Protocol and subdomain changes
Moving from HTTP to HTTPS, from www to non-www, or from a subdomain into the main domain are smaller migrations of the same kind. They still need sitewide redirects and updated internal links.
Redesigns
A redesign on its own is not always a migration. It becomes one when it changes URLs, removes pages or changes how content is rendered. Many traffic drops blamed on “the redesign” are really unplanned URL changes and deleted content.
What can go wrong
Any honest answer to what is website migration includes what can break. Knowing the common failure points is most of the battle. These are the ones that cause the most damage:
- Missing redirects. Old URLs return 404 errors, so search results, backlinks and bookmarks lead nowhere.
- Redirects to the wrong place. Sending every old page to the home page instead of its closest equivalent. Google’s guidance specifically warns against redirecting many old URLs to one irrelevant page.
- Lost content. Pages, blog posts or text blocks that did not survive the export, often because the old platform’s export tool only covers some content types.
- Blocked new site. A “noindex” tag or a robots.txt block left over from the staging site.
- Broken tracking. Analytics, ad conversion tags or pixels missing on the new site, so you cannot even measure what happened.
- Email outage. DNS changes during a hosting or domain move that drop MX records, so email stops arriving.
- Broken forms and integrations. Contact forms, CRM connections, payment links and automations that pointed at the old system.
Google itself says to expect temporary ranking fluctuation during a site move, settling over time. The aim of good planning is not to avoid every bump, it is to make sure nothing preventable goes wrong.
The five phases of a well-run migration
Whatever the type, a migration follows roughly the same shape.
- Scope and plan. Decide exactly what is changing (host, domain, platform, URLs) and what is not. Agree on a launch window, ideally a quieter period for your business, and who signs off.
- Inventory and benchmark. List every URL on the current site, note which pages bring traffic, leads and links, and record current performance so you can compare later.
- Build and map. Build the new site on a staging copy, move content, and create a redirect map from every old URL that changes to its new home.
- Launch. Switch DNS or publish, put redirects live, remove staging blocks, submit new sitemaps and test the critical paths: forms, checkout, logins, tracking.
- Monitor and fix. Watch Search Console, analytics and error logs for the following weeks, fixing broken links and redirect gaps as they appear.
The detailed task list for each phase, particularly the search side, is in our SEO migration checklist.
Who should be involved
Migrations go wrong most often when one person assumes another has something covered. Even for a small business, name an owner for each of these:
- Decision maker: approves scope, launch date and go/no-go.
- Developer or host: builds and deploys the new site, handles servers and DNS.
- SEO owner: URL inventory, redirect map, metadata, Search Console.
- Content owner: checks that every page, post and asset moved correctly.
- Marketing or ops owner: tracking, forms, CRM, email and ad platforms.
On a small team, one person may wear three of these hats. That is fine, as long as the list exists and nothing on it is unowned.
Signs you actually need a migration
People migrate for good reasons and bad ones. Good reasons include:
- Your host is slow, unreliable or not giving you the support you need.
- Your platform cannot do what the business now needs, such as a store, memberships or deeper SEO control.
- You are rebranding, or consolidating several sites into one stronger domain.
- Your URL structure is messy enough that it actively confuses visitors and search engines.
Weak reasons include wanting a fresh look (which can usually be done without changing URLs or platforms) or chasing a new platform because it is fashionable. Each migration carries risk, so make sure the benefit is clear before you start.
How to lower the risk
A few principles cut the risk of almost any migration:
- Change one thing at a time where you can. Moving host first and changing platform later is safer than both at once.
- Keep URLs the same wherever the new setup allows it.
- Back up everything before you start: files, database, DNS records, and an export of your content.
- Keep the old site available until you are sure the new one is complete.
- Test on staging before launch, with search engines blocked from the staging copy.
- Keep redirects in place long term. Google recommends keeping them for at least a year, and keeping them indefinitely is reasonable.
If you want someone to plan and run the whole thing, from URL inventory to post-launch monitoring, our website migration team can take it on. Email support@growthscribe.com with what you are moving and where.
FAQ
What is website migration in simple terms?
It is moving your website to a new home or a new setup: a different host, domain, platform or URL structure. The goal is to change what needs changing while keeping content, search visibility, links and integrations working.
Does a website migration hurt SEO?
It can if redirects, content or technical settings are mishandled. Even a well-run move may cause temporary ranking fluctuation while search engines process the changes, which Google describes as normal. Careful planning, complete redirects and monitoring keep that disruption to a minimum.
How long does a website migration take?
It depends on the type and size of the site. A simple hosting move for a small site is far quicker than a platform change with hundreds of pages and a new URL structure. Planning, building and testing usually take longer than the launch itself, and monitoring continues for weeks afterward.
Is changing web hosts a website migration?
Yes. A hosting move is the simplest type, because the domain and URLs stay the same. It still needs a full backup, careful DNS changes that preserve email records, and testing before and after the switch.
