← All playbooks
Publishing migration

Squarespace → Framer

Squarespace gives you one WordPress XML file, and it is a partial copy. Framer's Squarespace Import plugin loads the blog from that file. Pages, the shop, and the design are a rebuild, with redirects on the Framer domain.

Typical timeline10 to 25 business days30 to 70 hours active work
Statusneeds review
Source profileSquarespace export help reviewed 2026-11-01
Destination profileFramer Squarespace Import plugin and redirects help reviewed 2026-11-01
Documentation date
Review window
Evidence4 sources
This route needs review.Use it as a planning baseline, then verify the dated sources and test with representative data before production.
Before you migrate

Should you make this move?

Both platforms have a case. Compare what you gain with what you give up before scheduling the cutover.

Current platform

Squarespace

Reasons to stay
  • Beautiful templates and integrated hosting let small teams publish without technical operations
  • Editors get a purpose-built publishing workflow instead of raw files
Reasons to leave
  • Structured content, code control, and complex integrations are restricted
  • Themes, extensions, and content models add maintenance and portability constraints
New platform

Framer

What gets better
  • A Figma-like canvas, components, and effects let small teams publish marketing sites quickly
  • Editors get a purpose-built publishing workflow instead of raw files
What gets worse
  • CMS exports go through plugins, and the published site is not a portable Designer or WordPress project
  • Themes, extensions, and content models add maintenance and portability constraints
Best of the move

Framer: A Figma-like canvas, components, and effects let small teams publish marketing sites quickly. This removes a major source-side concern: Structured content, code control, and complex integrations are restricted.

Worst of the move

What you lose: Beautiful templates and integrated hosting let small teams publish without technical operations. What you inherit: CMS exports go through plugins, and the published site is not a portable Designer or WordPress project.

Jump to a section
01At a glance

Know the shape of the move.

Transfer outcome12 features audited
Transfer outcome distributionClean transfer: 0, Partial transfer: 5, Manual rebuild: 4, Not transferred: 3.
Clean0
Partial5
Manual4
Lost3
Mapping route8 of 11 fields have a destination path

This timeline assumes

  • This is a marketing site and one blog. A store belongs with Squarespace → Shopify. A design-tool move is also covered by Squarespace → Webflow, Framer → Webflow, and Framer → WordPress.
  • The Squarespace site is published, and site availability is Public. Squarespace says a trial cannot export.
  • You keep Squarespace online until Framer has the posts, the rebuilt pages, and the redirects you still need.
  • The WordPress XML file is the handoff. Squarespace says you click the WordPress icon even when the destination is not WordPress.
  • Redirects in Framer cover paths on the domain you connect there. The old host still owns a redirect of the whole domain.
02What transfers

What survives the move.

“Partial” and “manual” are not footnotes. They are work that must be scheduled and verified.

