Squarespace to Webflow: what the export hands you, and why Webflow can't read it
“Squarespace to Webflow” is the search that brings most people to Decamp's guides, and the reason is a format mismatch: Squarespace exports one kind of file and Webflow imports another. This note is what Squarespace says its export contains, read from its help page on 1 November 2026, and what that means for a move.
What you get from Squarespace
Settings → Export gives you a WordPress-format XML file (Squarespace help: Exporting your site). Per that page, it includes:
- layout pages, and gallery pages (project pages of the older York template only on version 7.0);
- one blog page with its posts and up to 1,000 comments per post;
- image blocks and text blocks, plus text from embed and Instagram blocks with minimal structure.
What it leaves out
- Every blog but one. Only one blog page exports, and you choose which. A site with a blog and a news section loses half of its posts unless you run the export twice, and the second run replaces the first.
- Other page types: album, cover, index, info, calendar, portfolio and store pages.
- Content in page-specific headers, footers and sidebars.
- Product blocks, audio blocks, video blocks, dropdowns and drafts.
- Style settings and Custom CSS. Webflow was always going to be a redesign; this confirms nothing visual comes along.
Why Webflow can't use the file
Webflow's CMS imports CSV files into a collection, one row per item, and fetches images from the URLs in the file during the import. It does not read WordPress XML. So the usual route is to turn the XML into a CSV with a rich-text column, which means handling the HTML in each post, finding the cover image, and mapping categories and the SEO description. Tools exist for that conversion, and so does copying posts by hand; what matters is that the step exists and that the XML is its only input.
Two consequences. First, any image the importer fetches must still be reachable at import time, so keep the Squarespace site alive until the import has finished and you have checked the pictures in Webflow. Second, whatever the XML does not hold (the second blog, the other page types, product pages) has to come from somewhere else.
The URLs
Squarespace blog posts usually live at /blog/<slug> (the path depends on the name of your blog page). Webflow collection items live under the collection's own path, which you choose. If you keep the same path, much of the redirect list is empty; if you don't, every old URL needs a 301 in Webflow's hosting settings. Build the list before the domain switches. See the same problem on Wix.
Checklist before you switch
- Count your blog pages. If there is more than one, plan for the others separately.
- List the pages of types the export drops (index, portfolio, album, store) and note which ones you need to rebuild.
- Decide the Webflow collection path first; it fixes your redirect map.
- Import while the old site is live; check images and links in the Webflow editor before cancelling.
- Export store products separately: see what the product CSV leaves out.
Decamp reads the published Squarespace site instead of the XML, so every blog page comes through, and it writes the Webflow CSV and the 301 list. The inventory is free. See the Squarespace to Webflow guide.
Paste a Squarespace address to count blogs, posts, pages and images for free.