Website & Development
Replatform vs Redesign vs Rebuild: Which Route Do You Choose?
Copy for AI
Replatform vs redesign: the right route depends on what’s actually broken.
If the problem sits in your tech, you replatform. If it sits in your look and user experience, you redesign. If your whole foundation no longer holds, you rebuild.
The verdict: diagnose first, then pick the smallest intervention that fully fixes the problem. Most B2B companies shout “we need a new website” and order the most expensive route, while a targeted one would have solved it.
Below is a sober decision framework that separates the three by the problem, not by what a vendor likes to sell.
It belongs in the broader context of our guide to building a B2B website. Rather talk it through for your own site? See our approach to website development.
What is the difference between replatform, redesign and rebuild?
A replatform touches your tech, a redesign touches your look, a rebuild touches both plus your foundation.
They sound interchangeable.
They’re three different projects, with a different budget, lead time and risk.
The three routes in one line each
Think of your site as a car:
- Replatform: a new, more efficient engine in the same car
- Redesign: the engine stays, the bodywork comes off
- Rebuild: new engine, new bodywork, new layout
A replatform moves your site to a different CMS or platform, while design and structure stay largely the same. Driving and maintenance get easier.
A redesign renews how your site looks and feels (layout, branding, UX), while the platform or codebase largely stays.
A rebuild is the most drastic. You rethink structure, content and tech at once, usually tied to a new positioning.
Side by side
Here’s how the three compare:
| Replatform | Redesign | Rebuild | |
|---|---|---|---|
| What changes | CMS or platform | Look, navigation, UX, copy | Positioning, structure, content, design, tech |
| What stays | Design and structure | Platform and back-end | Little or nothing |
| Relative budget and lead time | Medium | Lower | Highest |
| Main risk | URLs and rankings in the move | A sleeker site that converts no better | Risks pile up, especially findability |
Why the difference isn’t semantics
Order a rebuild for a problem a redesign would have solved, and you pay far too much.
You also take on more risk than necessary.
Order a redesign while the real problem is a slow, stuck CMS, and you solve nothing.
A year later, you’re left with the same complaint.
When do you choose a replatform?
When your tech works against you, but your design and structure still hold up.
The signal is simple: you don’t find your site ugly or confusing. You find it unmanageable.
Four triggers for a replatform
Watch for these:
- Slow publishing: you need a developer for every change
- No integrations: your CMS won’t connect to tools such as your CRM or analytics
- Structurally slow: you can’t fix your Core Web Vitals on the current platform
- Costs out of hand: maintenance, security or licences keep rising
On speed, the web.dev thresholds for “good” are clear. LCP within 2.5 seconds, INP of 200 ms or less and CLS of 0.1 or less, measured at the 75th percentile.
Check where you stand before you decide. Here’s what our own field data looks like:
PageSpeed Insights field data for customerimpact.be on mobile, October 2026. LCP passes at 1.9 s; CLS at 0.13 still needs work.
Our LCP passes at 1.9 seconds; our CLS of 0.13 doesn’t.
A CLS problem like ours is often fixable on the current platform. That’s a fix, not a replatform.
Run your own pages through our website speed test first.
The risk sits in the move, not the build
With a pure replatform, you keep the design as intact as possible and move the tech underneath.
The biggest risk is the transition.
Old URLs that disappear cost you rankings and traffic if you don’t redirect them correctly.
Google’s site move guide asks for a URL mapping: “decide where each one should redirect to.” It also warns that “you may experience ranking fluctuations”.
Three timing facts from the same guide and Google’s redirects documentation:
- Move time: a small to medium site “can take a few weeks for most pages to move”
- Redirect type: Google recommends “a permanent server-side redirect whenever possible”
- Keep them: redirects stay “for as long as possible, generally at least 1 year”
Our experience: migrations and redesigns are the classic cause when buyers tell us their organic traffic dropped. Badly done redirects can cut it sharply.
Treat the move as a separate track. Follow the playbook in website migration without losing rankings, and build your list with a 301 redirect plan.
Keep thinking platform-independently
Webflow, WordPress and a custom or headless approach each have strengths and weaknesses.
Which one fits depends on your team, content needs, budget and growth plans.
No platform always wins.
Our experience: WordPress, Drupal, Webflow and Joomla all used to be good default choices. Now it depends on the company.
AI and digital-native companies increasingly move to agentic websites. No plugin updates, no security warnings, and languages built and translated programmatically. That’s what our AI website development builds.
Two of the classic options, side by side:
Webflow’s homepage, October 2026.
The open source alternative takes a different approach:
WordPress.org, October 2026. It calls itself the platform of choice for millions of websites.
Weighing the two? See Webflow vs WordPress, or the wider view in which CMS to choose.
Doubting the logic of decoupling front and backend? Then read headless CMS explained.
When do you choose a redesign?
When your platform works perfectly well, but your site looks dated or makes visitors drop off.
Here the tech isn’t the problem. The first impression and the user experience are.
Four signals for a redesign
Recognisable signals:
- Dated look: it casts doubt on whether you’re still active
- Missing branding: your new positioning shows up nowhere
- Lost visitors: people don’t find what they need and leave before the form
- Flat conversion: traffic holds steady, enquiries lag
What a redesign touches
A redesign leaves your back-end in place. It focuses on design, navigation, copy and conversion paths.
That makes it faster and cheaper than a rebuild, provided your platform can handle the renewal.
Treat it as a project, not a touch-up.
Start from your goals and your data, not from what looks nicer.
The full approach is in the website redesign process. Budgeting is covered in website redesign cost.
”Nicer” isn’t a goal
Watch out for a common reasoning error.
In B2B, the goal is more and better leads from the same traffic.
A redesign that looks sleeker but brings no more appointments or quotes isn’t a success.
Steer on leads and revenue, not aesthetics alone.
How to build a site that brings in customers is in a B2B website that generates leads.
When is a full rebuild needed?
When both your tech and your content foundation no longer hold up.
It’s the heaviest intervention, so it’s the one you must justify most sharply.
Three signs your foundation is broken
Your foundation is broken when:
- Your company changed: for example new services, acquisitions or a new positioning
- Your structure is a maze: pages piled up over the years without a model
- Everything gets stuck at once: platform and information architecture block each other
What a rebuild puts on the table
With a rebuild, you rethink the site from the ground up:
- positioning and message
- structure and navigation
- content
- design and tech
Because everything is on the table at once, a rebuild costs more and takes longer. The risks pile up, especially around keeping your findability.
So plan ranking preservation in advance with maintaining rankings after a website redesign.
In the same move, put AI findability in the briefing. How to factor GEO into your website redesign is a separate read.
Not every “everything is outdated” needs a rebuild
Often, after a sober diagnosis, two of the three layers turn out to be fine.
A rebuild is justified when the foundation itself no longer fits. Not because the site happens to feel old and slow at the same time.
How do you decide between replatform vs redesign vs rebuild?
Ask three questions in order, and let the answers pick the route.
Here’s the decision in one picture:
The three questions in order
Work through them one by one:
- Is my foundation broken? Do positioning and structure no longer match what we sell, and to whom? Is the site a maze without a model? Two times yes points to a rebuild.
- Is my look broken? Does the platform still work, but the site looks dated, confusing or off-brand, and does conversion lag? That points to a redesign.
- Is my tech broken? Do design and structure hold, but the CMS works against you (slow, closed, expensive to maintain)? That points to a replatform.
For example, say your site looks fine but every new landing page needs a developer ticket. That’s question 3: a replatform, not a redesign.
Two principles that sharpen the choice
First: always take a baseline of your traffic, conversion and load time.
Without a starting point, you won’t know afterwards whether the intervention delivered anything.
You’d be guided by gut feeling.
Your Search Console already holds part of that baseline:
Our own Search Console, Core Web Vitals on mobile, October 2026. Layout shift, not load speed, keeps 349 mobile URLs out of the green.
In our case, 349 mobile URLs sit in “needs improvement” because of one layout shift issue.
Export that report, with your traffic and enquiries, before anything changes.
Second: choose the smallest intervention that fully solves the problem.
It’s tempting to “just do everything properly at once”.
But every extra layer you open adds budget, time and risk.
Sometimes the answer is: nothing drastic
If it’s only a few outdated sections, a targeted refresh beats all three big tracks.
Cheaper, faster, and often enough to remove the real bottleneck.
Not sure you need anything at all? Check the signs you need a new website first.
Frequently asked questions
Is a replatform cheaper than a redesign?
Not always. A redesign leaves the back-end in place, so it’s often the lighter project. A replatform moves the tech and adds a migration track with URL mapping and redirects.
Can you replatform and redesign at the same time?
You can, but then you open two layers at once and the risks add up. If only one layer is broken, fix that one first.
How long should redirects stay in place after a replatform?
Google’s site move guide says to keep them for as long as possible, generally at least one year.
Does a redesign hurt SEO?
It can, if URLs, content or internal links change without a plan. Keep URLs where you can, redirect the rest, and compare against your baseline after launch.
The short summary
Replatform, redesign and rebuild aren’t synonyms. They’re three answers to three different problems.
A replatform repairs your tech, a redesign your look and UX, a rebuild your whole foundation.
Diagnose first, take a baseline, then pick the smallest intervention that fully removes the problem. That way you pay for what you need, not what sounds good.
Still doubting which route fits your site? We’re a small, senior B2B team that advises platform-independently and steers on leads and revenue, not on aesthetics alone.
Contact us and we’ll tell you which layer is broken, and when a lighter fix is enough.
Free website scan
Enter your website and get an automatic scan within minutes, with concrete technical and SEO improvements. No sales pitch.
We only use your details for your scan. No spam, unsubscribe anytime.