By Mehdi HassanDo you need a redesign or a new platform?
You need a redesign if the problem is what visitors see and read. You need a new platform if the problem is what your team can do behind the scenes. Most sites that underperform have a messaging or design problem, not a platform problem, which is why a redesign is the more common answer.
The difficulty is that symptoms overlap. A slow, dated, hard-to-edit site can feel like one big problem that only a migration will fix. Split it into four symptoms (messaging, design, speed and workflow) and each one points to a specific fix. This is one part of our wider website migration decision framework, focused on the redesign question.
Redesign vs replatform: how do symptoms map to fixes?
Each symptom has a most likely cause and a first fix. The table is the short version; the sections below explain how to test each one.
Symptom | What you notice | Likely cause | Fix |
|---|---|---|---|
Messaging | Prospects ask what you do; bounce is high | Copy and positioning | Rewrite, then redesign |
Design | Site looks dated or templated next to competitors | Visual design | Redesign on the current platform |
Speed | Pages load slowly; poor Core Web Vitals | Build quality | Optimize in place |
Workflow | Editors wait on developers; content won't fit | Platform | Replatform |
Integration | Site can't connect to your product or CRM | Platform | Replatform, often to code |
Notice that only the last two rows point to a new platform. If your symptoms sit in the first three, a redesign or a fix in place is cheaper and faster.
How do you tell if it's a messaging problem?
It's a messaging problem if people don't understand what you sell after reading the homepage. Test it with the five-second test: show the homepage to someone outside the company for five seconds, then ask what the company does and who it's for. If they can't answer, it's messaging.
Other signs: sales calls start with a basic explanation, the headline could describe a competitor, or paid traffic bounces before scrolling. Fix it by rewriting the homepage and key pages around one customer, one problem and one outcome. Our guide on whether the problem is the platform or the copy goes deeper, and if you're replatforming anyway, see when to rewrite copy during a migration.
How do you tell if it's a design problem?
It's a design problem if the message is clear but the site doesn't look as credible as the company is. Put your homepage next to three competitors and two companies a stage ahead of you. If yours looks older, cheaper or more generic, design is holding you back.
A redesign on your current platform fixes this. Framer, Webflow and Next.js can all produce a modern, custom site, so the platform is rarely the blocker. Decide whether you need a full redesign or a lighter touch; our comparison of website redesign vs refresh helps you choose.
How do you tell if it's a speed problem?
It's a speed problem if real-user data shows slow loading or poor interaction scores, not just a feeling. Check Core Web Vitals in Google Search Console or PageSpeed Insights. Then look at what's heavy: large images, autoplay video, third-party scripts and too many font files are the usual causes.
Most of these are fixed in place. Compress and resize images, lazy-load video, remove unused scripts and limit fonts. Only consider replatforming for speed if the platform itself won't let you control what loads. Our guide to speeding up a Webflow or Framer site before migrating lists the fixes.
How do you tell if it's a workflow problem?
It's a workflow problem if the site's content and look are fine, but your team can't keep it current. This is the strongest case for replatforming, because workflow is set by the platform.
- Editors are blocked. Marketers need a developer to change a headline or add a page.
- Content doesn't fit. The CMS can't model case studies, integrations or locations without duplicating pages by hand.
- Integrations are impossible. The site can't share auth or data with your product, or sync with your CRM.
- Publishing is risky. Every change might break another page, so nobody changes anything.
If two or more apply, replatforming is likely worth it. If you're on code and want marketers free of engineering, see moving from code to a visual builder. If you're on a builder and need product integration, the move usually goes the other way, toward Next.js. Before you commit, build a redirect map so you know the SEO work involved.
Hypothetical example: one site, four symptoms
For example, suppose a B2B SaaS company on Webflow says its site needs a migration. Diagnosis shows the homepage fails the five-second test (messaging), it looks dated next to competitors (design), Core Web Vitals are poor because of a heavy hero video (speed), but marketers publish freely and the CMS fits (no workflow problem).
The right fix is a rewrite, a redesign and a video optimization, all on Webflow. No migration. Had the team replatformed, they'd have paid for a rebuild and still had all three problems on day one.
What if you have both a design and a platform problem?
Then do both, in the right order: messaging first, design second, build last. Write and design the new site in Figma before you commit to a platform, then build once. That way the new design shapes the build, and you don't rebuild twice.
Audit content
List pages and traffic, and decide what to keep. Our content audit method helps.
Fix messaging
Rewrite the homepage and key pages before any visual work.
Design in Figma
Explore directions and agree on one, independent of the platform.
Choose the platform
Pick based on workflow and integration needs, not design.
Build and migrate
Rebuild, move content, set redirects and launch at a quiet time.
Our brand and design sprint is built for the design step. It's $3,000, fixed: a brand refresh or redesign plus 10 website and product explorations, delivered as Figma files. You can build from them on any platform.
