"We need a new website." It's one of the most common sentences in marketing, and one of the most expensive. Sometimes it's exactly right. Just as often, it's a reflex, a response to frustration that a redesign or targeted fixes would solve faster and for far less money.
Replatforming, moving your site to a new underlying system, is a big commitment. So before you sign up for one, it's worth pressure-testing whether you actually need it. Here's a framework for making that call with clear eyes.
What's the difference between a redesign and a replatform?
This distinction saves a lot of money, so it's worth being precise.
A redesign changes how the site looks and works on the same underlying platform. New visuals, new structure, new content, same foundation.
A replatform changes the foundation itself, moving from one system to another, or from a heavily customized legacy build to a modern one. It's deeper, more involved, and more disruptive, because you're rebuilding the base, not just the surface.
Plenty of "we need to replatform" conversations are actually "we need to redesign" conversations. Naming the difference early keeps you from buying a foundation replacement when a renovation would do.
Don’t replace the platform if the platform isn’t the problem.
What are the real signs you need to replatform?
Look for structural problems, not surface-level annoyances. A few honest signals:
- Your current platform actively fights your goals. If you can't build the content structures you need, can't integrate essential tools, or hit a wall every time you try to grow, the platform itself may be the constraint.
- Maintenance is eating you alive. Constant plugin conflicts, security scares, fragile custom code that only one former contractor understood. When keeping the lights on consumes the time you should spend improving the site, that's a foundation problem.
- You can't integrate what the business needs. When we replatformed our client Plant Extracts International off a proprietary system onto WordPress and WooCommerce, the platform choice was driven by their need for flexibility, easier day-to-day management, and integrations the old stack simply couldn't support. If your current setup can't connect to the tools your business now depends on, that's a legitimate driver.
- The site can't scale with your content. Our client the Network for Public Health Law needed an architecture that could organize hundreds of pages and support programs, resources, news, and events without collapsing into chaos. If your content ambitions have outgrown your platform's structure, replatforming may be the honest answer.
- You're maintaining a legacy build nobody wants to touch. Sometimes the accumulated weight of years of customization makes a clean modern foundation genuinely cheaper than continued patching.
What are the signs you don't need to replatform?
Just as important, because these are the cases where replatforming wastes money.
- The site looks dated but works fine. That's a redesign, not a replatform.
- Content is disorganized. Often an information-architecture and content project, solvable on your current platform.
- SEO is underperforming. Usually a strategy and execution issue, not a platform limitation. We've driven strong organic gains for clients on their existing platforms through audits and optimization, no rebuild required.
- One feature is missing. Frequently addable through a plugin, integration, or custom development rather than a full migration.
If your platform still supports where you're going, the smart move is usually to improve what you have.
Can't you just optimize the site you already have?
Often, yes, and it's worth taking seriously before committing to a migration.
The lesson isn't "never replatform." It's "don't replatform to solve a problem that optimization can fix." A migration you didn't need is one of the most expensive detours in marketing.
How do you make the final call?
Work through it in order. First, define the actual problem, not the symptom. Second, decide whether it's a look-and-feel issue (redesign), a content-structure issue (architecture project), a performance issue (optimization), or a genuine foundation issue (replatform). Third, be honest about whether your current platform can support where the business is heading in the next two to three years.
If the foundation genuinely can't get you there, replatform with confidence. If it can, invest that budget in redesign, content, and optimization instead. Either way, you'll have made the decision on purpose rather than on frustration, and that's what separates a smart investment from an expensive reflex. Not sure which camp you're in? We can help you decide.
Frequently asked questions about replatforming a website
What is the difference between a website redesign and a replatform?
A redesign changes the appearance and experience while retaining the platform. Replatforming replaces the underlying system or technical foundation.
What are the signs that you actually need to replatform?
Your platform may need replacing when it blocks business goals, requires excessive maintenance, cannot support essential integrations, cannot scale, or relies on a fragile legacy build.
When should you not replatform?
Do not replatform merely because the design looks dated, content is disorganized, SEO is underperforming, or one feature is missing.
Can SEO optimization replace the need for a new website?
Often, yes. A technically sound website may improve substantially through SEO, content, architecture, and performance work without a migration.
How do you decide whether to replatform?
Define the real problem, determine whether it involves design, content architecture, performance, or the underlying platform, and assess whether the current foundation can support the next several years.
