Webflow → to Shopify

Webflow to Shopify: keep the design, move the commerce

Webflow is one of the best tools there is for building a marketing site. Webflow Ecommerce is not one of the best tools for running a store, and most of the migrations we see are brands that have hit that wall: one currency, a checkout they cannot extend, item limits on the CMS, and a growing list of apps that only exist on Shopify. This guide covers the two ways to make the move and what each one involves.

Two ways to leave Webflow Ecommerce

Unlike most platform migrations, a Webflow store has a real choice to make before any data moves.

Option	What it means	Best for
Full move to Shopify	The whole site, marketing pages included, is rebuilt on a Shopify theme. Webflow is retired.	Stores where the product catalog is the site. Simplest to run, one platform to maintain, one SEO footprint.
Split: Webflow front, Shopify commerce	Webflow keeps the marketing pages and blog. Products, cart and checkout run on Shopify, either on a subdomain such as shop.yourbrand.com or embedded with Shopify’s Buy Button and Storefront API.	Brands with heavy editorial or campaign content built in Webflow that they do not want to rebuild, and a design team that lives in Webflow.

We build both. The split is more design-friendly and more expensive to maintain, because two systems now need to agree on navigation, analytics and SEO. If in doubt, the full move is the cheaper long-term answer and the Horizon theme is flexible enough that most Webflow designs translate well.

Why stores outgrow Webflow Ecommerce

• Checkout. Webflow checkout is a fixed template with Stripe and PayPal. No Shop Pay, no checkout customization, no post-purchase offers, and conversion rates show it.
• One currency, one market. Webflow sells in a single currency per site. Shopify Markets handles currencies, languages, duties and local domains from one store.
• CMS item limits and variant caps. Products and SKUs count toward the CMS limit on your plan, and large variant sets get awkward quickly.
• Inventory and fulfillment. No multi-location stock, no native POS, and shipping rules that stop at flat rates and weight bands.
• The app gap. Subscriptions, loyalty, reviews, returns, bundles and B2B are all Shopify-native and mostly absent on Webflow.

What migrates from Webflow to Shopify

Data	Source on Webflow	Moves to Shopify?
Products and SKUs with prices, options, images, weights, categories	CMS, Products and SKUs collections, Export CSV	Yes. Webflow exports the Products collection and the SKUs collection separately. We join them on the product reference, rebuild the option structure and map each SKU to a Shopify variant.
Product descriptions and rich text fields	Same export	Yes, as HTML. Custom CMS fields become Shopify metafields so nothing is lost.
Orders	Ecommerce, Orders, Export CSV	Yes, with line items, totals, shipping, tax and status. Imported as real orders with the original number and date.
Customers	Users export, plus customer data on orders	Yes. Webflow User Accounts export separately from order customers, and the two are reconciled by email.
Passwords	Not exportable	No. Customers reset on first login or use passwordless accounts.
Discounts	Manual	Recreated on Shopify.
Blog and CMS content	CMS collection export	Yes for the blog, as Shopify articles with images rehosted. Other collections become metaobjects or pages depending on what they are.
Design and interactions	Webflow Designer	No. Rebuilt on a Shopify theme, or kept in Webflow in the split model.

Tools

Webflow is not a common source platform for the automated migration tools. Cart2Cart and LitExtension list it inconsistently and their connectors are thin because Webflow’s Ecommerce API is read-only for orders and limited for products. In practice a Webflow migration is a CSV and API job: export the two product collections, transform them, import with Matrixify or the Admin API, and handle orders and customers by script. That is how we run it, and it is why we reconcile every count back to the export rather than trusting a tool’s summary screen.

How we run it

1. Decide full move or split. Fifteen minutes on the survey, then a call. This decision shapes the whole scope.
2. Export and crawl. Products, SKUs, orders, users, the blog collection, and a full URL crawl of the live site.
3. Build in a free Shopify development store. Theme, checkout, payments, shipping, taxes and, if you are going international, Markets.
4. Sample import and sign-off. Twenty of each entity including the awkward ones.
5. Full run. Products, customers, orders, fulfillments. Silent import, no customer emails, no stock changes.
6. Redirects and SEO. Webflow uses /product/slug and /category/slug; Shopify uses /products/handle and /collections/handle. Every URL is mapped and tested. In the split model, Webflow’s own 301 settings handle the product paths pointing at the Shopify subdomain.
7. Integrations. Email, reviews, shipping and support connected to the migrated data.
8. Launch and audit report. Delta sync, DNS, Search Console, and a reconciliation ledger for every entity.

Timeline and cost

Scope	Timeline	From
Full move, under 500 products, standard theme build	6 to 8 weeks	$2,500
Full move, 500 products or more, standard theme build	8 to 12 weeks	$3,500
Full move with custom design matching the Webflow site	8 to 12 weeks	Quoted after audit
Split model, Shopify on a subdomain with shared navigation and analytics	6 to 10 weeks	Quoted after audit