ItemOutcomeImpactWhat happensMitigation
The export filepartialcriticalSquarespace's help, updated 9 October 2026, exports one XML file in WordPress format. It is not a full site backup, and Squarespace says you cannot use it to import into another Squarespace site.Download the XML and a products CSV and a contacts CSV before you cancel. Open the XML and see which pages are actually in it.
Layout pagesmanualcriticalLayout pages are in the export list. The Squarespace Import plugin describes a blog import: posts, authors, tags, and categories. It does not say layout pages become Framer pages.Rebuild each public layout page in Framer. Use the XML as a text source, not as a page importer.
One blogpartialcriticalSquarespace exports one blog page, its posts, and up to 1,000 comments per post. If you have more than one blog, you pick a primary blog. The plugin lists title, date, body, excerpt, and a cover image.Count posts on the primary blog. Import that file. Export again only after you decide what to do with the other blogs.
Extra blogsmanualhighA second blog page does not export in the same file. Squarespace's list says more than one blog page stays behind.Move posts onto the primary blog before export, or run a second export and a second plugin import after the first one is checked.
Design and CSSlostcriticalStyle settings and custom CSS do not export. Squarespace says many features depend on its JavaScript and CSS, so the file cannot carry the rendered site.Treat Framer as a new design. Copy any custom CSS you still want into a note before the Squarespace site goes away.
Page types that stay behindlosthighAlbum, cover, index, info, calendar, portfolio, and store pages do not export. Page-specific headers, footers, and sidebars do not export. Gallery pages do export, including York project pages on version 7.0.List every page that is not a layout page or the chosen blog. Rebuild the ones that still have traffic.
BlockspartialhighText blocks and image blocks export. Text from embed and Instagram blocks exports with minimum structure. Audio blocks, product blocks, video blocks, and dropdowns do not. The plugin says YouTube and Vimeo come across, and GitHub gists become links.Open one post with a video and one with an embed. Replace anything that arrived as plain text.
DraftslostmediumSquarespace does not export drafts. The plugin says drafts stay drafts, which only helps if a draft is already in the XML. With Squarespace's export, it is not.Publish or copy any draft you still need before you export.
CommentspartialmediumUp to 1,000 comments per post are in Squarespace's export. The plugin's 'what comes over' list does not mention comments.If comments matter, save them from Squarespace before you cancel. Do not assume the CMS import kept them.
ImagespartialcriticalSquarespace warns that a WordPress importer can keep image links that die when you cancel Squarespace. The plugin listing says it copies post images into Framer, including captions and lazy-loaded images turned into rich text. That copy step is the plugin author's claim.After import, open images from Framer's asset library. Cancel Squarespace only after those files no longer point at Squarespace.
Products and contactsmanualhighSquarespace's overview says products and contacts export as CSV files, separate from the XML. Store pages are on the XML exclusion list.Download both CSVs if you still need them. This playbook does not move a store.
Old post URLsmanualcriticalSquarespace post URLs include the date, such as /blog/2024/3/9/my-post. The plugin can add a redirect per post when the Framer plan includes redirects. Framer's help, updated 15 September 2026, says rules live in Site Settings, under Hosting, then Redirects. You publish to apply them. A CMS path change does not update an old rule. Wildcards use *. Capture groups use :1. A dated path can use :slug. Framer only redirects sub-paths on the current domain.Add the post redirects, publish, and request three old URLs. Point the domain with a redirect at the old host.
03Field and feature mapping

Where each thing goes.

SourceDestinationMethodNotes
Layout pageFramer pagemanualIn the XML. Rebuild it. The blog plugin does not claim these pages.
Blog postCMS itemautomaticTitle, date, body, excerpt, and cover, per the plugin listing.
Author, tag, categoryLinked CMS collectionsautomaticThe plugin creates those collections.
Cover and inline imageFramer assettransformThe plugin says it copies files in. Check them.
YouTube or VimeoVideo in the postautomaticPlugin listing. Gists become links.
Embed or Instagram textRich text with little structuremanualSquarespace's phrase is minimum structure.
CommentNo destinationunsupportedIn the XML up to 1,000 per post. Not in the plugin's import list.
DraftNo destinationunsupportedSquarespace omits drafts.
Custom CSS and stylesNo destinationunsupportedRebuild the look in Framer.
Dated post URLFramer redirecttransformPlugin button if the plan includes redirects, or a manual rule.
Product or contactCSV you keepmanualSeparate Squarespace exports. Not this blog import.
04Before you begin

Make the move recoverable.

Backup procedure

Create the source-of-truth backup

Keep the XML, the CSVs, and Squarespace online until Framer serves the pages.

  1. Confirm the site is published and Public.
  2. Export the WordPress XML from the Import and export content panel.
  3. Export products and contacts as CSV if you still need them.
  4. Save a list of public URLs, especially dated blog URLs.
  5. Leave the Squarespace subscription on.

Proof to capture: The XML file, the CSVs, and a URL list you can request after DNS moves.

Transformation · Squarespace WordPress export and the Squarespace Import plugin

Blog import

Load the one exported blog into Framer CMS.

  1. Export one blog as WordPress XML. Squarespace says to click the WordPress icon even if you are not going to WordPress.
  2. Drop the file into the plugin and check the fields. Nothing is written until you press Import.
  3. The free tier covers the first 25 posts. On 1 November 2026 the listing priced a one-project license at $49 and an unlimited license at $99. The unlimited key also works in the author's Webflow Import.
  4. Run the plugin again later only to update the same collections. Confirm it did not duplicate them.

Proof to capture: Save the input, output, command or tool settings, warnings, and final item counts.

Transformation · Plugin redirect action or Site Settings, Hosting, Redirects

Redirects

