Website Migration Cost: What Businesses Should Budget for a Replatform

Complexity Determines the Budget, Not Page Count

The first question everyone asks a vendor is how many pages, and it is close to the least informative number in the project.

What actually determines the budget is the current platform and what it will let you take with you, the destination platform, the number and type of templates, content volume and quality, integration count, SEO requirements, CRM requirements, redesign scope, any ecommerce or membership functionality, and how much launch risk the business can tolerate.

Two sites with identical page counts routinely differ by a factor of several in cost. This article explains why, and how to budget for the project you actually have.

What a Website Migration Includes

The full list, so you can check what a quote covers:

Discovery, content inventory, technical audit, information architecture, template development, content transfer, media migration, forms, integrations, redirects, metadata, analytics, QA, launch, and post launch monitoring.

Fifteen items. A quote that names four of them is not cheaper than one that names fifteen. It has moved eleven costs somewhere you cannot see them, and they will surface either as change orders or as problems after launch.

The Five Levels of Complexity

Level 1: simple content transfer. A small site, few templates, little customisation, minimal integrations, and a URL structure that can be preserved. Genuinely straightforward, and the only level where a fast fixed quote is reasonable.

Level 2: standard business website migration. Multiple templates, a blog, working forms, analytics, SEO preservation, and full redirect mapping. Where most established businesses actually sit. Still a technical project rather than a creative one.

Level 3: redesign plus migration. Everything in level 2 plus new information architecture, new messaging, a new design system, conversion improvements, and content editing. The redesign roughly doubles the surface area and adds review cycles that did not previously exist.

Level 4: complex marketing site replatform. Personalization to replace, multilingual content, advanced forms, CRM integrations, marketing automation, and a large content library. Integration and QA dominate the budget here rather than build.

Level 5: enterprise or ecommerce replatform. Product catalogue, customer accounts, order history, payments, inventory, multiple connected systems, complex permissions, and a launch where downtime has a direct revenue cost. A different category of project requiring a different category of planning.

Identifying your level before requesting quotes is the single most useful preparation available, because it lets you tell whether two proposals describe the same work.

What Each Cost Factor Actually Does

Number of templates. The strongest single predictor. Each distinct template is a separate design and build problem, and templates rarely transfer between platforms regardless of the pairing. Count yours before asking anyone for a number.

Number of pages and posts. Matters much less than expected when templates are shared. Ten thousand posts on one template can import in a weekend. Where volume does cost is cleanup.

Forms and integrations. Each one is configuration plus end to end testing plus the possibility that it behaves differently in production. This is the line that most often gets underestimated, because integrations are invisible until someone inventories them.

Multilingual content. Multiplies architecture decisions and QA. Not additive, multiplicative.

Redirect mapping. Scales with how much the URL structure changes. Preserving URLs reduces this to nearly nothing, which is why it is the first lever to pull.

SEO cleanup. Migrations surface legacy problems. Fixing them while everything is already being touched is efficient, and it is still additional scope that should be named rather than absorbed.

CRM replacement or retention. A large swing. Keeping the existing CRM removes an entire workstream. See CRM migration services for what the alternative involves.

QA and launch support. The item most tempting to trim and the worst one to lose. It is the difference between a launch and an incident.

Migration Cost Versus Redesign Cost

These are separate drivers and it helps to price them separately even when buying them together.

Migration preserves or transfers the existing system. The work is technical: templates rebuilt to match, content moved, URLs mapped, integrations reconnected.

Redesign changes the experience. The work is creative and editorial: new design system, new messaging, new structure, and the review cycles that come with both.

Combining them is often efficient, because templates are being rebuilt either way and doing that work twice costs more overall. It also increases scope, review cycles, and the number of people who must approve things.

The strongest argument for separating them is diagnostic rather than financial. If conversions or rankings move after a combined launch, you cannot attribute it. If you migrate like for like first, any change is the platform, and any later change is the design. Teams with revenue depending on the site usually want that clarity, and the full framing is in replatforming versus redesign.

What Makes a Migration More Expensive Than Expected

Nearly always a discovery failure rather than a build failure:

Poorly organised content that needs editorial work rather than an import. No URL inventory, so redirect scope was guessed and the guess was wrong. Many custom templates counted as pages during scoping. Unclear CRM ownership, so a decision blocks the build. Integrations nobody documented, discovered halfway through. Legacy forms with conditional logic nobody remembers building. Multiple languages mentioned late. Ecommerce or memberships treated as a feature rather than a subsystem. A short launch deadline that removes the QA which would have caught problems cheaply. And no internal decision maker, so every question costs a week.

That last one is the most expensive and the least discussed. A migration without someone empowered to make content and scope decisions quickly will overrun regardless of how good the vendor is.