Every quote is a fixed price. Payment is 50 percent to begin and 50 percent once the store is live and you are fully satisfied with the figures, and because we build in a development store you pay Shopify nothing until then.

SEO in the split model

The split model needs care that the full move does not. Two hosts means two sitemaps, and product pages moving from yourbrand.com to shop.yourbrand.com is a URL change Google treats like any other. We keep canonical tags clean, redirect the old product paths from Webflow, submit both properties in Search Console, and make sure analytics stitches sessions across the two domains. Done well it works. Done casually it halves your product rankings for a quarter.

Mapping Webflow’s CMS to Shopify’s product model

Webflow stores products as two linked CMS collections. The Products collection holds the name, description, images, category references and any custom fields you added. The SKUs collection holds one item per purchasable combination with its price, compare-at price, weight, dimensions, inventory and the option values that define it. Shopify’s model is one product with up to three options and up to 2,048 variants, so the translation is mostly mechanical but has four places where it needs judgement.

• Option order and naming. Webflow lets each product define its own option names. We normalize them (Size, Color, Material) so filters and swatches work across the catalog, and we put the most-searched option first.
• Custom fields. Anything you added to the Products collection, such as care instructions, specifications or a rich-text sizing guide, becomes a Shopify metafield with a definition, so the theme can show it and Search and Discovery can filter on it.
• Multi-image fields and per-SKU images. Webflow’s main image plus a multi-image field become the product gallery. A SKU-level image becomes the variant image, which is what makes a color swatch change the photo.
• Categories and reference fields. Category references become collections. Reference fields that point at other collections, such as a Designer or a Collection Season, become metafields that reference metaobjects, which keeps the relationship rather than flattening it to text.

Products that break Shopify’s limits, usually because Webflow allowed four option types, are restructured in the audit. The common fix is to move the least-used option to a line item property or split it into two products.

The split model in practice

If Webflow stays as the front of house, the details decide whether it feels like one site or two.

• Where the store lives. Shopify runs on a subdomain such as shop.yourbrand.com, and checkout runs on Shopify’s checkout domain under your brand. The product and collection pages are Shopify pages, so they load fast and use Shopify’s cart.
• Shared header and footer. The Shopify theme header is rebuilt to match the Webflow navigation, and both sites link to each other’s sections so a visitor never notices the boundary.
• Buy Button embeds. Webflow landing pages can still sell: a Shopify Buy Button or a small Storefront API component drops a product card or an add-to-cart into any Webflow page, with the cart persisting across to the Shopify domain.
• Analytics. One GA4 property with cross-domain measurement configured for both hosts, or sessions split in two and every report undercounts conversions.
• Search Console. Both hosts are verified as one domain property, the Webflow sitemap drops the old product URLs, and the Shopify sitemap picks them up.

Common mistakes in Webflow migrations

• Exporting only the Products collection and discovering that prices, stock and options live in the SKUs collection.
• Leaving the Webflow ecommerce pages live after launch, so Google sees duplicates on two hosts.
• Forgetting Webflow’s own 301 redirect list. Sites that were migrated onto Webflow from something else carry a redirect table that has to be recreated on Shopify, or the oldest URLs die a second time.
• Rebuilding every Webflow interaction. Most animations do not earn their place on a store, and the fast version converts better.
• Treating the split model as free. It costs less up front and more every month, and the audit is the time to be honest about that.

The blog and the rest of the CMS

Webflow sites are usually content-heavy, and the ecommerce collections are rarely the only ones. Blog posts export as a CSV with the rich-text body as HTML, the featured image and any reference fields such as author or category. We convert them into Shopify blog articles with the original publish dates, rehost every image on Shopify’s CDN so nothing points back at Webflow’s asset host after the site closes, and map authors to Shopify article authors. Other collections need a decision each: lookbooks, press mentions, stockists and team members become metaobjects with a template page each, while one-off landing pages are rebuilt as theme pages using sections. Webflow’s collection page URLs follow the pattern /blog/slug or /collection-name/slug, and every one is included in the redirect map. Forms are the last piece: Webflow form submissions live in Webflow, so the history is exported, and the forms themselves are rebuilt with Shopify Forms or your email platform’s embed so the leads land where they used to.

What you get at handover

Every Webflow migration ends with the same package: the reconciliation ledger that accounts for every product, SKU, order and customer from the export down to the live count; the redirect verification list showing each old URL and the status it returned when we tested it; the metafield definitions documented so your team knows where every custom field went; and a recorded walkthrough of the Shopify admin for whoever runs the store day to day. In the split model it also includes the cross-domain analytics configuration and the shared navigation spec, so a future Webflow designer knows what not to break.

Frequently asked questions

Start with the migration survey and tell us which model you are leaning toward. If you are comparing platforms first, our migration services page covers what we move from any source.