Keep dated Squarespace post URLs working on the Framer domain.

  1. Add one redirect per old post, or use a wildcard if the new paths share a pattern.
  2. Publish the Framer site. Rules do not apply before that.
  3. If you later rename a CMS path, edit the old rule. Framer does not update it for you.
  4. At the old DNS host, redirect the domain itself. Framer does not do that hop.

Proof to capture: Save the input, output, command or tool settings, warnings, and final item counts.

05Handle with care

The things most likely to hurt.

These are operating limits. Treat every “Stop if” condition as a blocked migration, not a suggestion.

Pilot

The XML is treated as the whole site

criticallikely likelihood

Store, portfolio, calendar, or a second blog is still public, and nobody rebuilt it.

Consequence
Those URLs 404 after DNS moves, and the content is only on Squarespace.
Mitigation
Walk the Squarespace page list against the XML before you import.

Stop if: A page with traffic is not in the file and has no Framer replacement.

Cutover

Images still point at Squarespace

criticalpossible likelihood

A post looks fine while Squarespace is online, and the image URL is still on their host.

Consequence
The post breaks when you cancel.
Mitigation
Open the asset in Framer and confirm the file lives there.

Stop if: A sample image request still goes to Squarespace.

Cutover

Redirects never get published

highpossible likelihood

The plugin added rules, and the site was not published, or the plan does not include redirects.

Consequence
Old /blog/year/month/day/slug links miss the new posts.
Mitigation
Request three old URLs after publish. Check the plan before you rely on the plugin button.

Stop if: An old post URL returns anything other than the new post.

06Precise timeline

Do the work in this order.

Estimate forA published Squarespace marketing site with one blog, rebuilt in Framer
Total elapsed10 to 25 business days
Active work30 to 70 hours
BufferAdd time for a second blog, a shop, or a large set of dated URLs.
01
Days 1 to 3Page list2 to 3 days
02
Days 3 to 5Export1 to 2 days
03
Days 5 to 15Import and rebuild5 to 12 days
04
Days 15 to 18Domain and redirects1 to 3 days
05
Days 18 to 28Watch the old URLs5 to 10 days
  1. Days 1 to 3 · inventory

    Page list

    4 to 8 hours active2 to 3 days elapsedSomeone who knows which pages still matter waiting
    • List pages, blogs, and the shop.
    • Mark what Squarespace will not put in the XML.

    Depends on: Squarespace admin

    Stop / go checkpoint

    Export?

    Go when: Every public page is either in the export plan or assigned to a rebuild.

    Stop when: A store or a second blog has traffic and no owner.

  2. Days 3 to 5 · backup

    Export

    2 to 4 hours active1 to 2 days elapsedSquarespace processing the file waiting
    • Confirm the site is Public.
    • Download the XML and any CSVs.
    • Save the URL list.

    Depends on: Published site

    Stop / go checkpoint

    Import the blog?

    Go when: The XML opens and the primary blog's posts are in it.

    Stop when: The export is from a trial or the wrong blog.

  3. Days 5 to 15 · pilot

    Import and rebuild

    16 to 40 hours active5 to 12 days elapsedDesign review waiting
    • Import posts with the plugin.
    • Rebuild layout pages.
    • Check images, video, and one old URL on a preview.

    Depends on: XML file

    Stop / go checkpoint

    Connect the domain?

    Go when: Posts and the pages you kept are on Framer, and sample images are local.

    Stop when: A template still loads Squarespace assets.

  4. Days 15 to 18 · cutover

    Domain and redirects

    3 to 8 hours active1 to 3 days elapsedDNS waiting
    • Publish redirects.
    • Point the domain.
    • Request old and new URLs.

    Depends on: Signed preview

    Stop / go checkpoint

    Leave Squarespace as a fallback?

    Go when: The homepage and three old posts resolve on Framer.

    Stop when: A redirect loop or a missing page shows up.

  5. Days 18 to 28 · observe

    Watch the old URLs

    3 to 6 hours active5 to 10 days elapsedSearch and shared links waiting
    • Check a week of 404s.
    • Add rules for paths you missed.
    • Keep Squarespace until that list is quiet.

    Depends on: Domain on Framer

    Stop / go checkpoint

    Cancel Squarespace?

    Go when: Images and the URL sample no longer need Squarespace.

    Stop when: A live page still depends on it.

07The point of change

Cut over with a way back.

Go live

Cutover

