Gemin
Start a project

Shopify to Webflow

Migrate from Shopify to Webflow

This is usually not a full platform move, and it should not be. Shopify is strong where money changes hands. Webflow is strong where the brand story, content and campaign pages need design freedom.

Start a project

A migration like this usually takes 3–4 weeks

Why people move

What changes when you move from Shopify to Webflow.

What is being compared Shopify Webflow
What it is built for Shopify Selling: catalog, checkout, inventory, tax Webflow Explaining: the pages that persuade
Marketing pages Shopify Liquid templates, workable but not the point Webflow The whole point
Content model Shopify Pages, blogs, metafields Webflow Collections with references
Checkout Shopify Theirs, and genuinely excellent Webflow Webflow Ecommerce, which is not the same thing Shopify wins this outright. Most of these projects keep the store on Shopify.
Who edits marketing content Shopify Theme sections and fields, with structural changes going back to Liquid Webflow The marketing team, inside the design system
Best shape Shopify A store with a site attached Webflow A site with a store attached

Once you have decided

What actually migrates.

What you have What happens Why
Marketing pages Rebuild Made again in Webflow. The old version is a reference rather than something that can be imported. Liquid templates do not transfer; the design does.
Blog posts Move Comes across as it is. The content survives the move and the work is transporting it, not remaking it. Exportable and mappable into a collection.
Products Depends Not answerable in general. Which one it is turns on your plan, your export or a decision nobody has made yet. The catalog exports as CSV, and whether it should is the separate question. If Shopify stays the system of record, the data stays with it and only the presentation layer belongs in Webflow.
URLs and redirects Reconfigure The same thing, set up again. Nothing is recreated, but it has to be pointed at the new site by hand. Paths are kept wherever the new structure allows it. Shopify's fixed prefixes are the ones that move, and some of its reserved routes cannot be redirected from inside Shopify at all, which is why the routing gets planned rather than discovered at cutover.
Apps Rebuild Made again in Webflow. The old version is a reference rather than something that can be imported. Each becomes a native feature, an integration, or a decision.

Before you budget it

Where this migration gets complicated.

  1. 01

    Product data is a catalog, not content

    Variants, inventory, pricing rules and collections are a system of record. Webflow Ecommerce can hold a catalog and it is a different product with different limits, so the comparison has to be done on the real numbers.

  2. 02

    Apps carry real functionality that is easy to miss

    Reviews, subscriptions, loyalty and bundles are installed apps with their own data. Each one needs an answer before the store's move is priced, and some of them have no equivalent.

How it runs

How the migration works.

  1. 01

    Plan

    What stays in Shopify, what moves to Webflow, and what functionality sits between the two.

  2. 02

    Build

    The marketing pages are built in the Designer. The storefront stays where it is unless moving it was scoped separately.

  3. 03

    Migrate

    Content in, assets rehosted and checked against the source, and every address that changes given a rule pointing straight at its replacement.

  4. 04

    Launch

    Forms at the record, every template at three widths and every old address requested, all before anything is switched. Then typically 3–4 weeks from start to live, and a week of watching what the old addresses return.

What you are buying

What is included.

  • Design rebuild

    Rebuilt directly against the existing site.

  • Responsive development

    Desktop, tablet and mobile, built and checked.

  • CMS architecture

    Collections and fields mapped before build.

  • Content migration

    Migrated and checked against the source.

  • Asset migration

    Collected, compressed and rehosted.

  • Forms and integrations

    Tested through to the final record.

  • Redirects

    Changed URLs mapped directly to replacements.

  • Metadata and canonicals

    Preserved wherever possible.

  • Search footprint preservation

    URLs inventoried before and checked after.

  • Pre-launch QA

    Forms, templates and old URLs verified.

  • Post-launch support

    One week of indexing and traffic checks included.

Search visibility can move during a migration. The goal is to preserve what search engines already understand, and to catch what changed quickly after launch.

Other migrations

Coming from somewhere else?

Reach out and see if we are a good fit.

Start a project

Currently booking two to four weeks out.