Can you redesign a website without changing the CMS?

A redesign does not require a new CMS

You can redesign a website without changing its content management system when the current platform can support the required page structure, content types, editorial workflow, integrations, performance, accessibility, and security obligations.

Keeping the CMS can reduce migration work and preserve a familiar editing process. It should be an evidence-based choice, not a shortcut that prevents the new website from meeting its goals.

Audit the platform against future needs

Review how content is modeled, who edits it, which fields and reusable sections exist, how preview and approval work, and where the current team relies on workarounds. Document integrations, hosting, licences, custom extensions, update responsibility, export options, and technical support.

Assess the future site rather than the present theme. A poor interface may hide a capable CMS; an attractive interface may hide rigid content structures and fragile dependencies.

Separate experience from technology

First define the audiences, journeys, content, components, functions, and operational needs of the redesigned site. Then test the CMS against those requirements. This prevents the current system from silently dictating the new information architecture.

The comparison between website redesign and replatforming explains how customer-facing change and platform change can be planned separately or delivered together.

Know when the CMS should change

Consider replatforming when essential content cannot be modeled cleanly, editors cannot maintain the site safely, required integrations are unreliable, updates are unsupported, ownership is unclear, or performance and accessibility problems are structural rather than cosmetic.

Include the cost and risk of both choices. A migration adds data mapping, content transfer, URL continuity, training, testing, and cutover work. Keeping an unsuitable platform can create recurring manual work and another rebuild.

Define the decision before design

• Requirements: document future content, editing, integration, and governance needs.
• Capability: prove what the current CMS can support without fragile workarounds.
• Ownership: confirm accounts, licences, code, hosting, and maintenance responsibility.
• Migration: estimate the work and continuity risks of changing platforms.
• Decision: state whether the redesign keeps, upgrades, or replaces the CMS.