What Reduces Cost Safely

Preserve stable URLs. Removes redirect scope and risk simultaneously.

Remove obsolete content first. Do not pay to move pages nobody reads. The URL inventory identifies them.

Separate must have from nice to have explicitly, in writing, before quoting.

Do not redesign every page. A subset carries most of the value.

Keep the CRM if it works. Removes a whole workstream and a whole risk category.

Stage the migration where the architecture allows it.

Prioritise high value pages. Get the revenue pages right first.

Complete discovery before development. Scope found mid build is the most expensive scope there is.

What does not reduce cost safely: skipping staging QA, skipping redirect mapping, and skipping post launch monitoring. Those look like savings and function as deferred costs with interest.

Questions to Ask Before Comparing Quotes

Is content migration included? Is content cleanup included, separately? Are redirects included, and who builds the URL map? Is SEO preservation included and what does it consist of? Are forms and integrations included and tested? Who owns QA? Is launch monitoring included and for how long? Is CRM work in or out? What happens when scope changes? Is post launch support included?

Ask every vendor the same ten. The answers will differ more than the prices do, and the gap between a cheap quote and a complete one is usually missing work rather than better value.

A Planning Formula

Rather than a single number, budget in components:

Migration scope = platform work + content work + SEO work + integration work + QA and launch risk.

Platform work is templates, architecture, and the build. Content work is transfer plus cleanup plus any editing. SEO work is inventory, URL mapping, redirects, metadata, and monitoring. Integration work is forms, tracking, CRM connections, and third party systems. QA and launch risk is staging testing, launch support, and post launch monitoring.

Ask for a quote that identifies each of those separately rather than hiding all five under "website migration". Two benefits: you can compare proposals meaningfully, and you can make informed trade offs, because if the number is too high you can see which component to reduce rather than negotiating blindly on the total.

For the HubSpot specific version of this, see HubSpot to WordPress migration cost. The SEO component is covered in the SEO migration checklist and, for WordPress destinations specifically, migrating without losing SEO.

Frequently Asked Questions

What determines website migration cost?

Complexity rather than page count. The strongest predictors are the number of distinct templates that must be rebuilt, the number of integrations requiring configuration and testing, whether the URL structure can be preserved, how much content cleanup the import demands, and whether a redesign is bundled in. A hundred pages sharing three templates is largely a repeatable process. Ten pages with ten bespoke layouts and a dozen connected systems is ten build problems plus an integration project, and it costs considerably more despite being a smaller site by every obvious measure.

Is a website migration cheaper than a redesign?

A like for like migration is usually cheaper than a redesign, because it carries no design, messaging, or content strategy work and no review cycles attached to those. It is also faster and lower risk, since URLs and structure largely stay put. The comparison shifts when they are combined, which many projects do because templates are being rebuilt either way. Combining is efficient in total effort and expensive in clarity, because a change in traffic or conversion afterwards cannot be attributed to either the platform change or the design change.

What makes a website migration more expensive than expected?

Discovery failures, almost always. Integrations nobody documented, a URL inventory that never existed so redirect scope was guessed, content quality bad enough to need editorial cleanup rather than an import, custom templates counted as pages, legacy forms with logic nobody remembers, and no internal decision maker so every question waits a week. Short launch deadlines multiply all of these, because compressed timelines remove the staging QA and testing that would have caught problems while they were still cheap to fix.

How can a business reduce website migration cost safely?

Preserve stable URLs, which removes redirect scope and risk at once. Remove obsolete content before migrating rather than paying to move pages nobody reads. Separate must have from nice to have explicitly. Avoid redesigning every page when a subset carries the value. Keep the existing CRM if it works. Stage the migration rather than launching everything at once. Prioritise the pages that produce traffic, leads, and revenue. And complete discovery before development starts, because scope discovered mid build is the most expensive scope there is.

What should a website migration quote include?

Content migration and content cleanup as separate items, URL mapping and redirect implementation, SEO preservation, forms and integrations with testing, QA on staging with a named owner, launch support, and post launch monitoring with a stated duration. Whether CRM work is in or out should be explicit. So should the boundary between migration and redesign, and what happens when scope changes. A quote that says website migration and gives one number is not comparable to a quote that itemises these, and the difference between them is usually missing work rather than margin.

Get the Scope Before You Get the Quotes

You cannot budget a project nobody has defined, and you cannot compare quotes priced against different assumptions.

Get a migration scope review and we will document your templates, your URL inventory, your integrations, and the CRM decision, so you know which complexity level you are in before any vendor puts a number on it. Related: replatforming versus redesign, CRM migration, and the SEO migration checklist. Book a strategy call or call us at 321-401-7016.