You have hit a Webflow limit that no plan tier removes. Preserve the design intent. Reassess the architecture.
Webflow is a strong visual tool. If what you need from content, interactions, application logic, speed, other languages or day-to-day running has moved on, we can compare the current site with a scoped replacement. What you pay, what support you get, who has access, which licences, who owns it and how it is handed over all get written down after discovery.
Drop your Webflow URL when you book. We can run a point-in-time diagnostic, review migration inputs, and identify what is needed for a written proposal.
Scope first, then commit in writing.
Look at what the account costs you today, and at who would run the replacement day to day. Availability incidents should be checked against Webflow's current status history; a different hosting architecture changes dependencies but does not eliminate outage risk. See the Webflow cost-input guide.
Compare vendors on the same scope: the same pages, design work, CMS, languages, commerce, integrations, testing, support and handover. Not on headline prices or generic benchmarks. The accepted proposal defines the commercial model and project-specific commitments.
Diagnostic discipline
A diagnostic is a point-in-time technical review, not proof of lost revenue or a guaranteed business result. We document the test context, distinguish observations from hypotheses, and flag when a migration may not be justified.
Evidence before outcomes
Public URLs can be inspected as implementation references, but they do not by themselves verify a client relationship, historical performance, revenue, costs, or commercial terms. Outcome claims require dated, client-approved source records and a reproducible method.
Record the page set, tool, device, network, date, and repeated runs.
Define scope, assumptions, exclusions, price model, and changes.
State support, access, licensing, ownership, and remedies explicitly.
When to Reassess Webflow
Not every Webflow site needs to migrate. These signals justify discovery, not a predetermined platform decision:
Account Economics Need Review
Before comparing anything, list what you pay for now: the site plan, workspace seats, languages, the store, apps, bandwidth, support and maintenance.
Required Logic Relies on Extensions
Map authentication, payments, databases, real-time data, and third-party tools, then compare supported Webflow paths with a custom architecture.
Content Model Is Under Pressure
Review current collection limits, relationships, localization, editorial workflows, exports, and growth assumptions against current provider documentation.
Website and Application Needs Are Converging
Dashboards, portals, role-based access, and live data may require application architecture. Discovery should validate the exact workflows and security requirements.
Portability Is Unclear
Test exports and document domains, assets, CMS data, code, credentials, repository access, licensing, and handover before choosing a migration path.
Discoverability Needs Evidence
Audit crawlability, rendering, entity clarity, structured data, content quality, and source credibility. Search and AI systems control indexing, rankings, and citations.
Product capabilities and retirement dates can change. If gated content or login flows matter, confirm the current status in Webflow's official documentation and inventory your implementation before relying on our overview of membership migration questions.
Map Hosting and Service Dependencies
Review Webflow's current official status history when availability matters to the migration case. Status records are time-sensitive and should be read in their original context.
An incident does not establish a specific revenue or lead loss without the business's own traffic, transaction, attribution, and recovery data. Document critical journeys and an evidence method before estimating impact.
Third-party monitors such as IsDown may provide additional signals, but their classifications and windows require verification. Use current provider records, your own monitoring, and the agreed service requirements.
A custom deployment introduces a different set of hosting, DNS, CDN, data, monitoring, and operational dependencies. The architecture and proposal should state responsibilities, recovery controls, support, and acceptance without promising uninterrupted availability.
Examples of Issues to Investigate
These posts describe individual experiences and are not representative performance or pricing evidence. Follow the links for context, then verify relevant issues against your own account and current provider documentation.
One agency participant described friction in configuring a simple editing workflow for clients.
A participant questioned the workspace economics for small client sites with limited editing needs.
One community participant described a hosting-cost concern for a high-bandwidth site; verify the original context and current pricing.
The same participant contrasted Webflow's design capabilities with the economics of an all-in-one agency service.
Use anecdotes to form questions, not conclusions.
A migration assessment should verify editor workflows, CMS exports, interactions, localization, ecommerce, account costs, performance, and third-party terms. Any white-label arrangement, price, timing, support, confidentiality, access, ownership, or remedy belongs in the written proposal.
Get your migration plan →Webflow vs Custom Coded
Compare current constraints with a project-specific architecture and operating model.
How We Migrate Your Webflow Site
A four-phase planning and delivery path. The proposal identifies included interactions, content, dependencies, milestones, and acceptance checks.
Webflow Inventory
We review structure, pages, components, interactions, collections, assets, forms, domains, localization, ecommerce, and integrations.
Architecture & Design Mapping
We define what is retained, redesigned, rebuilt, transformed, or excluded, including content, responsive states, accessibility, and technical dependencies.
Implementation & Data Validation
We build the approved scope in reviewable increments and verify migrated content and integrations against agreed samples and checks.
Cutover & Handover
We follow the agreed deployment, DNS, redirect, analytics, monitoring, rollback, access, licensing, documentation, and support plan.
Define What the Replacement Must Do.
A custom implementation can provide different application, content, and deployment controls. The proposal defines measurable targets, recurring services, support, repository access, licensing, IP, and handover.
Measured Experience
Define visual, responsive, accessibility, and performance acceptance checks for representative pages and interactions.
Scoped Application Logic
Assess authentication, payments, data, and API integrations against security, provider, and operational requirements.
Documented Operating Model
Estimate hosting and connected services, then state maintenance, support, repository access, licensing, and handover responsibilities.
What Webflow costs
The list prices, read off Webflow's own pricing page
Most of the numbers you will find for this are second-hand. These were read in a browser on 2026-08-05, on the billed-yearly view. We publish the date because a price without one is a guess, and Webflow changes these.
| Plan | List price | What the number does not say |
|---|---|---|
| Basic | $15 a month | billed yearly, per site, plus tax; custom domain, 300 static pages, 10 GB bandwidth. The monthly-billing toggle did not re-render when this was read, so no monthly figure is verified |
| Premium | $25 a month | billed yearly, per site, plus tax; the tier that adds the CMS, site search and code components. Previously named the CMS plan |
| Team | $2,500 a month | annual contract required. This is a platform plan, charged on top of the per-site plans, not instead of them. Google's AI Overview stated this as $2,500 a year when checked |
| Optimize add-on | $299 a month | priced by page views, and charged separately from the site plan |
| Localize Essential add-on | $9 a month | covers 1 to 3 locales in total, not $9 per locale. Localize Advanced is $29 a month for 1 to 10 |
| Analyze add-on | $9 a month | priced by sessions, and charged separately from the site plan |
All figures per site, plus applicable tax, on the billed-yearly view, read at webflow.com/pricing on 2026-08-05. Monthly-billing figures are not listed because the monthly toggle did not render when these were read, and we do not publish a number we did not see.
The Team plan is the line most budgets get wrong
When we checked, Google's AI Overview reported the Team plan at $2,500 a year. Webflow's own pricing page says $2,500 a month, on an annual contract. A team planning from the first number under-budgets that line by twelve times.
Two smaller ones travel with it. Team is a platform plan, charged on top of the per-site plans rather than instead of them, so a multi-site setup pays both. And Localize Essential at $9 a month covers one to three locales in total, not $9 for each one.
What a 50 to 100 page migration actually turns on
This is the question we are asked most, and page count is the least useful part of the answer. Four things move the number, and all four are knowable before anyone quotes you.
How many templates, not how many pages
Two hundred pages built from eleven templates is a smaller job than forty pages each laid out by hand. Count the distinct layouts before you count URLs.
How much of the CMS is relational
Flat collections port cleanly. Multi-reference fields, nested collections and anything driving conditional visibility have to be modelled again, and that is design work rather than export work.
What the interactions are load-bearing for
A scroll animation is decoration. An interaction that gates a form step or drives a pricing calculator is application logic in an animation costume, and it gets rebuilt.
Which integrations hold state
Embeds are cheap to move. Anything storing member data, orders or submissions inside Webflow needs an export path confirmed before a date is agreed, not after.
What continues to cost money after you leave
A migration removes the Webflow site plan. It does not remove every line, and a comparison that pretends otherwise is selling you something. The recurring cost usually falls. It does not go to zero.
- Hosting, which for a static marketing site is often materially cheaper, and occasionally free at low volume.
- The CMS, if you take one. Some are free at your size, some are per-seat, and the seat count is what moves it.
- Anything Webflow was bundling that you were not costing separately: forms handling, search, localization, analytics.
- Maintenance. Dependency updates and security patching do not disappear because the platform did. They change hands.
One argument on this site that has weakened
Several of our own guides describe Webflow as a closed system a serious operator eventually outgrows. That is less true than it was. As of the same pricing read, Webflow lists an MCP server and Webflow AI on every tier including the free one, ships app hosting, and markets itself as an AI-native platform. If the reason you are considering a move is that Webflow cannot talk to anything, check that assumption before you spend money on it. The access, cost and ownership questions above stand on their own.
Start with evidence. Put the agreement in writing.
Discovery is used to understand the current system, desired outcome, constraints, and dependencies. Scope, commercial terms, targets, support, ownership, and remedies become commitments only when they are stated in accepted written project terms. Those may be a concise quote or order summary accepted in email or chat, or a more detailed agreement for regulated or complex work.
Diagnostic first
We begin with the URL, stack, content, integrations, analytics, and operational constraints. Automated audit output is treated as an estimate to investigate, not proof of revenue loss or a guaranteed business result.
Evidence before outcomes
Performance measurements and project examples are point-in-time references. Any target used for your project should identify the tested pages, tool, date, device profile, run method, exclusions, and acceptance rule in the written scope.
Scope before certainty
The proposal says what is included, what is not, what we need from the client, what it depends on, and how changes get approved.
Targets need a method
If there is a performance or visibility target, we write down how it gets measured and what happens if it is missed.
Terms belong in the proposal
Payment milestones, support coverage, ownership, licenses, handover, and out-of-scope work are confirmed in writing.
What should be documented before work starts
Use the discovery conversation to gather evidence, then rely on the written proposal for commitments.
← Swipe to see more →
| Review area | During discovery | In the written proposal |
|---|---|---|
| Scope and exclusions | List what they have today, what it depends on, and what we are assuming | Say what is included, what is not, who does what, and how changes get handled |
| Performance and acceptance | Record a dated baseline, and name what only the client can change | Agree the target, which pages, which tools, the test conditions, and how it gets signed off |
| Commercial and handover terms | Talk through payment, support, ownership, access, and what happens at handover | State the milestones, what support covers, the licences, the handover, and what happens if something is wrong |
If a commercial term, target, or remedy is not in the written project terms accepted by both parties, this page should not be read as creating that commitment.
Scope and Commercial Review
Choose a planning path. Confirm the project in writing.
These are here to shape the first conversation. They are not quotes and not delivery promises. The scope, price, timing, tests, support, ownership and remedies are stated in the accepted written project terms, which may be a concise quote or order summary or a more detailed agreement.
Before Discovery
Working assumptions
We still have to look at the features, the integrations, the content, what could go wrong in the migration, and what it depends on.
After Discovery
Written proposal
The approved scope is where we write down what we committed to, what we assumed, what is excluded, the milestones, and how you sign it off.
Scope option
Starter
We review what this actually needs before committing to anything commercially or on delivery.
- What you get, what you do not, and what we need from you
- What we are waiting on, how you sign it off, and how changes get approved
- When you pay, what support you get, who owns it, which licences, and how it is handed over
Scope option
Growth
We review what this actually needs before committing to anything commercially or on delivery.
- What you get, what you do not, and what we need from you
- What we are waiting on, how you sign it off, and how changes get approved
- When you pay, what support you get, who owns it, which licences, and how it is handed over
Scope option
Scale
We review what this actually needs before committing to anything commercially or on delivery.
- What you get, what you do not, and what we need from you
- What we are waiting on, how you sign it off, and how changes get approved
- When you pay, what support you get, who owns it, which licences, and how it is handed over
Examples on a website are not a quote. Third-party fees, what we need from you, migration risk and anything out of scope get identified during discovery and documented in the proposal.
Improve the current system, or plan the migration.
Webflow Optimization
Not ready to leave Webflow? We can audit the current site and scope feasible improvements within its account, editor, script, content, and integration constraints.
- Performance optimization
- SEO improvements
- CMS restructuring
- Interaction refinements
Migrate to Custom Code
Scope a replacement implementation around the required design system, content model, application logic, performance method, and operating responsibilities.
- Documented performance budgets
- Scoped server-side requirements
- Validated content model
- Written repository and rights terms
- Current hosting and service estimate
- Written support and remedies
Frequently Asked Questions
Straight answers. No sales fluff.
What editing feels like depends on which CMS you pick, who is allowed to do what, whether they can preview, how publishing flows, and how content is structured. Discovery compares those requirements with Webflow's current editor and records any training, maintenance, or developer dependency in scope.
We can inventory Webflow interactions and evaluate equivalent or revised implementations. Feasibility, accessibility, reduced-motion behavior, browser support, assets, and acceptance criteria are defined for the approved interactions.
We can map your Webflow collections, fields, references, assets, languages, slugs and publishing flow onto a CMS that fits. Export coverage, provider limits, data cleanup, API access, and migration verification vary by project and provider.
Price and timing depend on how many pages there are, the design system, the interactions, the CMS data, the languages, whether you sell, what it connects to, the redirects, and how you sign it off. The written proposal states the commercial model, milestones, assumptions, support, access, licensing, ownership, and remedies.
It is possible, and platform capabilities change. The decision should use current Webflow documentation, your actual account and roadmap tolerance, and a like-for-like comparison of implementation and operating responsibilities.
Define the migration and acceptance method.
The accepted proposal states the page set, test conditions, redirect and data checks, client responsibilities, accessibility criteria, support, access, licensing, ownership, handover, and any remedies. This page does not create a performance or refund promise.
Explore More Services
Compare the scope, dependencies, and trade-offs for each service path.
Wix Migration
Map content, integrations, DNS, and a feasible migration scope.
Squarespace Migration
Review content, commerce, scheduling, and migration requirements.
Custom Engineering
Scope applications, dashboards, APIs, permissions, and integrations.
WordPress Migration
Inventory plugins, content, redirects, and migration dependencies.
Shopify (Headless)
Review frontend architecture while retaining compatible commerce workflows.
WooCommerce Migration
Assess checkout, plugin dependencies, store data, and migration options.
GoHighLevel
Evaluate a custom public frontend alongside compatible CRM workflows.
For Agencies
Discuss delivery roles, confidentiality, and terms in a partner agreement.