Serve the site from Framer while Squarespace can still be turned back on.

Recommended window: A low-traffic hour, with DNS access and the XML still on disk.

  1. Publish the Framer site with redirects in place.
  2. Request three dated post URLs and the homepage on a preview.
  3. Point DNS at Framer.
  4. Request the same URLs on the public domain.
  5. Leave the Squarespace site published.

Proof to capture: The public homepage and three old posts load from Framer, and Squarespace is still available.

Return to safety

Rollback

Point the domain back at Squarespace before you cancel it.

Deadline: Before you cancel Squarespace or delete the export.

  1. Restore the previous DNS records.
  2. Confirm the Squarespace site still answers.
  3. Leave the Framer project and the XML in place.
  4. Write down which URLs failed.
  5. Fix those pages before the next attempt.

Proof to capture: The public site is Squarespace again, and Framer is not receiving the domain.

Rollback immediately when
  • An old post URL 404s
  • An image still loads from Squarespace
  • A second blog or the shop was forgotten
  • Redirects did not apply after publish
  • The homepage is the wrong design
08Verification report

Prove the migration worked.

Every blocking check must pass. Capture the evidence before cleanup begins.

0%
Interactive report preview0 / 8 checks passed
PassIDCheckMethodExpected resultEvidence
V-01BlockingRight blogOpen the XML and compare post titles with the primary blog.The posts you meant to move are in the file.XML sample.
V-02BlockingPost countCompare Squarespace's post count with the Framer collection.Counts match, or the gap is the free 25-post cap you have not licensed past.Count sheet.
V-03BlockingLayout pagesWalk the public page list. Mark each one rebuilt or dropped.No public page is only in Squarespace.Page list.
V-04BlockingLocal filesOpen three posts and load an inline image with Squarespace blocked in the browser.The image still loads.Asset check.
V-05EmbedsOpen a post that had YouTube or Vimeo, and one that had a gist.Video plays. The gist is a link, if that is what you accepted.Post notes.
V-06BlockingDated URLsRequest three old /blog/year/month/day/slug URLs after publish.Each one lands on the new post.Redirect log.
V-07BlockingApex and wwwRequest both hostnames.The old host redirects the domain, and Framer serves the paths.DNS notes.
V-08BlockingSquarespace still upOpen the Squarespace admin and the public site on its Squarespace domain.You can still point DNS back.Admin screenshot.
09Post-migration cleanup

Remove the scaffolding safely.

Safe after: A week of quiet 404s, with images loading from Framer and Squarespace still billed until you cancel it on purpose.

  1. Archive the XML, the CSVs, and the URL list.
  2. Remove unused Framer CMS fields from the import.
  3. Update redirects if you renamed any CMS paths.
  4. Cancel Squarespace only after the image check.
  5. Keep the plugin license note with the project.
10Experiences from the field

When the plan met reality.

First-hand accounts are preferred. Vendor case studies are labeled, and every note below is an editorial paraphrase—follow the link for the full context.

First-person accountcosmefae · Reddit

A 2024 portfolio post priced Squarespace Business against Framer Basic2024

On 2 August 2024, cosmefae posted in r/framer that a portfolio was leaving Squarespace for Framer after years on Squarespace. The prices in the post are Squarespace Business at about $20 a month, about $248 a year, and Framer Basic at about $9 a month, about $114 a year. Those are the poster's 2024 figures, not a current price list. The other reason is design control, including CSS and JavaScript limits on Squarespace. The next day, frenchhie wrote that the same reasons prompted a switch in June, and that they were not going back. The thread does not describe an export file, images, or redirects.

What they recommend
  • Check today's Squarespace and Framer prices yourself. This thread is one portfolio's 2024 comparison.
  • Use the post for why a designer leaves, and use Squarespace's export help for what the XML actually contains.
Worth noticing
  • The move described is a portfolio site, with a public URL, not a shop or a second blog.
  • frenchhie's reply is another first-person switch, still without a content checklist.
Sources and evidence

Verify against the primary material.

Platform behavior changes. Check these sources and the review dates above before executing a production migration.

  1. Squarespace: export your site contentAccessed 2026-11-01
  2. Squarespace: import and export overviewAccessed 2026-11-01
  3. Framer marketplace: Squarespace ImportAccessed 2026-11-01
  4. Framer: redirectsAccessed 2026-11-01