What decides the cost of moving off Webflow

A migration is priced as a build: from $5,000, agreed in writing before anything starts. What sets the number is the layouts being rebuilt, the content being moved, the functionality being preserved and the addresses that change. The source platform affects all four, and two sites on the same platform can still be very different jobs.

What the exports actually give you

For a Webflow migration, scope three inputs separately: the code export, the CMS data and the connected services. The code is useful implementation evidence. Content still needs mapping, and services still need an operating destination.

Ask what source material has actually been reviewed. A representative export and integration test make an estimate more useful than assumptions based only on the visible page count.

Budget for URL mapping and redirects

On one migration I mapped and verified 773 redirects, against a site nobody would have called large.

That is why I inventory the addresses separately from the templates: the visible navigation does not reveal every address a migration has to account for. Before estimating, I work out which addresses should stay, which should point somewhere new and which content is being retired.

The four things that set the number

How many distinct layouts there are. Forty pages from three layouts is three templates and a collection. Forty hand-adjusted pages is more work, and a rebuild is often the chance to consolidate them into fewer reusable ones, which is worth asking about.

What shape the content is in. Content already structured (posts, products, team members, locations) is extracted, transformed and validated. Content typed into pages has to be pulled out and mapped first, which is a different job from re-keying it and is usually somewhere between the two.

What the existing site does. Forms, memberships, search, commerce, localization and whatever else the old platform was handling. Each needs a decision rather than an equivalent, and some need custom code or a third-party service. This is where a plugin-heavy WordPress site costs more than its page count suggests.

How many addresses change. Every address that changes needs a decision about where it goes, though not necessarily a rule of its own: a whole route family that moves predictably can be handled as a pattern. Working that out is real hours, and it is the line most often missing from a cheap quote.

What I charge for one

A migration is priced as a build: from $5,000. I review the existing site, the content available, the functionality that has to be preserved and the URL structure before agreeing a fixed scope and a price.

The estimate says what is being rebuilt, what is being migrated, what is being replaced and what is being retired, along with the testing and the post-launch support included.

One other shape exists if the move is not what you need: $2,500 a month for ongoing work on a site already in Webflow.

What to ask before accepting any quote

Five questions, and the answers tell you whether the number will hold.

What source material have you reviewed? The export, access to the old site, or a sample of the content. Quoting without looking at any of it is guessing.

Which templates and content types does the estimate include? A specific answer means somebody counted.

How will the existing addresses and search settings be handled? URL mapping and tested redirects keep existing content reachable. They sit alongside the metadata, the internal links and whether pages can be indexed, and rankings can still move regardless.

Which features need rebuilding, replacing or a separate service? Every migration off a busy site has at least one thing Webflow does not do natively.

What testing, launch support and ongoing costs are included? The parts that are easiest to leave out of a number.

The Webflow migration guide explains the source platform work in more detail. Compare the proposed scope with that inventory, including the features that require services or integration code rather than exported files.

Compare two scopes before comparing two prices

Imagine two Webflow sites with the same number of public pages. The first has four repeated templates, a straightforward blog and one contact form. The second has individually composed campaign pages, several languages, gated downloads, historical redirects and multiple CRM destinations. A page-count price treats them as similar. The migration work does not.

The right comparison is a list of outcomes. Both quotes may include the visual rebuild, but only one may include content conversion, editor training, redirect verification or the last import before launch. A lower total can represent an efficient approach, a smaller scope or an unrecognized dependency. You need the breakdown to tell which.

The following examples describe scope patterns, not price estimates or customer results.

A useful estimate identifies which pattern dominates your project and what has actually been inspected. It should not treat every unknown as if it were already solved.

Separate the migration bill from the running costs

A migration creates a new operating arrangement. The one-time project price and the ongoing cost of that arrangement answer different questions. Keep them separate when deciding whether the move makes sense.

The one-time work can include discovery, component development, content conversion, integration changes, verification, cutover and handover. The recurring work can include hosting, the CMS, forms, search, monitoring, dependency updates and support. Some services have free allowances; that does not make the complete setup free to operate.

Write down which account pays each bill, what usage could change the cost, and who responds when something fails. If the existing Webflow subscription overlaps with the new services during testing, include that temporary overlap too. It is easier to budget for an intentional transition than to discover duplicate invoices after launch.

A simple planning equation is:

First-year commitment = migration scope + twelve months of selected services + agreed maintenance + temporary overlap.

Use actual provider quotes and your expected usage to fill it in. Do not turn hypothetical hosting savings into a payback claim before including engineering time and the publishing experience your team will receive.

What should trigger a revised estimate?

A fixed scope needs a way to handle newly discovered work. Examples include a previously undocumented collection, a required integration that behaves differently from its documentation, or a decision to redesign campaign templates during the move.

The process should be explicit: describe the discovery, explain its effect, offer options and agree the adjustment before proceeding with the additional work. Sometimes the right option is to defer the feature. Sometimes a smaller implementation solves the immediate need. Sometimes the migration should include it and the schedule should change.

This is different from charging again for a promised outcome that was simply underestimated. If the agreed scope includes preserving a form's attribution fields, that responsibility should not vanish because those fields are harder to test than expected. Read the acceptance criteria alongside the exclusions.

A quote-review checklist you can use

A missing answer is a reason for a conversation, not automatic evidence of a bad supplier. What matters is whether the final agreement makes responsibility clear enough for both sides to assess completion.

Reduce uncertainty before trying to reduce price

The most useful preparation is a compact source package: collection names, representative exports, current integrations, important URLs and the publishing tasks that must remain possible. That lets a developer investigate the actual work instead of building a large allowance around unknowns.

If the budget is constrained, reduce scope deliberately. Preserve the design, defer unrelated features, consolidate redundant layouts where appropriate and agree which content is being retired. Avoid removing the verification that tells you whether the move worked. A smaller verified migration is a clearer purchase than a larger rebuild with its launch responsibilities left open.

Use the developer hiring questions to compare proposals and the timeline guide to understand how unresolved decisions affect delivery.

Want an estimate for your migration?

Send your current site, the platform it is on and the features you need to keep. I will review the scope and outline the likely work.

Request a migration estimate

Migrations from $5,000.