By Mehdi HassanShould you do a migration and redesign at the same time?
Usually yes, with guardrails. A migration and redesign at the same time saves money because a platform move is already a full rebuild: you pay to recreate every page either way, so recreating the old design is often wasted work. The risk is diagnosis. If traffic drops after launch, you won't know whether the platform, the URLs, the design or the copy caused it.
The answer depends on two things: how much of your revenue comes from organic search, and how bad the current design is. This framework turns those into clear rules. It sits alongside our hub on website migration cost, which shows how redesign scope moves the price, and our guide to whether to rebrand and redesign together if the brand is also changing.
Why does combining a migration and redesign save money?
It saves money because there's no such thing as moving a design between platforms. No converter exists between Webflow and Framer, from Wix to anything, or from a builder to code. Every page is rebuilt by hand or by agents, and a rebuild of a new design costs about the same as a rebuild of the old one.
Doing them separately means paying for two builds: one to recreate the old design on the new platform, and another a few months later to replace it. You also run two rounds of QA, two launches and two periods of post-launch monitoring. Teams that combine them pay for design work once, build once and launch once.
Why does combining them make SEO harder to diagnose?
When you change several things at once, you lose the ability to tell which one caused a result. After a combined launch, a ranking drop could come from missing redirects, changed titles, rewritten copy, removed sections, slower pages or a new internal link structure. Each needs a different fix.
What changes | SEO risk | How easy to diagnose alone |
|---|---|---|
Platform only, same URLs and content | Low | Easy: check rendering, speed and metadata |
URLs change | Medium to high | Easy: check the redirect map |
Visual design and layout | Low to medium | Moderate: check content still present and crawlable |
Copy rewritten on ranking pages | Medium to high | Hard: relevance has changed |
Pages merged or removed | High | Moderate: check redirects and lost queries |
All of the above at once | High | Very hard |
Design changes on their own are usually low risk for SEO, as long as content stays in the HTML and pages stay fast. The changes that move rankings are URLs, titles, headings and body copy. That's the key to the safe middle path below.
What are the rules for deciding?
Use these rules in order. The first one that applies gives you the answer.
Rule 1: if organic search drives most pipeline, separate them
Migrate one to one first, with identical URLs, titles and copy. Confirm rankings hold for a few weeks, then redesign in a second release.
Rule 2: if the current design is clearly hurting conversion, combine them
Rebuilding a design you already know is weak wastes money. Redesign during the move, under the guardrails below.
Rule 3: if the site barely ranks, combine them freely
With little organic traffic to protect, the diagnosis risk is small. Change design, copy and structure together.
Rule 4: if you're also changing URLs, keep copy stable
Change one of URLs or ranking-page copy per release, not both. URLs plus design is manageable; URLs plus copy plus design is not.
Rule 5: if a deadline is fixed, cut the redesign scope, not the SEO work
Launch with a redesigned homepage and key pages, and a one-to-one rebuild of the rest. Redesign the long tail later.
If you're not sure whether you need a full redesign, our guide to redesign vs refresh helps you size the change, and homepage-only redesigns cover the case where fixing one page is enough.
How do you migrate and redesign safely at the same time?
Freeze the things search engines rank, and change the things people see. That means keeping URLs, title tags, H1s and the core body copy of ranking pages, while freely changing layout, visual design, imagery, navigation styling and calls to action.
- Keep URLs identical wherever the new platform allows. Where it can't, map every change in the redirect sheet.
- Keep titles, descriptions and H1s on pages that rank, unless you have a specific reason to change one.
- Keep the body copy of top-ranking pages close to the original at launch. Rewrite in a later release; our guide to rewriting content during a migration covers when it's worth it.
- Redesign everything visual: layout, type, color, imagery, components and conversion paths.
- Benchmark first. Record rankings, traffic and Core Web Vitals per key page before launch, so you have something to compare against.
- Stage the launch. Launch the redesign on the new platform, monitor for a few weeks, then ship copy changes as a separate release.
For example, suppose a SaaS company with a strong blog wants a new look and a new platform
Hypothetical example: a B2B SaaS company gets most demo requests from blog posts, and its marketing pages look dated. It wants to move from WordPress to Next.js and redesign.
Under the rules, the blog is protected: every post keeps its URL, title and body copy, and only the template design changes. The marketing pages, which rank for little, get a full redesign and new copy. After launch, if blog traffic drops, the team knows to check redirects and template rendering first, because nothing else on those pages changed. Copy updates to top posts go out a month later, one batch at a time.
What does each approach cost?
A combined project costs more than a one-to-one migration but less than a migration followed by a separate redesign. Agency quotes for migrations typically range from about $1,500 to $25,000 depending on size and complexity, and adding design work moves a quote toward the upper end of what that site would otherwise cost.
Pros
- Combined: one design phase, one build, one QA cycle and one launch.
- Combined: the new design can be built natively for the new platform's strengths.
- Separate: clean diagnosis of any SEO change after each release.
Cons
- Combined: harder to tell what caused a traffic drop.
- Combined: bigger project, more decisions, more room for scope creep.
- Separate: you pay to rebuild the old design, then pay again to replace it.
AI tools change the math a little. If coding agents make a one-to-one rebuild cheap, separating the two becomes more affordable. Our comparison of AI migration vs agency migration covers when that's realistic. For timing, see how long a website migration takes.
What if you're consolidating several sites?
Consolidating several sites into one almost always means redesigning, because no single old design fits the merged structure. The guardrails still apply: map every URL from every old site, keep titles and copy on ranking pages, and launch the merged structure before rewriting content. Our guide to consolidating WordPress Multisite covers that case in detail, and the migration plan template gives you go/no-go gates for each stage.
