Moving from Webflow to WooCommerce
Webflow's published ceilings run from 500 ecommerce items at $29 a month with a 2% fee to 15,000 items at $212. Products, variants and categories all count toward those limits.
This migration is unusual in one respect that shapes the whole project: the design is usually worth keeping. Stores leaving WoodMart or WPBakery want the old look gone. Stores leaving Webflow generally spent real money on a designer, like the result, and are moving because of a limit rather than a disappointment. That changes the brief from "rebuild the storefront" to "reproduce this storefront on a system that does not cap us", and it changes who should do the work — you need someone who can read a Webflow design and rebuild it faithfully, not someone who will hand you a theme.
The ceilings are published, so check which one you are hitting
Webflow's current plans count ecommerce items, not products alone: products, variants and categories share the allowance. Standard at $29 a month permits 500 items and adds a 2% Webflow transaction fee on top of payment processing; Plus at $74 permits 5,000 items with no Webflow fee; Advanced at $212 permits 15,000. A catalog with 400 products can therefore exceed Standard if variants and categories push the combined count past 500. A fee problem may be solved by moving to Plus. A count above 15,000 is not solved by any self-serve ecommerce plan. A capability problem — subscriptions or a workflow Webflow does not support — needs a separate comparison rather than being disguised as a product-count problem.
- Standard: $29/mo, 500 ecommerce items, 2% Webflow fee
- Plus: $74/mo, 5,000 ecommerce items, no Webflow fee
- Advanced: $212/mo, 15,000 ecommerce items, no Webflow fee
- Products, variants and categories all consume the item allowance
Run the 2% arithmetic before anything else
On Standard, Webflow's 2% sits on top of Stripe or PayPal processing, so $200,000 a year hands over $4,000 for the platform fee alone. Plus costs $540 more per year and eliminates it — below roughly $27,000 in revenue Standard is genuinely cheaper, above it Plus pays for itself. Do this before commissioning anything: at $150,000 a year on Standard, most of the complaint disappears with a plan change.
The design is the asset — brief it that way
Webflow produces clean, well-structured output, and the visual work behind a Webflow store is usually the most valuable thing in the project. A migration should treat it as a specification rather than a starting point for someone's opinion. In practice that means capturing the design system first — type scale, spacing rhythm, colour tokens, breakpoint behavior, interaction timings — and rebuilding it as components before touching a single page. Webflow's interactions are the part most often lost: scroll-triggered animations and page transitions have no automatic equivalent, and they need to be listed and individually costed rather than assumed.
CMS Collections do not map to products one-to-one
Webflow stores use two content systems that look similar and behave differently: Ecommerce products, and CMS Collections used for lookbooks, editorial, size guides and category landing pages. The CSV export handles products acceptably. Collections need their own export and their own modelling decision, because a Collection with reference fields to other Collections has a relational structure that a flat CSV loses. Export both, and check reference fields specifically — a lookbook that references six products by relation will export as six broken references unless someone plans for it.
What you actually give up
Three things get worse and it is only fair to say so. Hosting stops being someone else's problem: Webflow's included hosting, CDN and SSL become your responsibility, and a WooCommerce store on cheap shared hosting will be slower than the Webflow site it replaced. The visual editing workflow goes; a designer who was shipping page changes without a developer will now need either a page builder or a developer, and that is a real operating cost. And the security surface grows, because you now own plugin updates, PHP versions and backups. None of these is a reason to stay if you have hit a hard ceiling, but a migration quoted without them is quoted dishonestly.
URLs, and the redirect map Webflow makes easy
This part is more forgiving than most platform migrations. Webflow's URL structure is generally clean and slug-based rather than ID-based, so a large share of paths can be preserved exactly on WooCommerce. Product URLs typically sit under /product/ and category or collection pages under their Collection slug — both reproducible. Export the full URL list from Webflow plus twelve months of Search Console data, keep every path you can, and reserve redirects for the ones that genuinely change. Preserving a URL always beats redirecting it, and here you can preserve most of them.
When you should stay on Webflow
If your combined product, variant and category count fits the plan you can afford, if you do not need subscriptions or another missing commerce workflow, and if the design team ships changes without developer time, staying is the right answer. The same applies if nobody on your side will own WordPress maintenance afterwards — Webflow absorbs hosting, updates and security, and replacing that with an unmaintained WooCommerce install trades a visible limit for a risk you cannot see. Migrate when a ceiling is blocking revenue, not when a competitor mentioned they use WordPress.
How this one is sequenced
Design system first, since everything else depends on it — tokens, components, breakpoints, then the interaction inventory with a cost against each. Product import next, run against staging until counts and variants reconcile. CMS Collections after that, with reference fields resolved deliberately. Then hosting: get this decided early, because the wrong hosting choice undoes the entire performance argument for leaving. Launch with the URL map verified by a crawl, and keep the Webflow site published on a subdomain for a fortnight so you have something to compare against when a page looks wrong.
Frequently asked questions
What is Webflow's ecommerce limit?
Standard, Plus and Advanced allow 500, 5,000 and 15,000 ecommerce items. Webflow counts products, variants and categories in that allowance, so the number of products alone does not tell you whether a catalog fits.
Is the 2% transaction fee avoidable?
Yes, by moving from Standard to Plus. That costs about $540 more per year, so above roughly $27,000 in annual revenue the upgrade pays for itself and the fee stops being a reason to migrate.
Can we keep our Webflow design?
Yes, and it should be the brief. The design system is captured first — type scale, spacing, colour tokens, breakpoints — and rebuilt as components. Scroll interactions and page transitions have no automatic equivalent and need individual costing.
Do our URLs survive the move?
Mostly. Webflow uses clean slug-based paths rather than IDs, so a large share can be preserved exactly rather than redirected — which is always the better outcome.
Squarespace to WooCommerce
When a Squarespace store hits its commerce ceiling, what transfers, what has to be rebuilt, and how to protect the search traffic your content earned.
Wix to WooCommerce
What actually transfers when a store outgrows Wix, what breaks, how the URL structure changes, and how to keep search traffic through the switch.
Choosing a platform
There is no best ecommerce platform for a small business. Five honest questions decide it for you: maintenance, selling rules, content, fees and ownership.
See how many sales your store is losing
Start with a free speed audit. You'll get your store's real numbers and an honest recommendation — even if it's "you don't need us".