Webflow Ecommerce Migration: A Choice, Not a Deadline

The short answer

Webflow Ecommerce is not being retired. Webflow's own statement is that "Nothing is changing for the Ecommerce Site plans at this time," and the Ecommerce plans are still on the pricing page as of July 2026.

That matters because a lot of Webflow content right now is written in deadline language. Some of it is earned: User Accounts was sunset in January 2026, and the legacy Editor and whitelabeling go on 4 August 2026. Ecommerce is in neither set. Nobody is being pushed off it.

So this is a decision made on numbers and fit, and the honest version of the question is narrow: does what Webflow Ecommerce costs and caps still match the store you are running? If yes, stay. If no, the work below is what moving actually involves.

What Webflow Ecommerce costs and caps today

From Webflow's pricing page, verified July 2026. Ecommerce is an add-on to a Site plan, priced per site:

• Standard, $29/mo billed yearly. 500 ecommerce items. 2% transaction fee, which Webflow states is "in addition to Stripe or Paypal processing fees." 3 staff accounts.

• Plus, $74/mo billed yearly. 5,000 ecommerce items. 0% transaction fee. 10 staff accounts.

• Advanced, $212/mo billed yearly. 15,000 ecommerce items. 0% transaction fee. 15 staff accounts.

Two details in there decide most migrations, and both are routinely misread.

The item cap is not a product cap. Webflow defines it as "Products, variants, and categories your store can have, independent of your CMS item limit." A store with 100 products averaging four variants, plus categories, is already close to the 500 ceiling on Standard while looking like a 100-product store. Count variants before assuming you have headroom.

The 2% on Standard is the real cost step. It sits on top of your processor's fees, and it disappears at Plus. That makes the Standard-to-Plus decision pure arithmetic: 2% of your annual gross merchandise value against the $45/month difference. Above roughly $27,000 a year in sales, Plus is cheaper than Standard, and the fee stops being an argument for leaving the platform at all.

So run the comparison properly before deciding. Your real Webflow cost is the Site plan plus the Ecommerce plan plus the fee on your actual volume, against the destination's plan cost plus its fees plus the migration. Plenty of stores discover the platform is not the expensive part.

When staying is the right answer

• Your catalogue fits the item cap with variants counted, and it is not growing fast.

• Moving to Plus removes the transaction fee for less than the fee costs you.

• You sell one-off physical products in one currency, which is the shape Webflow Ecommerce is built for.

• Your store is not the constraint on the business. Migrating a working checkout to fix a marketing-site problem is the wrong order.

When the platform genuinely stops fitting

• Variants push you past the cap and the next plan tier costs more than the store justifies.

• You need recurring billing. Webflow's Ecommerce feature set is built around one-time purchases. Subscriptions are not part of it.

• You need to sell in more than one currency. Webflow's Ecommerce comparison has no multi-currency row.

• Inventory has outgrown one location. No stock by warehouse, no bundle logic.

• Checkout needs to do something specific. Webflow gives you full control of cart and checkout design, but the flow itself is Webflow's.

• Staff account limits bind. 3, 10 and 15 by tier, and that is a real ceiling for a store with a fulfilment team.

Worth deleting from your own reasoning: "Webflow has no multi-channel selling." It ships Google Shopping product sync and Meta event integration on every Ecommerce tier, and automatic tax calculation across all three. Those are not reasons to leave.

Getting the data out

The code export will not help you. Webflow's export excludes Ecommerce outright, along with CMS content, User Accounts, password protection and form processing. Whatever you are picturing when you think "export the store", it is not that button.

What you actually use:

• CSV export for products and orders. Fast, and enough for a small catalogue, but it flattens structure and drops richer field types.

• The Webflow Data API for anything with real variant depth. Products, SKUs and their fields come out with structure intact, which is what you want when a product has an option set rather than a flat variant list.

• A crawl of the live store for the URL inventory. This is a separate artifact from the product export and you need both. The export tells you what products exist; the crawl tells you what paths Google has indexed, including ones that no longer map to a live product.

• Full-resolution image originals, downloaded rather than referenced.

Save all four as a raw checkpoint before any transformation. When an import goes wrong on day three, you want the untouched source, not a half-mapped intermediate.

Choosing where it lands

The question underneath every destination comparison is who owns the cart.

