Gemin
Start a project

Squarespace to Webflow

Migrate from Squarespace to Webflow

Squarespace is comfortable until the site needs more structure or design control than the template wants to allow. The Webflow move keeps what works visually and fixes the parts that have become hard to manage.

Start a project

A migration like this usually takes 2–3 weeks

Why people move

What changes when you move from Squarespace to Webflow.

What is being compared Squarespace Webflow
Design Squarespace Template with a style editor Webflow Layout built directly, no template underneath
Content model Squarespace Collections, but fixed shapes Webflow Collections you define, with references between them
Editing Squarespace Genuinely good for one person Webflow Editor scoped to what should change Squarespace is pleasant to use and people underrate that. The move is worth it when the site outgrows the shapes, not because the editor is bad.
Page types Squarespace Index, album, event and gallery pages, drawn by Squarespace Webflow Sections and collections you define These are the most designed pages on most Squarespace sites, and they are the ones the export leaves behind entirely.
SEO control Squarespace Solid basics Webflow Per-page and per-item control, with real redirect handling
Commerce Squarespace Built in and capable Webflow Built in, and a genuine question A working Squarespace store is not obviously better off in Webflow Ecommerce. Scope it separately.

Once you have decided

What actually migrates.

What you have What happens Why
Pages Rebuild Made again in Webflow. The old version is a reference rather than something that can be imported. The export is a WordPress XML file. It carries text, not layout.
Blog posts Move Comes across as it is. The content survives the move and the work is transporting it, not remaking it. The one thing the export does well. Posts come across with titles, bodies and dates.
Other collections Rebuild Made again in Webflow. The old version is a reference rather than something that can be imported. Events, products, galleries and portfolios are not in the export in a usable shape.
Images Move Comes across as it is. The content survives the move and the work is transporting it, not remaking it. There is no bulk image export, so the assets are collected separately, then compressed and rehosted. On an image-heavy site this is the line that moves the quote most.
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 where keeping them is practical, because the cheapest redirect is the one nobody needed. Squarespace's own patterns, like the dated blog route and the /s/ asset paths, do not survive, and each of those gets a rule pointing straight at its replacement.
Store Depends Not answerable in general. Which one it is turns on your plan, your export or a decision nobody has made yet. Products export separately as CSV and the export is not the store: images, reviews, variants and checkout behavior each need their own decision. Whether the store should move at all is still the real question.

Before you budget it

Where this migration gets complicated.

  1. 01

    The XML is a WordPress file and it flattens the blocks

    A post built from separate blocks arrives as one run of HTML in one field. Anything that was structured on the old site has to be re-structured before it is a collection, by hand or by a script somebody writes, and none of that work is visible in a file that imports without errors.

  2. 02

    Index and album pages have no Webflow shape to land in

    They are page types rather than content, so rebuilding them starts by deciding what each should become: a collection, a template, or a page that was only ever one page. That modeling happens before the design rather than during it, and these are usually the most designed pages on the site.

How it runs

How the migration works.

  1. 01

    Plan

    What the export gives us, what has to be rebuilt, and what each index, album, gallery and portfolio page becomes: a collection, a template, or a page that was only ever one page.

  2. 02

    Build

    Templates built against the model, with the live Squarespace site open beside them rather than its export.

  3. 03

    Migrate

    The blog comes out of the XML and the images come off the live site, both checked against the source. The dated blog route and the /s/ asset paths do not survive, so each one gets a rule pointing straight at its replacement.

  4. 04

    Launch

    Forms, templates and every old address checked before anything is switched. Then typically 2–3 weeks from start to live, and the Squarespace plan gets closed on purpose rather than at renewal.

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.