Migration
Squarespace to Webflow
One blog and the layout pages leave as XML, converted to CSV for Webflow; the store, events and design are rebuilt. Blog posts can often keep their addresses.
Trusted by teams from pre-seed to the S&P 100
What moves, and what gets rebuilt
Each part of the site, what it becomes, and whether it comes across, needs converting or is rebuilt.
SquarespaceOne blog page and its posts, in the WordPress-format XML file that is Squarespace’s only site export
Blog postsNeeds convertingWebflowA Blog posts Collection, imported from a CSV made by converting the XML
SquarespaceLayout pages, plus calendar, portfolio and store pages and any second blog, which do not export
Pages, events, portfolioRebuiltWebflowStatic pages built again in the Designer, and a Collection with its own fields for each type
SquarespaceThe template’s style settings and custom CSS, neither of which leaves Squarespace
DesignRebuiltWebflowA style guide, classes and components set up in Webflow, using the old site as the reference
SquarespaceThe Asset library, which downloads one image at a time; post images that load from Squarespace
Images and filesNeeds convertingWebflowImages uploaded to Webflow or imported by URL, all before the Squarespace site is cancelled
SquarespacePhysical and service products in a CSV, without featured images, variant images or alt text
StoreNeeds convertingWebflowWebflow Ecommerce on an Ecommerce plan, from a CSV reshaped to Webflow’s product template
SquarespaceForm blocks saving to Contacts, Acuity scheduling blocks, and member areas and courses
Forms, bookings, membersRebuiltWebflowWebflow form blocks, Acuity’s scheduler in a Code Embed element, and a separate membership service
SquarespacePosts under the blog page’s slug, products under /p/, automatic canonicals, schema and titles
URLs and searchNeeds convertingWebflowCollections under one folder, a 301 for each changed address, and every SEO field filled in by you
SquarespaceYour domain, registered with Squarespace or elsewhere and pointed at the Squarespace site
DomainComes acrossWebflowThe same domain and registrar, with its DNS records pointed at Webflow on launch day
Moving from Squarespace to Webflow, step by step
What Squarespace’s export holds and leaves behind, how its fixed content types become Collections, the store, bookings and members, the addresses you can keep, the checks, and who should stay.
Why teams move from Squarespace to Webflow
Most companies that make this move have outgrown their first site. It went up quickly on Squarespace, and it worked while the site was a homepage, a few service pages and a blog. Then it needed case studies with the client, sector and result in fields of their own, or a team page that sorts by office. Squarespace’s collections come in fixed kinds (blog, store, calendar, portfolio, courses and videos), and we did not find custom fields for them anywhere in its help centre. In Webflow you design each content type and its fields yourself.
The second reason is search. Squarespace makes the decisions for you: every site shares one robots.txt that nobody can edit, the structured data is added automatically and cannot be changed, and we found no setting for a canonical URL of your own. A marketing team that wants to set those things itself needs a platform that hands them over. The third is design. Anything past Squarespace’s style settings goes in code injection and code blocks, and Squarespace says code relying on parts outside its published list may break when the platform changes.
Some reasons will not carry the move. Webflow will not lift your rankings, and for a few weeks the move puts every changed address at risk. It will not save money on editors: above its lowest plan Squarespace includes contributors, and Webflow needs a paid seat for everyone who edits. If the site only looks dated, a redesign on Squarespace costs less than a rebuild.
Webflow’s own Squarespace guide is plain about the method: nothing converts the site, and you rebuild it with the Squarespace one open beside you as the reference.
What Squarespace lets out, and what Webflow takes in
Squarespace has one export for site content, in the Import & export content panel. Click Export, then the WordPress icon even though you are not going to WordPress: the file can only be in WordPress’s format. The site has to be published and set to Public, and a trial site cannot export at all. If the site has two blogs, Squarespace asks you to choose a primary one, and only that blog goes in the file.
The XML holds the layout pages, that one blog with its posts and up to 1,000 comments on each, text and image blocks, and gallery pages. Text from embed blocks comes out with little structure. Everything else stays behind: store, calendar, portfolio and index pages, the second blog, page-specific headers, footers and sidebars, dropdowns, audio, video and product blocks, drafts, the style settings and the custom CSS.
Images are the slow part. Squarespace cannot export images or uploaded videos in bulk; the Asset library downloads images one at a time. The XML refers to images by link, and Squarespace warns that those links stop working once the Squarespace site is cancelled. Plan to have every image on Webflow before that day.
Two other exports help. Products leave as a CSV from the Products panel, and contacts, including form submitters saved to the Contacts panel, as a CSV too.
Webflow’s CMS imports CSV only, up to 4 MB a file, one Collection at a time. Webflow’s Squarespace guide does not mention the XML, but its WordPress guide describes the same file: run it through an XML to CSV converter, then import the result. The file holds pages as well as posts, so check that only post rows go into the Blog posts import. An image column needs a direct URL ending in an image file, and images imported that way get no responsive variants. Test five rows first to see whether Squarespace’s image links pass.
How Squarespace content maps to Webflow Collections
Squarespace’s fixed types each become a Collection in Webflow, and this is where the move pays for itself, because each one can now have the fields it always needed. Type by type:
- The primary blog becomes a Blog posts Collection, filled from the converted CSV: title to Name, slug to Slug, body to rich text, date to a date field.
- A second blog is not in the file. We did not find Squarespace saying whether you can run the export again with the other blog chosen as primary, so try it before planning to copy posts by hand. Two blogs can become one Collection with a reference field for the old blog’s name.
- Categories and tags, if the converted file carries them, become their own Collections, linked from each post by multi-reference fields. Import them first, because Webflow matches references by slug.
- Events become an Events Collection with start and end dates, a location and a booking link. Nothing exports, so enter them by hand or build a CSV from the calendar page.
- Portfolio projects become a Projects Collection, with the gallery as a multi-image field and the client, sector and services as fields of their own.
- Video pages become a Collection whose video field takes YouTube or Vimeo links only. Videos uploaded to Squarespace cannot be exported in bulk, so find the original files and put them on YouTube or Vimeo first.
- Layout pages become static pages, rebuilt in the Designer. The copy can come from the XML; the layout cannot.
If posts or projects carry facts in the body text, such as the client’s name in the first line, because there was nowhere else to put them, pull those into columns before you import, and the templates can use them.
Comments come out in the file, but we did not find a way in Webflow’s documentation for visitors to comment on posts. Keep the ones worth keeping in the post body, or add a comments service through custom code.
The store, bookings, members and forms
These are the parts of a Squarespace site that came in the plan. On Webflow each one is a separate decision.
Store. Squarespace exports physical and service products as a CSV, leaving out the featured images, variant images, alt text, additional information and reviews. Webflow Ecommerce maps product columns itself, but only if the headers and entries match Webflow’s own template, so the file has to be reshaped first, and the import runs only in the Designer. Ecommerce has its own Site plans, each with a cap on products, variants and categories counted together. Payments go through Stripe or PayPal, so Squarespace Payments does not come with you. Webflow’s store cannot be used with its localisation add-on. Export the order history from Products & Services, Orders, as a CSV for your records.
Bookings. Squarespace’s scheduling is Acuity Scheduling, which runs as an account of its own. Acuity’s scheduler embeds in almost any site: copy the code under Scheduling Page, Link, and paste it into a Code Embed element in Webflow, which needs a paid Site plan or Workspace.
Members and courses. Every current Squarespace plan can sell courses, memberships and gated content. Webflow closed its own members feature, User Accounts, on 29 January 2026, so gated pages need a separate membership service; Webflow’s notice points to Outseta and Memberstack. Export the member list from Lists & Segments as a CSV, and expect to rebuild each course and its lessons.
Forms. Squarespace form blocks save to the Contacts panel, a CSV download, email, a Google Drive sheet, Mailchimp or Zapier. Download the old entries, then rebuild each form with Webflow’s form block, give it a name so its entries stay apart, and send it to the same place as before.
The order of work
This is the order we run the move in, and it works the same if you are doing it on your own:
- Inventory. List every address in /sitemap.xml, add the pages that bring in visits or links from analytics and Search Console, and copy each page’s SEO title and description from its settings.
- Redirect map. Copy the existing rules from Developer tools, URL mappings, then write the new address beside every old one in one spreadsheet.
- Content model. Create a Collection for each Squarespace type and the fields it lacked, then import ten converted posts and open every field.
- Rebuild. Set up the fonts, colours and type scale, then build the components, static pages and Collection templates on the staging address.
- Content. Import the posts, enter or import the events and projects, reshape and import the products, upload the images and files, and connect the forms and the scheduler.
- Checks. Fill in every title and description, the canonical URL, the schema and the sitemap, and test the forms and internal links on staging.
- Launch. Import the redirects, publish, then change the domain’s DNS records last, as Webflow’s Squarespace guide advises, and submit the sitemap in Search Console.
- Watch. Check the old top pages’ traffic and Search Console’s list of pages not found for several weeks, and add a rule for each address the map missed. Keep the Squarespace site until every image is confirmed on Webflow.
Keeping URLs, redirects and search
A Squarespace post always sits under its blog page’s slug, and a Webflow Collection item always sits under its Collection URL, so a blog at /blog with a Collection URL of blog keeps the address of every post whose slug is the title only. Squarespace slugs are already lowercase with dashes only, so Webflow’s slug rules leave them alone. Static pages keep paths such as /about, and a portfolio at /work, rebuilt as a Collection with the URL work, keeps its project addresses.
Some addresses change shape. Check Blog preferences, Post URL format: if it includes the year, month or day, posts carry dates in their paths, which a Webflow slug cannot hold. A change to that format does not touch older posts, so one blog can mix both kinds. Events always include a date. On 7.1 a product sits at /shop/p/name if the store page is /shop, and a video at /library/v/name; we did not find a way to put Webflow items two folders deep, and Webflow reserves /product for its store. Where the slugs are unchanged, one capture-group rule carries each pattern: /shop/p/(.*) to /product/%1.
Rules already in URL mappings need rewriting. Squarespace writes them as /old -> /new 301 and uses [name] for every item in a collection; Webflow uses two columns, with (.*) in the old path and %1 in the new. A CSV import replaces all of Webflow’s redirects, they run oldest first, and Webflow suggests staying under 1,000. Redirects need a paid Site plan or Workspace.
Squarespace did several search jobs that Webflow leaves to you. Its title formats wrote every title; in Webflow each page and template needs its own. It added canonical tags; Webflow adds none until you enter the canonical URL. Its schema for blog posts, events, products and your business was automatic; in Webflow you write it in each page’s schema field, on a paid plan. Switch on the sitemap, and upload the llms.txt you typed into Squarespace.
We inventory valuable URLs, plan redirects and check canonicals, indexability, content and internal links. We also monitor after launch. These steps manage migration risk; they cannot guarantee that rankings will stay unchanged. A dip while Google recrawls the site is normal.
When this site’s addresses changed, we mapped each old address by hand to the page that replaced it, used permanent redirects and wrote no wildcard rule. Pages with no replacement return a 404 instead of sending people to the homepage.
Checks before you point the domain
Run through these on the staging site, and the redirect checks again once the domain points at Webflow:
- The Blog posts Collection holds as many posts as the Squarespace blog, and the second blog, events and projects are all in.
- Every image in the Asset library that the site uses is in Webflow, and opening five posts shows no image still loading from Squarespace.
- Each product has its images, variants and alt text again, since the CSV left them out.
- Every page and template has its own title and description, copied or rewritten from Squarespace’s.
- The canonical URL matches the live domain exactly, the sitemap is on, and schema is written for posts, events and products.
- Every row of the redirect map, the old URL mappings included, lands on the right page in one hop.
- Each form has a name, a test entry has arrived where it should, and the old entries are saved.
- The Acuity scheduler books a test appointment from the Webflow page.
- Members can sign in to the new membership service and reach the pages they paid for.
- A test order goes through checkout and payment once the Ecommerce plan is on, and is refunded.
- Analytics and tag scripts are in the site-wide custom code and recording visits.
- Any email records on the domain are noted, so they can be checked after the DNS change.
When to stay on Squarespace
Squarespace is a good home for a lot of sites, and leaving one costs a full rebuild. Stay if:
- The site is a homepage, some service pages and a blog, and the plan is to keep it that way. You would be paying to rebuild what you already have.
- Several people edit and nobody wants to pay for a Webflow seat for each.
- You sell courses, memberships or gated content. Squarespace includes them; on Webflow they mean a separate service with its own login.
- The store is the business. Every paid Squarespace plan can sell; Webflow needs an Ecommerce plan, takes Stripe and PayPal only, and cannot localise a store. If you are leaving Squarespace for the store, look at Shopify.
- Nobody will own the search setup. On Webflow the titles, canonical URL, schema and sitemap are yours to set and keep right.
- The site is image-heavy and the move has no other reason. Every image is downloaded and uploaded again.
- The complaint is the look. A redesign on Squarespace fixes that for less.
What decides the time and the cost
The rebuild takes most of the time, because nothing of the design leaves Squarespace. The number of distinct layouts matters more than the number of pages. The blog is one template, whatever its size.
After that, the time follows what the export leaves out. Images, downloaded one at a time, can take days on a large portfolio. Events, projects and a second blog are entered by hand or rebuilt as spreadsheets. A store adds reshaping the product CSV, adding back every product’s images and testing checkout. Member areas add choosing a service and rebuilding each course. Redirects are light when posts use the title alone, and heavier when dates are in the paths.
Our websites start from $15,000, and most take four to eight weeks. A migration is priced as a website project, on the page system, content work, integrations, publishing requirements and migration complexity, and we agree the scope and the price before we start. We build websites in Webflow, and Morse Micro’s is one.
Doing it yourself, you pay for a Webflow Site plan, an Ecommerce plan if you sell, a seat for each editor and any membership service, on their own pricing pages. Keep paying for Squarespace until the images are safe. A domain registered with Squarespace keeps renewing there after the site is cancelled.
Vendor details were checked against Squarespace’s and Webflow’s own documentation on 15 November 2026. Both change their plans and features, so read theirs before you start.
Moving from Squarespace?
Short answers, from the guide above.
Only part of it. Squarespace’s one site export is a WordPress-format XML file holding the layout pages and a single blog. Store, calendar and portfolio pages, a second blog and the styles stay behind, and images download one at a time. Webflow says there is no automated way to convert a Squarespace site, so you rebuild the design and convert the blog to CSV for Webflow’s CMS.
Nobody can promise every position holds, but most of what protects them is in your hands. We inventory valuable URLs, plan redirects and check canonicals, indexability, content and internal links, then monitor after launch. On Webflow that means keeping addresses where you can, a 301 for each one that changes, the sitemap on and the canonical URL set. Some movement in the first weeks is normal.
Most of our website builds take four to eight weeks, and a migration is scoped as a website project. On this move the rebuild takes most of it, because the design does not leave Squarespace. Image-heavy sites add days, since Squarespace downloads images one at a time. A store, events, member areas or a second blog add more, because none of them is in the export.
Many of them. Pages at /about or /services keep their paths as static pages. A Squarespace post sits at /blog/post-name, and a Webflow Collection with the URL blog puts it at the same address, as long as the slug is unchanged. Posts whose address includes a date, events and products under /p/ change shape, so each needs a 301 redirect or a pattern rule.
It can stay registered with Squarespace. Cancelling the Squarespace site does not cancel the domain, which keeps renewing. In the domain’s DNS settings you delete the Squarespace Defaults records and add the records Webflow gives you. You can instead transfer the domain to another registrar with an auth code, which can take up to 15 days. Change the records only once the Webflow site is ready to publish.
Where to go next
- Webflow vs SquarespaceWebflow if a growing company needs content types of its own and control of search settings. Squarespace if the site is pages and a blog that a few people keep up to date.
- WordPress to WebflowPosts come across as CSV, pages and the design are rebuilt, and posts move under a folder. A 301 for each changed address protects the search traffic.
- Webflow to custom codePages are written again as components, CMS content leaves as CSV or through Webflow’s API, and a permanent redirect for each changed URL protects search.
Planning this move?
Tell us where it is now and where it is going. We’ll say what we’d keep, what we’d rebuild and how long it takes.
Most teams start with a call, then a sprint or an audit.
The people you’d work with, from the first call to launch