Very little moves from Squarespace to Webflow automatically. Webflow's help centre says there is no automated way to convert a Squarespace site, and that the move "is a rebuild, not a transfer". Squarespace's own export is a single WordPress-format XML file that carries one blog, layout pages and text and image blocks, and leaves out store pages, portfolio pages, video blocks, drafts and custom CSS.
This guide sorts a Squarespace site into what you can export, what you copy by hand and what you rebuild, then covers the redirect map, the domain and a realistic timeline. Every limit comes from Squarespace's or Webflow's own documentation, read on 5 November 2026.
Squarespace to Webflow: what moves and what is manual
Webflow's Squarespace migration article opens with an audit: every page, URL path, content type, font, form, extension, custom code snippet and existing redirect. On Squarespace the audit decides the budget, because the export covers only part of the site.
| Squarespace content | Export from Squarespace | Into Webflow |
|---|---|---|
| Layout pages, text and image blocks | In the XML file | Rebuilt by hand; copy text from the XML or the live page |
| One blog, all posts, up to 1,000 comments per post | In the XML file; you choose the primary blog | Converted to CSV and imported into a Collection |
| A second or third blog | Not exported | Copied by hand, or exported by switching the primary blog |
| Portfolio, store, index, album and calendar pages | Not exported | Rebuilt as Collections or static pages |
| Products | Separate CSV, up to 10,000 products; no images, alt text or reviews | Webflow Ecommerce or a CMS Collection |
| Images | One at a time from the Asset library | Upload to the Assets panel, or import by URL |
| Uploaded videos | Cannot be downloaded | Use your original files or a video host |
| Style settings, custom CSS, drafts, audio and video blocks | Not exported | Rebuilt or recreated |
Source: Squarespace Help Center, Export your site content, Export products to a .csv and Asset library articles; Webflow Help Center, Migrate your site from Squarespace to Webflow; read 2026-11-05
The XML file is the starting point, not the import. Webflow imports CMS content from CSV files of up to 4 MB, not from WordPress XML. Someone has to turn the XML into one CSV per Collection, with the post title, slug, date, body HTML, image URL and category in columns. Our WordPress to Webflow migration checklist walks through the same XML-to-CSV step from the WordPress side, because the file format is the same.
Only one blog leaves per export. Squarespace asks you to pick a primary blog when a site has several. Run the export once per blog, changing the primary blog each time, and keep the files separate.
Images are the slow line. Squarespace says it is not possible to download all images in bulk. Webflow's own article tells you to budget time for this on an image-heavy site. Importing images by URL during the CSV import avoids the manual download for blog cover images, but Webflow warns that images imported this way get no responsive variants, so important images are better uploaded directly.
Products lose their pictures. The product CSV leaves out featured images, variant images, alt text and reviews. Plan a separate pass for product photography.
Getting the blog into Webflow CMS
Model the Collection first. Create Categories and Authors Collections before Posts. Webflow matches reference fields by turning plain text into a slug and looking for an item with that slug, so import the referenced Collections first and use their slugs in the Posts CSV. A required reference that does not match imports the row as a draft with the field blank.
Keep the slugs. Squarespace post slugs are lowercase, use only dashes and run from 3 to 200 characters. All of that fits Webflow's slug field, which takes under 256 characters. Copy each slug exactly rather than letting Webflow generate one from the title.
Keep the dates. Map the original publish date to a date field and sort the Collection by it, or every post will look as if it was written on import day.
Check rich text after import. Webflow's rich text field accepts HTML but may clean up embeds and remove attributes it does not support. Spot check a long post with images, embeds and headings before you import the rest.
For a blog of a few dozen posts, copying by hand is often faster than writing a converter. Above that, a short script against the XML file pays for itself. Our guide to Webflow CMS import tools compares the options for that step.
The redirect map for Squarespace URLs
Squarespace builds item URLs from a small set of rules, so the redirect map is mostly a handful of wildcards, once you know which rules your site used.
| Squarespace pattern | Example | Webflow URL | Rule |
|---|---|---|---|
| Static page | /our-team | /our-team | None if the slug is kept |
| Blog post, title only | /blog/my-post | /blog/my-post | None: name the Collection URL "blog" |
| Blog post with date | /blog/2021/3/14/my-post | /blog/my-post | /blog/(.*)/(.*)/(.*)/(.*) to /blog/%4 |
| Blog category | /blog?category=News | /category/news | /blog%?category%=News to /category/news |
| Blog tag | /blog?tag=webflow | /tag/webflow | /blog%?tag%=webflow to /tag/webflow |
| Store product (version 7.1) | /shop/p/red-sweater | A product or Collection page | /shop/p/(.*) to the new path with %1 |
| Portfolio sub-page | /work/project-name | /work/project-name | None if the Collection URL is "work" |
Sources: Squarespace Help Center, URL slugs and Linking to categories or tags; Webflow Help Center, redirects and Page URLs; read 2026-11-05
Check the Post URL format. Squarespace lets owners build the post URL from the title, year, month and day plus custom text, and a new format only applies to posts written after the change. An older blog can mix both styles. Crawl the live site, or read the post links in the XML file, before writing rules.
Dated URLs need a wildcard. Webflow's Page URLs article says only static pages can be organised in folders, so a Collection page cannot live at /blog/2021/3/14/my-post. Webflow supports several capture groups in one rule, so the four-group wildcard in the table above sends every dated post to its title slug.
Escape the old path. Webflow requires a % before special characters in the old path: the percent sign, hyphen, ampersand, asterisk, brackets, equals sign, underscore, plus and question mark. That is why the category rule reads /blog%?category%=News, and why /our-team becomes /our%-team in a redirect's old path. Webflow also strips a trailing slash before a query string, so write /blog%?tag%= and not /blog/%?tag%=.
Mind the reserved slugs. On a Webflow site with Ecommerce turned on, /product and /category are reserved, so pick another Collection URL for blog categories. Squarespace category URLs are fixed query strings, so each category with traffic needs its own rule.
Order is age in Webflow. Webflow runs redirects in the order they were added, so add single-page rules before the wildcards that would catch them. Squarespace runs its URL mappings from top to bottom, so the order of your old list carries over if you add the rules in the same sequence.
Rewrite old Squarespace redirects. Squarespace stores redirects in its URL mappings panel as lines such as /old-url -> /new-url 301, with up to about 2,500 lines. Copy them out, rewrite each one to point at the final Webflow URL so nothing chains, and keep the total under the 1,000 rules Webflow recommends. Once the domain points at Webflow, Squarespace's mappings stop running.
Our website migration SEO checklist covers the crawl, the staging rehearsal and the watch period after launch.
Squarespace domain to Webflow: point it or transfer it
Webflow is not a domain registrar, so a Squarespace domain cannot be transferred to Webflow. It is connected by DNS records, wherever it is registered.
| Option | What you do | Watch for |
|---|---|---|
| Keep it at Squarespace, point it | In DNS settings, delete the Squarespace Defaults, then add Webflow's A, CNAME and TXT records as custom records | Squarespace says changes can take 24 to 48 hours; the domain must use Squarespace nameservers |
| Keep it at Squarespace, use custom nameservers | Move DNS to a host you choose and add the records there | Registration and billing stay at Squarespace |
| Transfer it to another registrar | Turn off the domain lock, request the auth code, give it to the new registrar, then point it | Up to 15 days; 60-day lock after registration, transfer or a contact change |
Source: Squarespace Help Center, Pointing a Squarespace domain, Transferring a domain away from Squarespace and Domain locks; Webflow Help Center; read 2026-11-05
Pointing is the shorter route. Webflow's DNS article lists three records: an A record for @ with the value 198.202.211.1, a CNAME for www with the value cdn.webflow.com, and a TXT record for _webflow with the one-time verification value from Site settings. Squarespace's article says the domain cannot point to another site while the Squarespace Defaults are in place, so they have to go. Webflow issues the SSL certificate once the records point at it, which it says typically takes a few minutes.
Transferring takes planning. Squarespace emails the auth code to the registrant contact, which may not be the login email, and says it should arrive within 24 hours. Remove DNSSEC before starting. For domains registered with Squarespace Domains LLC, Squarespace holds a 5-day window in which you can reject the transfer. Squarespace recommends a screenshot of the DNS records first.
Protect email. If Google Workspace or another mail service runs on the domain, list the MX records before touching anything. When pointing, change only the website records. When transferring, Squarespace says to adjust the MX records at the new provider straight away to avoid an interruption.
Lower the TTL in advance. Webflow recommends cutting the TTL to the lowest value your DNS host allows, typically 30 seconds, at least one full TTL period before the switch. With a 24-hour TTL, that means a day ahead.
How long a Squarespace to Webflow migration takes
Most of the calendar is the rebuild. The domain and search steps add fixed waits.
| Step | Typical duration | Source |
|---|---|---|
| Download images | One at a time; depends on library size | Squarespace Help Center |
| Rebuild and import into Webflow | Two to three weeks per site in our own builds | Octo Agency |
| Lower TTL before cutover | One full TTL period, often 24 hours | Webflow Help Center |
| DNS change takes effect | 24 to 48 hours at Squarespace; SSL in minutes once pointed | Squarespace and Webflow Help Centers |
| Optional domain transfer | Up to 15 days | Squarespace Help Center |
| Google processes the move | A few weeks for a small to medium site | Google Search Central |
| Keep redirects | At least one year | Google Search Central |
Source: as listed per row; read 2026-11-05
Our Webflow builds take two to three weeks per site, inside a four-week marketing-site process that starts with the URL map. A domain transfer can run in parallel, but we would not start one in the same week as launch: point the domain first, transfer it later if you want it elsewhere.
The cutover, in order.
- Crawl the Squarespace site and export Search Console's top pages and linked URLs.
- Export the XML once per blog and the product CSV; copy the URL mappings panel.
- Download images and confirm font licences.
- Create Collections in Webflow; import Categories and Authors, then Posts, keeping slugs and dates.
- Rebuild pages, forms and integrations, then add tracking in Site settings.
- Write the redirect CSV with escaped old paths, single rules before wildcards.
- Publish to the webflow.io staging domain and test every row of the redirect map.
- Lower the TTL, then add the Webflow records and remove the Squarespace Defaults.
- Publish to the custom domain, test the redirects again, submit the sitemap and watch Search Console.
Keep the Squarespace subscription until the redirect report is clean. Google says rankings may fluctuate while it recrawls, and that permanent redirects do not cause a loss in PageRank.
What this means for your Squarespace to Webflow migration
We build marketing sites in Webflow and applications in Next.js, so we are not neutral about where you end up. Squarespace does small sites well, and our Webflow vs Squarespace comparison sets out where it stops for a growing B2B company. This guide assumes that decision is made.
On most Squarespace moves, the blog and the images are the work, and the redirect map is a few wildcards plus single rules for retired pages. Our Wix to Webflow migration guide covers the same job from Wix, where the blog cannot be exported at all. If your blog runs to hundreds of posts, we would script the XML conversion rather than copy by hand, and we would write the URL map in the first week, before design starts. Our marketing website service page explains how we scope a Squarespace to Webflow migration.
