Webflow migration
Webflow Migration Cost: Scope, Tiers and Evidence
Moving a site off Webflow onto a custom build starts at $1,500 with PandaCodeGen, $3,500 for a larger marketing site, and $5,000 to $10,000 where templates, CMS or integrations multiply. Those are our prices, not a market average. What decides which one you land in is rarely page count. It is how many distinct templates hide behind those pages, how your CMS collections reference each other, which features Webflow will not export at all, which systems have to keep talking to each other afterwards, how the URLs get mapped so the search traffic survives, and what you have to see before you sign it off.
Every Webflow figure on this page was re-checked against Webflow's own pricing page and help centre on August 2, 2026.
Hassan Jamal·Mar 25, 2026·12 min read
The short answer
- ✓PandaCodeGen's public planning tiers start at $1,500 Starter, $3,500 Growth and $5,000 to $10,000 Scale.
- ✓For a 50 to 100 page site we quote after sorting out how many templates you really have and tidying the content, not by multiplying one page price by 100.
- ✓Webflow's code export gives you the front end, not the whole application. Your CMS, store, forms, search, other languages and anything behind a login all need separate work.
- ✓The signed scope is where the final price, the schedule, who owns what, how you sign it off, support and refund terms all live.
Pages
How many templates you really have, not how many pages.
Systems
Your CMS, forms, search, store, logins and anything they connect to.
Acceptance
How you sign it off: content is right, it works, it ranks, people can use it, it is fast.
Operation
What you pay providers, plus support and your own team's time.
Which move are you actually making?
This page prices moving off Webflow onto a custom build. Two different jobs get called a “Webflow migration” and they do not cost the same. Rebuilding an existing site into Webflow is a build on a new platform. Moving off Webflow onto code you own is the one with real engineering in it, because the CMS, forms, search, localization and anything gated do not transfer, they get reproduced, and the URLs have to be mapped so the search traffic survives.
This is also why published Webflow migration ranges look so inconsistent. A range that mixes a rebuild into Webflow with a replatform off Webflow is describing two jobs with one number. For the same distinction across every platform we work with, see our website migration cost guide.
The four planning tiers for a Webflow migration
Four tiers, and the column that decides which one you land in is the last one: what can move it. A Webflow migration climbs a tier when the CMS reference graph gets complicated, when something has to be rebuilt because Webflow will not export it, or when more systems have to keep talking to each other after launch. It rarely climbs because there are more pages.
| Tier | Starting point | Potential fit | What can move it |
|---|---|---|---|
| Starter | $1,500 | Small, well-defined migration with limited templates and integrations | CMS, content cleanup, forms, redirects and custom behavior |
| Growth | $3,500 | Larger marketing site or migration with structured content | Design change, complex CMS, analytics, localization and integrations |
| Scale | $5,000 to $10,000 | Multi-template, integration-heavy or higher-risk migration | Commerce, user systems, custom applications, data and governance |
| Custom | Scoped separately | Requirements outside the standard tiers | Program size, compliance, multiple markets, complex data or ongoing team |
They are not market medians, paid-project receipts, competitor quotes or a promise that every site fits a tier. A proposal is valid only for its written scope and date.
The same tiers are set out with their inclusions on the pricing page, and the delivery process behind them is described on our Webflow migration service page. If this article and the pricing page ever disagree, the pricing page is correct.
Why published Webflow migration ranges span more than 10x
Search this and you will be told a Webflow migration costs somewhere between a few thousand dollars and the high five figures. That range is real, and it is useless, because it averages four different jobs into one number. A code export dropped onto new hosting, a like-for-like rebuild, a rebuild with a new content model, and a replatform that also changes what the site does are not variations in size. They are different projects, and only the last two are affected much by page count at all.
Three things collapse the range to something you can plan against, and none of them is the number of URLs. How many genuinely distinct templates and states exist, as opposed to how many pages use them. How much of the content moves by export and how much has to be rebuilt by hand, which is decided by what Webflow will and will not hand you. And how many connected systems have to keep working on the other side. Price those three and the quote stops being a range.
One line worth adding to the recurring column while you are here: Webflow bills Workspace seats separately from Site plans, so the cost of the people who edit the site is not included in the hosting figure most comparisons quote. Read the current seat pricing from Webflow's own pricing page for your own team size rather than from a summary, including this one.
Webflow migration cost for a 50 to 100 page website
Most sites this size land in our Growth or Scale tier, so $3,500 to $10,000, and which end depends on template count rather than URL count. Fifty URLs can be five templates repeated with different content, or fifty unique layouts with their own interactions, and those are not the same job. Count templates before you budget.
In Webflow's own vocabulary the unit that costs money is the Collection, not the Collection item. A Collection needs its fields defined, its Collection page template built, its Collection lists placed and its reference fields wired to whatever else points at it. That work happens once. The three hundred posts inside it are data and travel with the import. It is why a blog, a case-study library and a team directory can cost more between them than four hundred pages sitting inside any one of them, and why pricing per page measures the wrong thing in both directions.
Build a route inventory that assigns every URL to a template, content source, language, canonical, redirect disposition and acceptance test. Normalize repeated patterns before estimating.
- ✓Static pages grouped by shared layout and component coverage.
- ✓Your CMS collections, the fields in each, how they reference one another, the slugs, and how many items there are.
- ✓Assets, alt text, video, downloads and image transformations.
- ✓Forms, notifications, spam controls, file uploads and historical submissions.
- ✓Search, gated content, ecommerce, localization and custom scripts.
- ✓Metadata, canonicals, structured data, internal links and redirects.
- ✓Review rounds, content owners, approvals and launch dependencies.
A 50 to 100 page site can fit a standard tier when it collapses into a small set of clean templates. It can also exceed Scale when pages are unique, content is inconsistent or multiple business systems must be replaced. The inventory, not the URL count alone, decides.
Enterprise Webflow migration pricing
Enterprise Webflow work carries two price tags and they are set in different places. Webflow publishes the platform side: Team is $2,500/mo on an annual contract, and Enterprise is quoted on request with no figure published anywhere on webflow.com, read August 2, 2026. The migration side is not published by anyone, ours included, because at this size the cost is governance rather than pages. Our Scale tier starts at $5,000 to $10,000 and enterprise programs are scoped separately against the workstreams below.
Enterprise work adds governance, not just pages: who someone is, what they are allowed to do, other languages, security review, legal approval, design-system ownership, multiple repositories or sites, deployment environments, release management, observability, incident response and procurement. These requirements should be priced as explicit workstreams with named acceptance evidence. Where the target site is closer to an application than a brochure, that work sits under custom engineering rather than a standard migration tier.
What factors increase the cost of a Webflow migration project?
Six things move a Webflow migration up a tier: the number of genuinely distinct templates, the shape of the CMS reference graph, anything Webflow will not export (ecommerce, localization, search, gated content), the integrations that have to keep working on launch day, the state of the content itself, and the number of people who have to approve it. Page count is the weakest predictor on that list.
- ✓More unique templates, components and responsive states.
- ✓CMS reference graphs, rich text embeds, localized fields and inconsistent content.
- ✓Ecommerce catalog, checkout, orders, subscriptions, tax, fraud and customer accounts.
- ✓Forms, search, membership, personalization, experimentation and custom code.
- ✓CRM, marketing automation, analytics, consent and advertising integrations.
- ✓New information architecture, visual redesign, copywriting or asset production.
- ✓Accessibility remediation and regulated privacy or security requirements.
- ✓Compressed schedules, delayed content, additional reviewers or unclear decision rights.
One of those deserves pulling out, because it is the most common reason two quotes for the “same” site differ by more than double: whether you are reproducing the current design or changing it. A visual replica is an engineering job with a fixed reference to test against, so every page has a right answer both sides can see. A redesign delivered inside the same project adds discovery, design rounds, copy decisions and approvals, and it removes the reference that made acceptance objective. Both are legitimate work. Buying them as one line without saying which you mean is what produces the argument at sign-off, so decide before you brief rather than during review.
What Webflow actually exports
Webflow's current code-export documentation says paid Workspace plans can export HTML, CSS, JavaScript and assets, and states directly that Site plans do not include the ability to export your site's code. That catches people out: paying Webflow monthly for hosting does not, on its own, entitle you to the code. It also says the exported code excludes CMS databases and functionality, User Accounts, ecommerce databases and functionality, localized content beyond the primary locale, code components, password protection, form processing, existing form submissions, reCAPTCHA elements inside forms and site search. Collection lists render their empty state and Collection pages show nothing bound to a Collection field. User Accounts is a particular trap here because the product itself was withdrawn; we walk through the consequences in our guide to the Webflow User Accounts sunset.
CMS collections, ecommerce collections and User Accounts can each be exported separately as CSV, localized Collection content included. That is data, not a working target application. The migration still needs schemas, relationships, media, transformations, validation, preview and publishing behavior.
What does it actually cost to move the content?
Usually far less than a per-page rate implies, and you can prove it on your own content in about twenty minutes. Published estimates for a Webflow migration often price content at $15 to $50 per page, which assumes somebody retypes it. Webflow's own CMS import documentation says the opposite is normal: CSVs exported from other content management systems “like WordPress are already structured in a way that's compatible with Webflow”, hundreds or thousands of items import in one pass, and CSV values map to reference fields during that import. Content that imports cleanly should not be billed by the page.
A per-page rate becomes honest only where the import genuinely breaks, and Webflow names those cases itself. Open your own export and check these six columns before you accept any content line in a quote. Read on August 2, 2026 against Webflow's CMS import article.
- ✓Rich text has to arrive as HTML. A body column exported as plain text, or as another editor's markup, is rework on every single row.
- ✓Image fields need a direct URL ending in an image extension, and Webflow tells you to run that column through a bulk URL checker first, because a broken link cannot be mapped at all.
- ✓Video fields accept YouTube and Vimeo URLs only. Self-hosted video does not map, so those pages get rebuilt by hand.
- ✓Number fields reject $100, 100 USD and 10,000. Currency symbols, unit labels and thousands separators have to be stripped before the column will map.
- ✓File fields take no imported data whatsoever. Every PDF, spec sheet and download is manual work, whatever the page count says.
- ✓Option fields cap at 100 distinct values, so a sprawling free-text category column has to be normalized before it can become a field.
The same article carries the trap that catches multilingual sites: an exported CSV contains only the items from the locale you are currently viewing. A site in four languages is four exports and four import passes, which is a scope question rather than a page-count question. If every column above passes, ask for content to be priced as one scripted pass instead of per page. If several fail, you now know which ones, and that conversation is about specifics rather than a haggle.
What a professional migration should include
Nine workstreams, and the test of a quote is whether it names them rather than whether it is expensive. Three get assumed most often: the functional states nobody demos, the accessibility checks, and the rollback plan. A quote listing deliverables but no acceptance evidence has priced the building and not the proving.
- ✓Discovery, inventory, dependency map and accepted target architecture.
- ✓Page, component, CMS, content, asset and integration migration.
- ✓Functional states including errors, validation, empty states and permissions.
- ✓Responsive implementation for agreed devices and browsers.
- ✓Accessibility checks against the agreed standard.
- ✓Analytics, consent, tag and conversion-event validation.
- ✓SEO inventory, rendered-output checks, URL mapping, redirects and sitemap.
- ✓Security configuration, credential handling and account ownership.
- ✓QA evidence, rollback plan, cutover, monitoring, handoff and support.
What may not be included in a standard quote
Ask for exclusions in writing. Common separate workstreams include new brand strategy, photography, video, net-new copy, data cleansing, custom product development, complex integrations, translations, legal or compliance advice, paid vendor plans, email and DNS coordination, and ongoing growth work. An exclusion is not a problem when it is visible before signing. The URL mapping and redirect workstream is the one most often assumed rather than quoted, and what a migration does to your search rankings explains why it deserves its own line.
How to compare migration quotes without calling one padded
A higher quote may include more work or a different risk allocation. Normalize each proposal line by line before comparing price. Do not infer padding, overcharging or equivalent scope without the underlying statements of work.
- ✓Same route and template inventory.
- ✓Same design and content responsibilities.
- ✓Same CMS, data, form, search and integration requirements.
- ✓Same SEO, accessibility, security and performance acceptance.
- ✓Same provider fees, support period, warranty and maintenance.
- ✓Same ownership, licensing, account and handoff terms.
Who should you hire?
Four delivery models, and the column worth reading is the third: what stays your problem in each case. An independent specialist leaves you owning project management and continuity. A studio or an agency absorbs that and charges you for it. An internal team owns all of it, including the cost of whatever they stop doing while the migration runs.
| Model | Useful when | Buyer must own or verify |
|---|---|---|
| Independent specialist | Scope is narrow and internal direction is strong | Design, project management, QA, continuity and release |
| Migration studio | A defined site needs accountable end-to-end delivery | Relevant evidence, capacity, terms and handoff |
| Full-service agency | Brand, content, marketing and engineering must move together | Named team, workstream coordination and comparable scope |
| Internal team | The organization has product, design and engineering capacity | Opportunity cost, migration expertise and launch ownership |
Whichever model you pick, ask to see finished builds rather than a capability list. Ours are documented in our project case studies, and the people who do the work are named on our about page.
How much does it cost to host a Webflow site?
Read on Webflow's own pricing page on August 2, 2026: Site plans are Starter at $0, Basic at $15/mo billed yearly and Premium at $25/mo billed yearly, all quoted per site in USD before tax. Basic is described as being for “simple sites that don't need a CMS” and carries 300 static pages and 10 GB of bandwidth, so a single Collection puts you on Premium. Platform plans start at Team, $2,500/mo on an annual contract, with Enterprise quoted on request. Selling adds a separate Ecommerce plan: Standard $29/mo with a 2% transaction fee, Plus $74/mo and Advanced $212/mo at 0%. Add-ons sit on top and are priced by usage: Optimize from $299/mo, Analyze from $9/mo, Localize from $9/mo.
That is the platform line, and it is the smaller half of the comparison. Leaving Webflow does not mean zero recurring cost either. Build the target budget from hosting, bandwidth, builds, CMS, database, forms, email, search, analytics, monitoring, backups, security, domains, support and internal time. Use current provider terms and a realistic usage scenario. Free allowances can change and may not fit commercial operation. Our breakdown of what Webflow costs once every line is counted sets out the categories to carry across, and what Next.js hosting actually costs to run does the same for the target side.
The two models do not carry the same cost lines at all, which is why holding one monthly number against another tells you very little. Build both columns from your own current invoices. Webflow reorganizes this lineup more often than most vendors, so re-read every figure above on the day you budget, with the monthly and yearly toggle set the way you actually intend to pay.
| Cost line | On Webflow | On a custom Next.js build |
|---|---|---|
| Platform / hosting | Site plan, plus a workspace seat cost if more than one person edits | Host plan; can start on a free allowance but commercial use usually needs a paid tier |
| CMS | Premium is the cheapest plan carrying the full CMS on a custom domain; Basic is described as being for simple sites that do not need a CMS, and the free Starter plan's limited CMS sits on a webflow.io subdomain | Separate service or self-hosted; priced by documents, seats or usage |
| Ecommerce | Plan upgrade where applicable | Commerce backend or payment provider fees, billed separately |
| Forms and email | Included from the paid Site plans up; the free plan is capped at 50 submissions | Form handling and transactional email provider |
| Bandwidth / builds | Included within plan allowances | Metered above the plan allowance; depends on traffic and build frequency |
| Search, analytics, monitoring | Native or third-party add-ons | Chosen per tool; several have usable free tiers |
| Maintenance | Platform handles updates and security | Yours or your vendor's: dependency updates, patching, monitoring |
| Exit cost | Export is partial; some features do not come with you | You hold the source, so moving host is a redeploy |
Maintenance. On Webflow it is bundled into the plan price and effectively invisible. On a custom build it is real work that either you do, or you pay someone to do, or nobody does. A comparison that ignores it will always make custom look cheaper than it is.
If you are still deciding whether to move at all rather than how much it costs, Webflow versus a custom website compares the two operating models directly, and why teams are leaving Webflow in 2026 covers the triggers that usually start the conversation.
Measure performance separately from rankings
Webflow has no universal PageSpeed ceiling, and custom code has no automatic 90-plus result. Test representative routes under recorded mobile and desktop conditions and inspect field Core Web Vitals where available. Google says good Core Web Vitals support page experience, while relevance and many other signals still affect search. Do not convert a lab-score change into a promised ranking or revenue result. For what the individual metrics mean and how to read them, see Core Web Vitals explained and how site speed relates to search performance.
Treat availability as a requirement, not an outage anecdote
An incident count taken over a fixed window is volatile evidence and cannot settle a migration decision on its own. If availability matters, define the required service level, dependencies, monitoring, backup, recovery objective, incident response and remedy for both current and target systems.
When does a Webflow migration pay for itself?
There is no universal payback period. Compare the migration and ongoing cost with current invoices, support, internal work and measurable business constraints. Model low, central and high scenarios. After release, compare actual costs and outcomes without attributing every change to the migration. For the cross-platform view of how these budgets are built, see our website migration cost guide.
How to get an accurate quote
Spend twenty minutes counting before you brief anybody and the quotes come back comparable instead of as a range. Everything below is already inside your own Webflow account. A provider holding these seven things can price the work; one without them is estimating, and the estimate is what turns into a variation later.
- ✓Open the Pages panel and count the pages, then count them again by layout. The second number is the one that prices the job.
- ✓List every CMS Collection, the fields in each and the reference fields between them. The Collection is the cost unit, not the items inside it.
- ✓Note every third-party integration the site talks to, and mark which have to work on launch day rather than the week after.
- ✓Say whether anything is gated, localized, searchable or sold, because those are the four things Webflow will not export.
- ✓Name the content owners, the approvers and how many review rounds the schedule assumes.
- ✓State who should own the repository, hosting, CMS and domain at the end, and give read-only access or exports so nobody estimates blind.
- ✓Ask for assumptions, exclusions, milestones, acceptance evidence, change control and support in the proposal itself, with vendor fees and third-party licenses separated from the agency price.
PandaCodeGen commercial terms
A common payment option is 30 percent at onboarding and 70 percent at the delivery milestone, and another written schedule may be agreed. A refund is tied to failure to deliver the signed scope, not a change of preference after work begins. Starter includes 15 business days of launch defect support; Growth and Scale include 30 business days. Custom deliverables transfer after full payment under the contract. PandaCodeGen retains reusable tools and pre-existing code, and third-party components keep their licenses.
Frequently asked questions
Frequently Asked Questions
How much does Webflow migration cost in 2026?
PandaCodeGen's planning tiers start at $1,500 Starter, $3,500 Growth and $5,000 to $10,000 Scale, with custom work scoped separately. Final price depends on templates, CMS, export gaps, content, integrations, SEO, accessibility, QA, cutover and support.
What factors increase the cost of a Webflow migration project?
Unique templates, CMS relationships, localization, interactions, ecommerce, membership, forms, search, integrations, content cleanup, redesign, accessibility, security, SEO, compressed schedules and additional reviewers can all expand scope. Quantify them from the live inventory.
What are the ongoing costs after a Webflow migration?
Include hosting, bandwidth, builds, CMS, database, forms, email, search, analytics, monitoring, backups, security, domains, support and internal time. Free allowances are not permanent commercial-cost promises, and exact cost depends on the chosen providers and usage.
How much should we budget for a Webflow migration for a 50 to 100 page site?
Most sites this size land in PandaCodeGen's Growth or Scale tier, so $3,500 to $10,000, and which end depends on template count rather than URL count. Fifty URLs can be five templates repeated with different content or fifty unique layouts, and those are not the same job. Group the URLs into templates and CMS Collections before budgeting. These are our prices, not a market average.
How much does it cost to host a Webflow site?
Read on Webflow's own pricing page on August 2, 2026: Site plans are Starter at $0, Basic at $15/mo billed yearly and Premium at $25/mo billed yearly, quoted per site in USD before tax. Basic is for sites that do not need a CMS, so a single Collection puts you on Premium. Platform plans start at Team, $2,500/mo on an annual contract, and Enterprise is quoted on request. Ecommerce is a separate plan at $29, $74 or $212/mo, and Optimize, Analyze and Localize are usage-priced add-ons on top.
Do I have to pay per page to migrate my content?
Usually not, and you can check it yourself in about twenty minutes. Webflow's CMS import documentation states that CSVs exported from other content management systems like WordPress are typically already compatible, and that hundreds or thousands of items import in one pass. A per-page rate is only honest where the import genuinely breaks: rich text that is not HTML, image columns with broken or non-direct URLs, self-hosted video, number columns containing currency symbols or thousands separators, file fields which accept no imported data at all, and option columns with more than 100 distinct values.
Will I lose my Google rankings when migrating from Webflow to Next.js?
Webflow slugs are yours already, so the URL mapping is often lighter here than on Wix or Squarespace. The risk sits in what does not export: Collection-driven pages, localized content, site search and gated areas are rebuilt rather than transferred, and a rebuilt template is where content quietly goes missing. Diff the rendered output route by route.
How long does a Webflow migration take?
Weeks rather than months, set by template count and by how much of the site does not export. Your Webflow site keeps running throughout, so the pressure is on approvals rather than downtime. The cutover itself is short; what takes time is testing that every rebuilt Collection template renders what the original did.
Primary sources
- Webflow pricing
- Webflow site plans
- Webflow code export
- Webflow CMS import and export
- Webflow exported forms
- Webflow User Accounts sunset
- Webflow feature sunsets and deprecations
Get your Webflow migration plan
We will inventory templates, CMS, exports, integrations and SEO risk before proposing a tier. Extra pages or features can be discussed against the same written scope.
Related Articles
Webflow User Accounts Sunset: January 29, 2026 Recovery Guide
What Webflow officially removed, how unmigrated accounts, data, gates and subscriptions were affected, and how to scope a recovery or replacement.
Leaving Webflow in 2026: Stay, Optimize, or Migrate?
A current framework for leaving Webflow: pricing and bandwidth changes, export limits, total cost, performance diagnosis, and an SEO-safe migration plan.
Webflow vs Custom Website in 2026: A Four-Factor Decision
Choose using editing, requirements, ownership and lifecycle responsibility, with current export, pricing, SEO and performance limits.