Redesign and migration
Redesign or rebuild
Website redesign vs rebuild — restyling an existing site versus replacing its underlying platform — priced and scoped completely differently.
A redesign changes how a site looks and is organised while keeping its underlying platform. A rebuild replaces the platform itself. Confusing the two when briefing a project is the single most common cause of a quote that seems wildly out of proportion to what was actually asked for.
What a website redesign genuinely is: a minor refresh, not a rebuild
A redesign — sometimes called a refresh or a restyle — changes the visual design, the content structure, or the navigation of a site. It stays on the same underlying platform, and generally the same hosting and codebase. A new template applied to an existing WordPress site is redesign-scope work. So is a reorganised set of service pages, or updated photography and typography. These can typically be scheduled and priced without touching the technical foundations.
What a website rebuild genuinely is: replatforming an outdated CMS or site structure
A rebuild — sometimes called a replatform — replaces the underlying system the site runs on. That might mean moving from one content management system to another. It might mean moving from a website builder to a custom-coded platform. Or moving between fundamentally different technical foundations. This is a different category of project. It involves not just what visitors see, but how content is stored, how the site is edited, and how it connects to other systems. Critically, it also covers how existing content and URLs carry across. That last part is covered in full on moving between platforms.
Why the redesign rebuild distinction changes the brief and business goals entirely
| Redesign (same platform) | Rebuild (new platform) | |
|---|---|---|
| What changes | Visual design, content structure, navigation | The underlying system itself |
| Content migration risk | Low — content generally stays in place | Real — every piece of content needs to move, covered on content migration |
| URL and SEO risk | Low, if URLs are kept the same | Real — a new platform frequently changes URL structure by default, covered on redesigning without losing rankings |
| Typical timeframe | Weeks | Months |
| What a supplier needs to quote against | The scope of visual and structural change | The full technical migration, including data, integrations and redirects |
What a template change actually includes, and what rebuilding does not
Applying a new theme or template to an existing WordPress site is often treated as the clearest example of pure redesign-scope work, and it usually is. But it is not automatically a drop-in swap. A theme change can still require checking that existing plugins remain compatible with the new theme’s structure. It can mean rebuilding any custom page layouts that were built specifically against the old theme’s templates. It also means reviewing whether custom code added to the old theme — via a child theme or theme-specific functions — needs to be carried across or rebuilt for the new one. None of this rises to rebuild-scale work. But it is more than “pick a new theme and publish.” A quote that treats a template change as literally instantaneous is underscoping it slightly in the other direction.
The middle case that straddles the line: usability, structure and a site that feels slow
Some changes sit genuinely between the two categories. Moving from an older page-builder-based WordPress site to a modern block-based full-site-editing theme stays on the same platform in the broadest sense — still WordPress, still the same database. But it changes enough of the underlying editing and templating system that it behaves more like a rebuild in practice. The category that matters is not the platform’s name. It is the actual technical distance being covered. That means asking whether the content, structure and functionality genuinely carry across with light adjustment, or whether most of it needs to be recreated against a different underlying system. When a project sits in this middle ground, it is worth asking a prospective supplier to describe specifically which of the redesign-scope or rebuild-scope work in the table above applies. Do not simply accept the platform’s name as the answer.
Why price alone does not reliably signal which category a quote represents
Two suppliers quoting the same underlying request can describe it as a “redesign” and a “rebuild” respectively, for reasons that have nothing to do with what is actually being proposed. One may be scoping the work more thoroughly than the other. Or the two may have different assumptions about what stays and what changes. That difference is usually discovered only when the deliverables are compared line by line, rather than by the label on the quote. The category names in this page are a starting vocabulary for that conversation. They are not a substitute for confirming, specifically, what each supplier’s quote actually includes.
Why “just redesign it” sometimes turns into a rebuild anyway, when you actually need rebuild-level work
Some redesign requests reveal, during scoping, that the current platform genuinely cannot support what is being asked for. A modern, accessible, responsive design pattern the old platform’s templating system cannot render is a common example. At that point, the honest scope becomes a rebuild, whether or not that was the original intent. This is a legitimate scope change, not a bait-and-switch. It just needs to be explained and re-quoted, rather than absorbed silently into what was originally priced as a lighter piece of work.
What to establish before briefing either
- Is the current platform capable of supporting the desired visual and structural changes at all
- Is the current platform itself the reason the site needs work, or only its current template or content
- If the platform is changing, has the migration scope — content, URLs, integrations — been genuinely accounted for in the quote, not treated as an afterthought
What to do next
Establish honestly which category the project actually is before requesting quotes. A redesign quote and a rebuild quote answer different questions, and they are not comparable against each other. For the platform-change specifics once a rebuild is confirmed, see moving between platforms. For what either category of project typically costs, website design services sets out the broader service scope this decision sits inside.
Evidence for this page
This page exists because the demand below was measured, not assumed. The figures are search-market data about the topic — they are not prices.
- Entity this page targets
- website redesign vs rebuild
- Measured Google volume
- no data
- Keyword difficulty
- no data
- Advertiser cost per click
- no data
- AI assistant volume
- no data
- Advertiser competition
- no data
- Measured on
- 31 July 2026
- Search results inspected for intent
- No
2 other phrasings resolve to this same page
refresh vs rebuild website · redesign vs replatform
Not present in the measured keyword set under the Australian phrasings tested. A genuine null.
Source: research/national-volume-au.json · DataForSEO Labs, location_code 2036 (Australia), language en · pulled 31 July 2026.
Provenance
Written by Australian Website Design. Published 2026-08-03, last updated 2026-08-03.
Sources
- WordPress.org — About themes (accessed 2026-08-03)