By Mehdi Hassan
How do you move a Squarespace site to Webflow?
You move a Squarespace site to Webflow by exporting what Squarespace allows, converting the blog content into a CSV for the Webflow CMS, rebuilding the pages and design in Webflow, and redirecting any URL that changes. No tool converts a Squarespace site into a Webflow project, so the design is always rebuilt. The export only shortens the content move.
This guide focuses on what the export contains and how to fill its gaps. For the bigger decision of where to go after Squarespace, read our hub on outgrowing Wix, Squarespace or GoDaddy, and if you're still choosing, Squarespace vs Webflow for a growing business.
What does the Squarespace export actually contain?
The Squarespace export is a WordPress-format XML file, generated from the Import and Export settings. It's designed to move a blog to WordPress, so it handles blog content well and everything else unevenly. Check Squarespace's current help docs for the exact list, but the pattern looks like this.
Content | In the XML export? | How to fill the gap |
|---|---|---|
Blog posts (one blog page) | Yes, with titles, dates, tags, categories, body | Convert to CSV for the Webflow CMS |
Additional blog pages | No, only one blog exports | Temporarily move posts or scrape the rest |
Basic pages | Partly; text, images and some blocks | Copy the rest by hand while rebuilding |
Gallery pages | Partly | Download images and rebuild |
Product pages | No | Export products as CSV from Commerce |
Events, albums, many blocks | No | Rebuild or replace with embeds |
Design, custom CSS, templates | No | Rebuild in Webflow |
Images | As links to Squarespace's CDN | Download and re-upload |
In short: blog yes, pages partially, products no. The export is valuable for the blog and close to useless for the rest, which is why the page rebuild is the biggest part of the job.
How do you get Squarespace blog posts into the Webflow CMS?
Webflow can't read Squarespace's XML directly, so you convert it into a CSV that matches your Webflow blog collection and import that. A short script or a converter tool handles the conversion; the cleanup afterward is where the time goes.
Build the Webflow collection first
Create fields for name, slug, publish date, summary, main image, body, author and category, so you know what the CSV must contain.
Convert XML to CSV
Map each post's title, slug, date, excerpt, categories and HTML body into the matching columns.
Clean the HTML
Strip Squarespace block wrappers and inline styles so the body imports as clean rich text.
Re-host images
Download every image referenced in the posts, upload them to Webflow and replace the CDN links.
Import and review
Import the CSV, then open posts with embedded images, galleries or videos and fix them by hand. Webflow's CSV import can turn images inside rich text into placeholders.
Check SEO fields
Add each post's SEO title and description, which you'll need to collect from Squarespace or a crawl.
If your blog is the heart of the site, use the move to tidy its structure, categories and templates; our guide to blog setup for a startup website covers what to set up.
How do you rebuild pages and products that don't export?
Pages and products that don't export are rebuilt in Webflow, using the live Squarespace site as the reference. For pages, that's a design rebuild with copy moved by hand. For products, it's a CSV export from Squarespace Commerce plus a decision about where the store should live.
- Pages. Save each page's copy into a document, edit it, and build the new layout in Webflow. Squarespace sections rarely map cleanly to a good Webflow layout, so rebuild rather than recreate.
- Products. Export the product list from Squarespace Commerce as CSV, then import into Webflow Ecommerce or move the store to Shopify. Product descriptions and variants need checking after import.
- Forms. Squarespace forms don't transfer. Rebuild them in Webflow or connect your CRM's forms.
- Scheduling, members and donations. These rely on Squarespace extensions and need replacement tools.
What to do if your site has more than one blog
Squarespace exports only one blog page per site. If you have a blog and a separate news or resources section built as a second blog, export one, then use one of two approaches for the other.
Option one: temporarily move the posts of the second blog into the first on Squarespace, export, and split them by category in Webflow. Option two: scrape the second blog's posts from the live site into the same CSV structure. Either way, note each post's original URL so its slug and redirect are correct.
How do you keep SEO in a Squarespace to Webflow migration?
Keep SEO by matching Squarespace URLs in Webflow wherever you can and redirecting the rest one to one. Squarespace blog URLs usually follow the blog page's slug, such as /blog/post-slug, and some older sites use date-based paths. Webflow collection URLs follow the collection slug, so you can often recreate the blog path exactly.
Squarespace URL | Webflow approach | Redirect needed? |
|---|---|---|
/about, /services | Static page at the same path | No |
/blog/post-slug | Collection slug blog with the same item slug | No |
/blog/2021/3/4/post-slug | Clean /blog/post-slug | Yes, one per post or a pattern |
/blog?category=news | Category collection page | Usually yes |
/shop/p/product-slug | Webflow /product/product-slug or a store | Yes |
Carry over titles, descriptions, headings and alt text, submit the new sitemap on launch and watch Search Console for 404s. Moving from WordPress follows the same discipline, as covered in WordPress to Webflow migration, and the redirect patterns are similar to the Wix to Webflow route.
Is Webflow the right move after Squarespace?
Webflow is the right move after Squarespace when you need a real CMS, more design control and full SEO settings, and someone on the team is willing to learn it. If your team is design-led and wants something closer to Squarespace's ease, compare Squarespace to Framer migration.
