By Mehdi Hassan
How do you migrate from Squarespace to Framer?
You migrate from Squarespace to Framer by exporting your content from Squarespace, importing the blog into a Framer CMS collection, rebuilding each page in Framer, and redirecting any URL that changes. Framer's Squarespace import plugin helps with the blog. Nothing imports Squarespace page layouts or design, so the pages are a rebuild.
Framer is a natural step for design-led teams leaving Squarespace, because it keeps a visual canvas while removing template limits. If you want a deeper relational CMS instead, compare Squarespace to Webflow migration, and see all the routes in our hub on outgrowing Wix, Squarespace or GoDaddy.
What does the Framer Squarespace import plugin handle?
The Framer Squarespace import plugin brings blog content from a Squarespace export into a Framer CMS collection, saving you from building a CSV by hand. Plugins update often, so check its current listing in the Framer marketplace for supported fields, but plan around what any import of this kind can and can't do.
Content | Import plugin | What to do |
|---|---|---|
Blog post titles, slugs and dates | Handled | Spot-check slugs against live URLs |
Blog post body text and headings | Handled, with cleanup | Review formatting on long posts |
Images in posts | Varies; verify where they're hosted | Make sure no image loads from Squarespace |
Galleries, embeds, video blocks | Converts poorly or not at all | Rebuild by hand in the post |
Categories and tags | Partly | Decide your category structure first |
SEO titles and descriptions | Often missing | Copy from a crawl |
Pages, design, products | Not handled | Rebuild pages; move products to a store |
The plugin can only work with what Squarespace exports. Squarespace's XML export includes only one blog page per site and leaves out product pages and many block types, so those gaps carry through to Framer whatever tool you use.
What are the steps in a Squarespace to Framer migration?
The migration runs in seven steps, with the URL inventory first and the import in the middle, after the CMS collection is designed.
Crawl and benchmark
List every Squarespace URL with its title, description and traffic from Search Console. Mark each Keep or Change.
Export from Squarespace
Generate the XML export from Squarespace's Import and Export settings, and export products separately if you sell any.
Design the Framer CMS collection
Create the blog collection with the fields you want, and set its detail page path to match your Squarespace blog path.
Run the import or copy by hand
Use the Squarespace import plugin for large blogs, or copy posts directly for small ones.
Rebuild pages
Build every page in Framer at its kept path, using components for repeated sections.
Fix posts and SEO fields
Rebuild galleries and embeds, re-upload images and fill in each page's title, description and social image.
Redirect and launch
Add redirects for every changed URL, connect the domain, submit the sitemap and watch for 404s for two weeks.
When should you hand-rebuild instead of using the plugin?
Hand-rebuild instead of importing when the blog is small, when posts are built mostly from galleries and embeds, or when you're rewriting the content anyway. In those cases, cleaning up an import takes longer than moving posts deliberately.
- A small blog. For a few dozen posts, copying each into Framer and fixing it as you go is often quicker than reviewing an import line by line.
- Visual posts. Portfolios, recipes and case studies built from Squarespace galleries and image blocks lose most of their structure in an export.
- A content rewrite. If you're consolidating thin posts or changing your positioning, move only what survives the audit.
- A new content model. If posts become case studies with fields for client type, results and services, map each one by hand into the new structure.
Hypothetical example: a studio site with a visual blog
For example, suppose a design studio has 15 Squarespace pages and 40 blog posts, most of them project write-ups built from galleries. An import would bring across titles and a little text, but the galleries, which are the point of each post, would need rebuilding anyway.
The better plan: create a Projects collection in Framer with fields for client industry, services, a cover image and a gallery, then move each post by hand into that structure, keeping each slug. The site ends up with a real portfolio instead of a blog pretending to be one, and only the URL path changes, from /blog/ to a new path, with a pattern redirect.
How do you keep SEO when moving from Squarespace to Framer?
Keep SEO by matching URLs wherever possible and redirecting the rest one to one. Framer lets you set any page path and the detail path for each CMS collection, so a Squarespace blog at /blog/post-slug can stay at exactly the same address.
- Keep page slugs such as /about and /services identical.
- Set the blog collection path to /blog/, or to whatever your Squarespace blog page used, and keep each post's slug.
- Redirect date-based post URLs, product URLs and renamed pages in Framer's redirect settings.
- Copy titles, descriptions and alt text from your crawl, since they don't come through reliably.
- Check page speed after launch; animation-heavy rebuilds can slow pages, so see GSAP vs Motion vs CSS for website animation and Core Web Vitals fixes by platform.
The same export, clean and import discipline applies to any CMS move, as covered in CMS content migration, and to the WordPress route in WordPress to Framer migration.
Is Framer the right choice after Squarespace?
Framer is the right choice after Squarespace when the site is mostly marketing pages and a blog, and a designer or marketer will own it. It gives far more layout and motion freedom than Squarespace, with similar ease of editing.
