Squarespace to Framer: migration check
Almost always; the work is untangling section blocks, not moving the content.
What maps where
TodayIn FramerFit
- Blog and gallery pagesCMS collectionsNative
- Section blocksFramer sectionsNative
- FormsFramer FormsNative
- Code injectionCustom code settingsNative
- Summary blocksCMS-driven componentsCode component
- Member areasMemberstack or external authExternal
- CommerceStripe links or Shopify embedExternal
Where it gets tricky
- The official export is a WordPress-format XML that skips products, index pages, and most block types. Plan for copy-paste plus scripting to move the content across.
- Squarespace hard-codes collection prefixes like /blog/ into every post URL. Cleaner paths in Framer mean one redirect per post, and nothing writes that map for you.
- Image URLs in the export point at Squarespace's CDN, and they die when the subscription ends. Pull the originals while the account is still active.
Questions that come up
Why move from Squarespace at all?
Speed of change, mostly. Teams leave when every layout fights the template. Framer gives you real layout control and a CMS without a developer on call. If Squarespace is not actually in your way, stay.
Do my blog posts and their URLs come with me?
Yes. Posts move into a Framer CMS collection and keep their paths where possible, with 301 redirects where not. I migrate the first batch so the pattern is proven; your team finishes the tail with my checklist.
What happens to Squarespace Commerce?
The store stays if it earns money. Framer takes the marketing pages on the main domain and the shop keeps running separately. Small catalogs can move to Stripe-based checkout later, as its own decision.
From the design gallery
See all
