What is the difference between a website migration and a rebuild?

A migration moves an existing site, its content and ideally its design and URLs, to a new platform or host. A rebuild redesigns or restructures the site, usually with new templates, new content structure or both. Many projects are a mix of the two.

Is moving from WordPress to Shopify a migration or a rebuild?

It is usually both. Products, pages and URLs can be migrated, but the theme and templates normally need to be rebuilt for the new platform. The scope depends on how much of the design must change.

Which option carries more SEO risk?

Whichever changes more URLs and content. A rebuild that restructures the site carries more risk than a like-for-like migration, but either can go wrong without a redirect plan and post-launch checks.

How do I know whether my current design is worth keeping?

Look at whether it supports your current goals, whether it works well on mobile and for keyboard users, and whether the templates are maintainable. If the design works and the platform is the problem, migrate. If the design and structure are both holding the business back, rebuild.

CMS Migration or Full Rebuild: How to Tell Which You Need

When a website is painful to run, people often say they need a rebuild. Sometimes that is true. Often the real problem is the platform, the hosting or the way content is stored, and the design is fine. In that case the right project is a migration. Choosing wrongly means paying for work you did not need or keeping a site that still does not work.

Four questions that decide it

1. Is the problem the platform, or what is on it?

Slow editing, plugin conflicts, unreliable hosting and security worries are platform problems. Unclear messaging, confusing navigation and poor conversion are site problems. Platform problems point toward migration. Site problems point toward a rebuild.

2. Would you keep the current design if you could?

If visitors and staff are happy with how the site looks and works, rebuilding its design from scratch is expensive. If the design is dated, inaccessible or inconsistent, a migration will only move those problems to a new place.

3. How much of the content is worth keeping?

A site with years of strong content may justify a careful migration. A site full of outdated pages may need an audit and clean-out, which is a rebuild decision in disguise. A content inventory answers this faster than a debate does.

4. How much search visibility are you protecting?

If the site already earns meaningful visits, URLs and content structure are assets. A migration that keeps them intact is the lower-risk path. A rebuild is still possible, but needs a full redirect and launch plan.

What each project usually involves

Migration: moving content, media and data, recreating templates on the new platform as closely as practical, keeping URLs where possible, connecting forms and integrations, testing, switching DNS and monitoring. Email and DNS dependencies are common hidden risks.

Rebuild: research, new structure, new design, new templates, new copy where needed, development, content migration, redirects, accessibility and performance testing, launch and monitoring.

Both: a platform change with a redesign is the largest option. Splitting it into two stages often reduces risk, because you can confirm the new platform is stable before changing the design.

Common situations

WordPress site with plugin and speed problems: often a cleanup or migration to better hosting first, then a decision about design.
Moving from WordPress to Shopify or the reverse: product and page data can move, but the theme usually has to be rebuilt.
Old custom site nobody can edit: a migration to an editable CMS, with the design recreated, is often the sensible path.
A brand refresh with no platform problem: a redesign on the current platform may be all you need.

Red flags in a proposal

A vendor recommends a rebuild without inspecting the current site.
No plan for redirects or URL preservation.
No mention of email, DNS, forms or integrations.
A fixed date with no staging review.
No post-launch monitoring.

A way to start

Run a free PageScore for a first look at performance and technical health, then consider a human-reviewed Website Diagnostic if the decision is large. Our website migration page explains how we handle moves between platforms and hosts. If you are also weighing agencies, our guide on what changes the cost of a project shows how scope decisions affect the quote.

Frequently asked

What is the difference between a website migration and a rebuild?: A migration moves an existing site, its content and ideally its design and URLs, to a new platform or host. A rebuild redesigns or restructures the site, usually with new templates, new content structure or both. Many projects are a mix of the two.
Is moving from WordPress to Shopify a migration or a rebuild?: It is usually both. Products, pages and URLs can be migrated, but the theme and templates normally need to be rebuilt for the new platform. The scope depends on how much of the design must change.
Which option carries more SEO risk?: Whichever changes more URLs and content. A rebuild that restructures the site carries more risk than a like-for-like migration, but either can go wrong without a redirect plan and post-launch checks.
How do I know whether my current design is worth keeping?: Look at whether it supports your current goals, whether it works well on mobile and for keyboard users, and whether the templates are maintainable. If the design works and the platform is the problem, migrate. If the design and structure are both holding the business back, rebuild.