Moving from Squarespace to a Self-Hosted CMS (2026 Guide)

Squarespace is great until the month you realize you're paying rent on a site you don't actually own. If the transaction fees, locked templates, or that thin XML export file have you looking at the exit, this guide walks you through the whole move.

TL;DR: Moving from Squarespace to a self-hosted CMS means exporting your content (Squarespace's XML export only covers blog posts and basic pages), setting up your own hosting (roughly $5–$15/month), importing content, and mapping every old URL to a new one with 301 redirects. Budget a weekend for a small site, longer if you have hundreds of posts. You trade convenience for ownership: full code access, your own database, no platform fees, and no template walls. We use UnfoldCMS as the worked example below — disclosure: this is our product — but the steps apply to any self-hosted CMS.

Why people leave Squarespace

The three complaints that come up again and again: fees that scale with your success, templates you can't truly customize, and content you can't fully take with you. None of these matter on day one. All of them matter by year two.

Transaction fees. On Squarespace's lower commerce tiers, the platform takes a cut of every sale — historically around 3% on the Business plan, dropping to 0% only on the pricier commerce plans. If you sell anything, you're paying twice: the subscription and the toll.

Template limits. Squarespace templates look polished, but customization stops where the style editor stops. You can inject some custom CSS and code blocks (on paid plans), but you can't touch the underlying markup, change how a collection renders, or add server-side logic. If your design needs one thing the template doesn't do, you're stuck.

No code or data control. You can't access your database, run a query, add a custom field to posts, or move your media in bulk. Your site lives inside someone else's product decisions. When Squarespace changes an editor, deprecates a template family (as happened with the 7.0 → 7.1 split), or adjusts pricing, you adjust with it.

What "self-hosted" actually means

Self-hosted means the CMS software runs on a server you rent — and you hold the keys. You can read and edit every file, back up the full database, switch hosts whenever you want, and customize anything. In exchange, updates, backups, and security are now your job (or your developer's).

In practice, that looks like:

• You rent hosting — a shared PHP host or small VPS, typically $5–$15/month.
• You install the CMS — upload files, point a database at it, run an installer. With a modern PHP CMS this takes well under an hour. Our setup guide for a self-hosted CMS walks through it step by step.
• You own the stack — templates are real code files you can edit, the database is yours to query and export, and media lives on your disk.
• You maintain it — apply updates, keep backups, renew the domain and SSL (most hosts automate SSL now via Let's Encrypt).

If you're weighing this trade-off in general terms, we've written a longer comparison of self-hosted vs SaaS CMS platforms that covers the ownership question in depth.

What Squarespace lets you export (and what it doesn't)

Squarespace's built-in export gives you a single XML file in WordPress format — and it's limited. It includes blog posts, text/image/embed blocks, and one regular page collection. It does not include products, events, audio/video blocks, album pages, style settings, member areas, or your actual image files.

The fine print that catches people:

• Only one blog. If your site has multiple blog collections, only one exports. You'll handle the others manually or with a scraper.
• Images aren't in the file. The XML references image URLs still hosted on Squarespace's CDN. Once you cancel your subscription, those URLs can die. Download every image before you cancel.
• Products and commerce data export separately as CSV (products only — not orders in the same flow), and event pages don't export at all.
• Layouts don't transfer. The export carries content, not design. Your new site's look gets rebuilt in your new CMS's templates.

So plan for three buckets: content the XML covers (posts, basic pages), content you'll copy by hand or script (everything else), and design (rebuilt from scratch).

Step-by-step migration plan

A safe migration runs in this order: inventory, export, build the new site in parallel, import, download media, set redirects, switch DNS, then verify and cancel. Never cancel Squarespace first — keep it live until the new site is confirmed working and indexed.

1. Inventory your URLs. Crawl your live site (Screaming Frog's free tier handles up to 500 URLs) or pull /sitemap.xml. Save the full list — this becomes your redirect map later.
2. Export the XML. In Squarespace: Settings → Advanced → Import / Export → Export. Pick the WordPress format and download the file.
3. Download all media. Work through your image library and save originals locally. The XML only links to Squarespace-hosted copies.
4. Set up hosting and install your CMS. Cheap shared PHP hosting is fine for most content sites. Install the CMS on a temporary subdomain or local environment so you can build without touching the live site.
5. Import your content. Some CMSs read WordPress-format XML directly. If yours doesn't, convert the XML to structured data and push it through the CMS's API. (More on the scripted approach in the UnfoldCMS example below.)
6. Re-upload media and fix references. Replace every images.squarespace-cdn.com URL in your content with your own hosted copies.
7. Rebuild design and navigation. Recreate menus, the homepage, and key landing pages in your new templates.
8. Map redirects. Match every old URL to its new home (next section — this is the SEO-critical step).
9. Switch DNS. Point your domain at the new host. Keep TTL low (300s) the day before so the cutover propagates fast.
10. Verify, then cancel. Submit the new sitemap in Google Search Console, click through your top pages, watch the 404 log for a week or two — then cancel Squarespace.

SEO-safe redirects: don't skip this

Every old Squarespace URL needs a 301 redirect to its new equivalent, or Google treats your moved pages as dead and your rankings reset. This is the single highest-stakes step of the whole migration — a site that loses its redirects can lose most of its organic traffic within weeks.

Squarespace's URL patterns rarely match a new CMS's defaults. A Squarespace blog post lives at /blog/post-title or sometimes /blog/2024/3/14/post-title; your new CMS might use /blog/post-title too, or something else entirely. Either way, build an explicit map:

• Take the URL inventory from step 1.
• For each old URL, write the new URL next to it in a spreadsheet.
• Load that map into your new CMS as 301 (permanent) redirects.
• Redirect retired pages to the closest relevant page — not everything to the homepage (Google treats mass homepage redirects as soft 404s).

Two extra wins while you're in there: keep your image filenames descriptive when you re-upload (image search traffic transfers too), and resubmit your XML sitemap in Search Console the day you switch DNS so Google recrawls quickly.

Cost comparison: Squarespace vs self-hosted

Over three years, a self-hosted content site usually costs less in cash but more in attention. Squarespace runs roughly $200–$600+/year depending on plan; self-hosting runs roughly $60–$200/year for hosting plus whatever your CMS license costs (many are free or one-time purchases).

Note the maintenance row. That's the honest price of self-hosting, and it's why the decision isn't purely financial. WordPress users know this trade well — we've broken down the hidden costs of WordPress separately, and many of those line items (premium plugins, security services) apply to any neglected self-hosted stack.

Worked example: moving a blog to UnfoldCMS

Disclosure: UnfoldCMS is our product. Here's how the plan above looks with it as the destination — a Laravel-based CMS that runs on cheap shared PHP hosting, no background workers or VPS required.

Import. UnfoldCMS doesn't have a one-click Squarespace importer. Instead, it ships a versioned REST API at /api/v1/* with full admin write CRUD. The practical flow: parse the Squarespace XML with a short script (any language), then POST each post to /api/v1/admin/posts with a Sanctum token. A few dozen lines of code handles hundreds of posts, including categories and scheduled posted_at dates.

Redirects. The built-in redirect manager handles the SEO step: 301s and 302s, CSV import (so your spreadsheet map loads in one upload), hit tracking, and optional expiry dates for temporary redirects. Slug history is automatic too — if you rename a post later, the old URL keeps resolving.

SEO plumbing. Sitemap and robots.txt generate dynamically, JSON-LD structured data ships via Blade helpers, and uploaded images get WebP conversions out of the box. Search is database-backed — no external service to configure.

The rest. Scheduled publishing, threaded comments, and role-based permissions are all in the Core tier. See what's included at each tier →

For a broader look at running your own CMS long-term, the complete self-hosted CMS guide for 2026 covers hosting choices, backups, and maintenance routines.

Stay on Squarespace if...

Honestly, self-hosting isn't the right call for everyone. Squarespace earns its fee when zero-maintenance matters more than ownership. Stay put if any of these describe you:

• Nobody on your team is comfortable with hosting. If "update PHP" sounds like a chore you'll postpone forever, the platform fee is cheaper than a hacked site.
• Your store is the business. Squarespace's commerce stack (checkout, inventory, taxes) is built in. UnfoldCMS, for one, has no built-in ecommerce — you'd be wiring up your own store layer, which is real work.
• You change your site twice a year. A brochure site that rarely changes doesn't benefit much from code access.
• Design-by-dragging is the feature you bought. Self-hosted CMSs generally trade visual builders for template files. If you never want to see code, that trade runs against you.
• The math doesn't move you. Saving ~$200/year doesn't justify a weekend of migration plus ongoing upkeep for everyone. That's fine.

Leave when the platform is the bottleneck — fees eating margins, designs you can't build, data you can't reach. Stay when it's quietly doing its job.

FAQ

Does Squarespace export include my images? No. The XML file references image URLs hosted on Squarespace's CDN, not the files themselves. Download every image manually (or with a script) before canceling your subscription, because those CDN URLs aren't guaranteed to survive after your site goes offline.

Will I lose my Google rankings when I leave Squarespace? Not if you do redirects properly. Map every old URL to its new equivalent with a 301 redirect, keep your page titles and content substantially the same, and resubmit your sitemap in Search Console. Expect some ranking wobble for a few weeks, then recovery.

How long does a Squarespace migration take? A small blog (under ~50 posts) is a weekend project: export, import, redirects, DNS. Hundreds of posts, multiple collections, or a store pushes it to one or several weeks, mostly spent on media cleanup and redirect mapping.

Can I keep my domain when leaving Squarespace? Yes. If you registered the domain through Squarespace, you can transfer it to another registrar (after the standard 60-day lock from registration) or simply repoint its DNS to your new host while leaving registration where it is.

Sources

• Squarespace: Exporting your site — official docs on what the XML export includes and excludes
• Squarespace: Pricing plans — current plan tiers and transaction fee terms
• Google Search Central: Site moves with URL changes — Google's own guidance on 301 redirects during a migration
• Squarespace: Transferring a domain away — domain transfer steps and the 60-day lock