Shopify. The platform owns checkout, payments, inventory, tax and the app ecosystem around them. Your storefront can still be a custom Astro or Next.js build against the Storefront API, so this is not a choice to give up the frontend. The trade is that checkout is Shopify's, product URLs take Shopify's shape so redirects are mandatory, and Shopify Payments is a different processing relationship from your current Stripe account.

BigCommerce. The same trade, with a different bias: it does not penalise you for using a third-party payment processor, and its B2B features around quotes and price lists are stronger. Worth shortlisting specifically when you want managed commerce but need to keep your existing processor.

Stripe plus a custom checkout. Products and prices live in Stripe, orders persist in your own database, and checkout is Stripe Checkout or Payment Element inside your own flow. You keep the Stripe account you already have, product URLs stay exactly where they are because you control routing, and there is no platform fee. The cost is that inventory, fulfilment and tax logic are yours to build or integrate. This fits small catalogues, digital goods, services and stores where checkout is part of the product experience.

A rough rule: if operations run the store, pick a platform that owns the cart. If the storefront is the store, own it yourself.

What has to move, object by object

• Products. Titles, descriptions, prices, compare-at prices, categories, images.

• Variants and SKUs. The part that breaks. Webflow models variants as options with combinations, and destinations differ in how they represent that. Diff SKU lists before and after import with a script rather than by eye: a mismatch does not error, it silently detaches inventory from the thing being sold.

• Inventory counts, captured as late as possible before cutover so they are not stale on day one.

• Customers. Emails and addresses port. Passwords do not, from any platform, so returning customers set a new credential or sign in by emailed link. Say so in advance.

• Orders. Read-only, with the payment provider's transaction ID preserved on every record.

• Discount codes. Re-created, not migrated. Audit which are still active first, because most stores are carrying dead ones.

• Shipping zones and rates, and tax settings. Configuration rather than data, and the one to re-verify per region with test transactions rather than trusting the setup screen.

Product URL redirects

This is where a store loses money quietly. Product pages carry the commercial rankings, and a broken product URL is a lost sale rather than a lost pageview.

• Preserve paths where you can. If the destination lets you keep the existing product path shape, take it. Every redirect you do not need is a risk you do not carry.

• Build the map from a crawl, not the export. The export lists current products. The crawl lists indexed paths, including discontinued products, old slugs and paths already behind a Webflow redirect. Those need targets too.

• 301, never 302, and never a chain. Old path to final path in one hop. Chains through an intermediate slug leak and are slow to diagnose.

• Discontinued products need a decision, not a default. A 404 is correct when there is no successor. Redirecting everything to the category page is worse than a 404 and search engines treat it as one anyway.

• Verify after cutover, at the response level. Request every old path and assert the status and the final destination. Then watch coverage and 404s in Search Console for the first weeks, because that is where the misses surface.

The product-page details that go with it: re-implement Product and Offer structured data so rich results and Shopping listings survive, set the canonical on variant URLs to the parent product so variants do not compete, and keep filter and faceted-navigation URLs out of the index unless a specific one is a landing page.

Image continuity

Product images are ranked assets and they break in a specific way. Export the originals, rehost them on the destination, and repoint the product records. Do not leave the new storefront pointed at Webflow's CDN: that makes your store depend on a subscription you are cancelling, and it puts image continuity outside your control.

While the images are in your hands, fix the alt text. Webflow product images frequently carry empty or generic alt attributes, and a bulk pass at import time is cheaper than a project later.

What this costs

A Webflow migration for a 50 to 100 page site runs $5,000 to $25,000. An ecommerce store sits in the upper part of that band rather than outside it, and the drivers are variant complexity, integration depth around shipping and tax, and how much order history you carry across. Catalogue size matters less than people expect; a thousand simple products is easier than a hundred with deep option sets.

For how the band breaks down by site size and scope, see the Webflow migration cost breakdown.

Where this fits in a wider migration

The store is one workstream. The rest of the site moves alongside it and usually sets the schedule.

For what leaving Webflow involves overall, including what the code export does and does not include, see the complete Webflow to code migration guide.

For the sequence, the pre-launch checks and the cutover order, see the Webflow migration checklist.

What to do next

Send your store link through the free review form below with your product count, your rough variant depth, and your monthly volume. We will come back with the destination we would actually pick, the redirect scope, and a fixed-price number. If the arithmetic says moving to Plus and staying on Webflow beats migrating, that is the answer you will get.