What is a website replatform and when does it make sense?

A redesign changes what your website looks like and how it's structured. It typically involves new branding, new information architecture, new content, and new design. It's a large, expensive undertaking that touches every part of the site.

A replatform changes what your website runs on. The design stays the same. The content stays the same. The URLs and search rankings stay the same. What changes is the infrastructure underneath: how content is managed, how the site is hosted, how changes are deployed, and what it costs to keep everything running.

The two aren't mutually exclusive. You can replatform and redesign at the same time. But treating them as separate decisions is useful because it means you don't have to wait for (or fund) a full redesign to address platform problems that are costing you money right now.

Not every website needs to be replatformed. If your platform is working well, costs are reasonable, your team is productive, and you're not hitting limitations, there's no reason to change.

A replatform makes sense when the platform itself has become the problem:

Your maintenance costs are disproportionate. If a large share of your annual web budget goes to keeping the lights on (security patches, framework updates, server maintenance, database upkeep) rather than making the site better, the platform is working against you. A modern platform can significantly reduce or eliminate this overhead.

Changes are slow and expensive. On older platforms, even straightforward changes can require developer involvement, custom code, and careful testing. If adding a new page type, updating a layout, or publishing content takes longer than it should, the platform architecture is the bottleneck.

Your team finds the CMS frustrating. Content management systems have improved dramatically in recent years. If your editors are working around the CMS rather than with it, creating workarounds, maintaining spreadsheets, or avoiding the system altogether, a modern CMS would make a significant difference to their productivity and satisfaction.

You're facing growing technical risk. Aging platforms accumulate technical debt: outdated dependencies, unsupported frameworks, known vulnerabilities. The cost of addressing this debt on the existing platform is often comparable to the cost of moving to a new one, except the investment in the old platform doesn't carry forward.

You're about to invest in a major project. If you're planning significant work on your website, it's worth asking whether that investment should go into the current platform or a new one. Building on top of aging infrastructure means the new work inherits all the existing limitations and costs.

"The very first year we had the new platform we were able to develop a mobile-enabled scavenger hunt which has resulted in an ongoing sponsorship agreement with Sunshine Coast."

             Ryan McArthur, Beervana

The process is more structured and predictable than a redesign, because the scope is narrower. You're not making subjective decisions about branding and design. You're making practical decisions about technology and content structure.

A typical replatform follows these steps:

1. Audit. Review the existing site: what content exists, what templates and page types are in use, what integrations and custom functionality are present, and where the pain points are.

2. Plan the content model. Design the content structure for the new CMS. This is where the shift to a modern, component-driven architecture happens. Instead of rigid page templates, content is structured as reusable building blocks that editors can assemble.

3. Build the front-end. Recreate the site's existing design using a modern framework. The goal is visual parity: the site should look the same to visitors.

4. Migrate content. Move content from the old CMS to the new one. Depending on the scale and complexity, this can be partially or fully automated.

5. Test and launch. Ensure everything works, redirects are in place, search rankings are preserved, and the editorial team is comfortable with the new system.

The timeline and cost depend on the size and complexity of the site, but a replatform is typically faster and less expensive than a redesign because you're not starting from scratch on design, information architecture, or content strategy.

The site your audience sees looks the same on launch day. What changes is everything behind it:

• Lower ongoing costs. Modern hosting (static sites served from a CDN) costs a fraction of running a dedicated server. Maintenance overhead drops significantly.
• Faster changes. Component-driven architecture means new pages and features are assembled from proven building blocks, not built from scratch each time.
• A better CMS. Modern content management systems are designed for the people who actually use them. Editing, publishing, and managing content becomes faster and less frustrating.
• Reduced risk. No more patching aging frameworks, managing server infrastructure, or worrying about unsupported dependencies.
• A foundation for what comes next. Instead of working around platform limitations, your team can focus on making the site genuinely better for the people who use it.

If any of the triggers above sound familiar, it's worth exploring. We've completed replatforms for New Zealand organisations ranging from national institutions to small non-profits, and we're happy to have a no-obligation conversation about whether it makes sense for your situation.

Book a call with us or check out our replatforming estimator to see what it's likely to cost for you.

Get your estimate

See further readings that might be of interest to you.

Website replatforming - a general guide on replatforming

What does a website replatform actually cost? — a breakdown of where the money goes and what drives costs up or down.

SilverStripe alternatives: a guide for NZ organisations considering a move — a quick review of what is out there.