Plan your move from Squarespace to Webflow

Move a Squarespace site to Webflow when the team needs more design control and a CMS that grows: what exports, what gets rebuilt and how to keep your URLs working.

Content export
Supported layout content and one blog, as a WordPress-format file. Everything else is checked, copied or rebuilt.
Rebuilt in Webflow
Layouts, store and event pages, and any custom CSS.
Biggest risk
Images still loading from Squarespace after you cancel, and collection URLs that change.
Can stay where it is
Scheduling or a store can move to a dedicated tool and stay connected.

Is the move worth it?

Why teams move from Squarespace to Webflow

  • Layouts beyond the template

    Squarespace sections are quick to use. Webflow gives control of every class, breakpoint and component as the design grows.

  • Content types you define

    Squarespace has fixed collection types such as blogs, events and products. Webflow collections have the fields you choose, and reference each other.

  • Custom content collections

    Case studies, resources, team members and articles as separate collections, each with its own template.

  • Interactions and custom code

    Animations and scripts are part of the build, rather than added through code injection.

When staying on Squarespace is the better call

If the site is small, the team edits it happily and it relies on Squarespace Commerce, Scheduling or Member Areas, the move adds work without much gain. Squarespace suits sites that fit its templates and built-in business tools.

What moves

Where each part of the Squarespace site goes

Everything is listed before anything moves. This is how each kind of content usually maps; your inventory decides the final plan.

On SquarespaceIn WebflowHow it gets there
Layout pagesStatic Webflow pagesText and images copied in as the pages are rebuilt.
One blog and its postsA Blog posts collectionSquarespace’s export produces a WordPress-format XML file, which is converted to CSV and imported.
Any other blogsTheir own collectionsOnly one blog exports, so others are copied by hand or collected with a script.
Gallery pagesA collection or a static galleryGallery-page export applies to Squarespace 7.0. Other gallery content is checked separately, and images are uploaded to Webflow.
ProductsWebflow Ecommerce or a connected storeStore pages aren’t in the site export, so products are moved separately or re-entered.
Events, portfolio and index pagesCollections or static pagesNot in the export. Rebuilt and copied across.
Form blocksWebflow formsRebuilt, with entries sent to email or your CRM.
Code injectionWebflow custom codeEach script reviewed and moved if it’s still needed.

Rebuilt rather than moved

  • Style settings and custom CSSNeither exports. The design is rebuilt as Webflow components.
  • Headers, footers and sidebarsPage-specific header, footer and sidebar content isn’t in the export.
  • Video, audio and product blocksNot included in the export, so they’re added again in Webflow.

Step by step

How to move a Squarespace site to Webflow

Before the move

  1. List every page, post and item

    With its URL, traffic and links, including events, products and portfolio items.

  2. Export the blog and save the images

    Run the WordPress-format export and download every image at full size.

  3. Plan the collections

    Map Squarespace’s collection types to Webflow collections and fields.

  4. Write the redirect map

    Every changed URL against its replacement.

The move

  1. Build the design

    Components and templates in Webflow.

  2. Import posts and collections

    A sample first, then everything, with images uploaded to Webflow.

  3. Rebuild forms and tools

    Forms, newsletter sign-up, scheduling links and analytics.

  4. Review on staging

    Your team checks each page against the original.

After the move

  1. Point the domain at Webflow

    Change the DNS records. The domain can stay registered where it is or be transferred.

  2. Publish redirects and test

    Check a sample of old URLs return a 301 to the right page.

  3. Submit the sitemap

    Then watch Search Console for 404s.

  4. Cancel Squarespace last

    Only after every image and file is confirmed on Webflow.

Search traffic

Keeping your rankings through the move

Google treats a migration as a site move. These are its rules, then the risks that are specific to Squarespace.

What Google asks for

  • A permanent (301) redirect from every changed URL straight to its closest replacement, with no chains.
  • No redirecting old pages to the home page in bulk. Pages with no replacement return a 404 or 410.
  • Redirects kept for at least a year, and a new sitemap submitted in Search Console.
  • Some ranking movement is normal while Google recrawls. On a medium-sized site it can take a few weeks or more to settle.

The migration SEO checklist lists every check before, during and after the move.

If traffic drops anyway, these are the checks to run.

  • Images hosted by Squarespace

    Images in posts load from Squarespace’s servers. If the import keeps those addresses, they can break when the subscription ends. Upload them to Webflow.

  • Collection URL prefixes

    Posts sit under the blog page’s slug, such as /blog/post-name. Matching the collection slug in Webflow keeps most post URLs the same.

  • Product and event URLs

    Store and event items have their own paths. Map each one, or redirect retired items to the closest page.

  • Titles and descriptions

    Check each page’s SEO title and description against the export and copy across any that are missing.

Your part

What your team does during the move

  • A short content freeze

    Publishing pauses on the old site between the final content import and launch, usually a few days. Anything urgent in that window is added to Webflow by hand.

  • Whoever runs the store or bookings

    If those move to new tools, the person who runs them tests orders and appointments before launch.

  • A staging review

    Your team clicks through the staging site, checks the content and submits every form before the domain switches.

What you provide

  • Squarespace admin access
  • Access to the domain and DNS
  • A list of extensions, store and scheduling settings in use
  • Search Console access

Questions about the move

How do I export my Squarespace site?

Squarespace’s Import and Export settings create a WordPress-format XML file. It includes supported layout content and one blog with its posts. Gallery-page export applies to Squarespace 7.0, so other gallery content needs checking. Store, event and index pages, drafts, style settings and custom CSS aren’t included.

Can I move from Squarespace to Webflow without losing SEO?

Yes, if every changed URL gets a 301 redirect to its closest match, titles and descriptions move with the content and the new sitemap is submitted. Expect some movement while Google recrawls.

Can I keep my domain?

Yes. Point its DNS at Webflow. It can stay registered with Squarespace or be transferred to another registrar.

What happens to my Squarespace store?

It doesn’t export with the site. Depending on the catalogue, it moves to Webflow Ecommerce, moves to a store platform such as Shopify, or stays separate on a subdomain.

Do the images move automatically?

No. Download them, upload them to Webflow and check that images inside posts no longer point at Squarespace.

Is Webflow harder to edit than Squarespace?

Day to day, no. Editors change text, images and CMS items without touching the design. Building new layouts takes more skill, which the handover covers.

How long does the move take?

It depends on the number of pages and posts, how many features need replacing and how much content needs cleaning. The first step is an inventory of pages, posts, forms and integrations, and the estimate follows from it. Nothing is estimated before that list exists.