Migrate Squarespace to WordPress: The Definitive Migration Guide

Squarespace is polished, opinionated, and easy to start with. It's also expensive to scale, restrictive on functionality, and completely tied to Squarespace's infrastructure. Every business that starts on Squarespace eventually runs into one of three walls: a plugin they need that Squarespace doesn't offer, a hosting cost that no longer makes sense at their traffic, or a workflow limitation that Squarespace's editor can't accommodate. On plugins: Squarespace's extensions marketplace is genuinely useful but a rounding error compared to WordPress's 60,000-plugin ecosystem. On cost: the Squarespace Business plan runs $23/month per site; Commerce plans run $27-$49/month. Comparable WordPress hosting runs $5-$15/month unmanaged or $30-$50/month fully managed with better performance. On workflow: every editorial change goes through Squarespace's editor, which is fine for solo operators and painful for content teams. Migrating to WordPress solves all three at once. You get the plugin ecosystem, you pay a fraction of the hosting cost at any scale, and your team gets wp-admin — a real editorial surface that scales from one editor to fifty.

Squarespace, like Wix, does not expose a complete self-hosted code export. The migration works differently from Webflow or Framer as a result. The pipeline takes your live Squarespace URL, boots a headless browser, and walks every route in the site's sitemap. For each route it captures the fully-rendered HTML, downloads referenced assets (images, fonts, CSS, JavaScript), and stores the captured page as a candidate template. In parallel, if you provide the XML export from Squarespace's Settings → Advanced → Import/Export panel, the pipeline pulls blog post content, categories, and tags from that file. This second source is used specifically for editable content, so posts land in WordPress with clean, structured markup rather than the sometimes-messy HTML that comes out of the browser crawl. The converter merges both sources into a coherent WordPress theme: shared header and footer extracted into `header.php`/`footer.php`, static pages mapped to `page.php` templates, blog posts populated from the XML into WordPress's native Posts, custom post types registered for any Squarespace collections that aren't the blog, and a `functions.php` that ties it all together.

Cleanly: layouts, typography, colors, spacing, breakpoints, images, presentational CSS animations, hover states, form styling, blog post content, and product images. The captured HTML preserves all of these because they were part of the rendered page. Needs rewiring: Squarespace-hosted services like Scheduling (replace with Amelia or Bookly), Commerce (replace with WooCommerce), Member Areas (replace with MemberPress or Paid Memberships Pro), and Email Campaigns (replace with MailPoet, Brevo, or ConvertKit). Each of these is a straightforward substitution — the design of the pages hosting the service is preserved; the underlying service is swapped. Does not survive: any custom Squarespace code injection that referenced Squarespace-specific data attributes or CSS classes. Those markers are Squarespace-only and get stripped during migration. If a specific feature depended on them, rebuild it in WordPress as a small plugin or theme customization.

Do these four things in Squarespace before starting the migration. First, publish every page you want migrated — unpublished pages are invisible to the crawler. Second, export the XML file via Settings → Advanced → Import/Export → Wordpress (yes, Squarespace's export format is technically labelled 'Wordpress' inside the Squarespace UI). Save the XML locally. Third, if you're on Squarespace Commerce, export the product catalogue as CSV via Commerce → Inventory → Export. Fourth, temporarily disable password protection on any password-gated pages during the crawl window so the crawler can reach every URL. If your site is bigger than a hundred pages, tell the crawler which sections to skip by editing the site's `robots.txt` before the migration starts. Excluding heavy archive pages or duplicate paginated views keeps the crawl budget focused on the templates that matter.

Paste your Squarespace URL into the AI to Wordpress live-site converter and (optionally) attach the XML export. The pipeline detects Squarespace from characteristic markers in the rendered HTML (Squarespace's CDN URLs, `data-block-type` attributes, `sqs-*` CSS classes) and applies Squarespace-specific patches: stripping Squarespace's tracking scripts, replacing Squarespace's asset CDN with local mirrors, and mapping known widget patterns to WordPress equivalents. The crawler walks every route, captures rendered HTML, extracts shared shell into `header.php` and `footer.php`, generates templates for each unique page type, and emits a `functions.php` that registers menus, image sizes, and — if the XML export was provided — a WP-CLI script that imports blog posts on activation. Before you pay, the theme boots inside a WordPress Playground instance in your browser. Click through every page, every blog post, every product, every form. If anything looks wrong, fix it at source and re-run. If everything looks right, pay €17 and download the theme ZIP.

Upload the theme via Appearance → Themes → Add New → Upload and activate. Recreate menus via Appearance → Menus. Set the home page under Settings → Reading. If the migration included an XML import, run it via Tools → Import → WordPress (upload the XML file) — this populates blog posts with their content, categories, tags, and featured images. For Squarespace Commerce migrations, install WooCommerce and import products via WP All Import from your Squarespace CSV export. WooCommerce owns cart, checkout, tax rules, shipping zones, and payment gateways — reconfigure each of these to match your Squarespace setup. Budget half a day for this step on a real store; it's not automatic, but it's well-trodden ground with excellent documentation. For forms, install WPForms, drop shortcodes onto migrated pages, and route submissions to the same email or CRM as before. For analytics, install MonsterInsights or Fathom. For SEO, install Rank Math and enable XML sitemaps. For scheduling, install Amelia or Bookly. For memberships, install MemberPress or Paid Memberships Pro. Each of these takes 20-60 minutes to configure.

The migrated theme preserves your Squarespace URL structure exactly — every path the crawler walked lands at the same path in WordPress. Blog post URLs (`/blog/{slug}`, `/journal/{slug}`) match Squarespace's slug structure. Product URLs match Squarespace Commerce's URL structure. That means, in the common case, every inbound link continues to resolve without a redirect. If you're also moving from a `squarespace.com` subdomain to a custom domain (or between custom domains), install Redirection and import a CSV of `old_url,new_url` pairs. Submit the new sitemap in Search Console within 24 hours and request indexing for the top ten pages by traffic. In our data, sites re-index inside one to three weeks. Rankings usually improve because WordPress emits richer structured data than Squarespace (breadcrumbs, article, organization, product), and because cached WordPress pages hit sub-500ms TTFB where Squarespace's dynamic rendering typically sits at 700-1000ms. Both are signals that nudge rankings up.

Three things get better the day after cutover. First, your monthly hosting bill drops from Squarespace Business or Commerce pricing to WordPress hosting pricing, a difference that compounds every year the site is up. Second, your team gets wp-admin — a real editorial surface with permissions, revisions, and workflows that Squarespace's editor can't match. Third, your feature ceiling disappears. Every plugin in the WordPress ecosystem is now available: complex commerce, advanced analytics, multi-language, memberships, custom automations, learning management, event ticketing, booking systems. The design didn't change, the URLs didn't change, and the visitor experience didn't change. What changed is the platform you're building on. You've moved from renting a site on Squarespace to owning a site on WordPress, and every future decision — from adding a feature to switching hosts to internationalising — is now yours to make.