--- title: "Squarespace to WordPress Migration Guide" source: https://refact.co/insights/migration/squarespace-to-wordpress-migration author: "Masoud Golchin" date: "2026-06-12" --- # Squarespace to WordPress Migration Guide You will find the same five-step recipe in most Squarespace to WordPress migration guides: get your XML, put down WordPress, run the importer, choose a theme and point the domain. The steps are there, but they are the easy part of the job. The importer does not touch the hard stuff: the URLs, redirects, media ownership, ecommerce and form data, tracking, editor workflows or that first month post-launch when the search traffic tells you if the move was any good. So if you are thinking of making the switch in 2026, do not think of it as “moving a website.” Your mental model should be “partial content export and a parallel rebuild.” View it as a copy job and you will be busy righting wrongs in the first quarter after you go live. View it as a rebuild and it is manageable. ## When a Squarespace to WordPress Migration Is Actually Worth It There is a reason teams go with Squarespace in the first place. You get hosting, SSL and updates in one bundle along with an editor that keeps you in line. The numbers bear it out. A 2026 analysis from Candid Creative of millions of sites shows a WordPress site is about 1.8 times less likely to make the grade on mobile Core Web Vitals than one on Squarespace, Wix or Duda. Even with a heavier median JavaScript payload, Squarespace’s real-world performance is better because the platform enforces discipline on templates and hosting. Which makes the usual justification for migrating – “WordPress will be faster and better for SEO” – a weak one. On its own it is seldom true. Your rankings and speed are a function of how you handle plugins, your theme, your hosting and whether you preserve your URLs at cutover. Do a poor job and you have made both worse. Only migrate if you can put your finger on something Squarespace is not doing well. Good reasons tend to be of this nature: - You have a content model for directories, research libraries or product catalogs that calls for custom post types and taxonomies. - An LMS or paywalled content that requires more than what Member Areas offer. - Ecommerce operations with variants, subscriptions or third-party integrations that have left Squarespace Commerce behind. - Editorial needs like an editorial calendar, scheduled publishing and custom roles for multiple authors. - Server-side webhooks or fine-grained tracking that demand custom endpoints. If you are lured by the promise of “more flexibility,” hold off. Unused flexibility is just an operational cost. Once you cut over, backups, security and plugin compatibility are your problem, not someone else’s. ## What Actually Transfers From Squarespace, and What Does Not Then there is the matter of the official export. It is a WXR-style XML file and narrower in scope than you might think. Squarespace will give you blog posts (one at a time), some pages and comments, and will flatten a few gallery pages into images. But it leaves out the business logic: no Commerce products or orders, no discount rules, no email campaigns or form submissions, and certainly none of the layout and styling. They market it as being able to move “most of your content,” but most of your business is not content. Media is where projects have a way of breaking without fanfare. The XML will have image references to static1.squarespace.com. The WordPress importer sees those as external and lets them render while your Squarespace account is active. Cancel the subscription and half your site goes dark. You need to crawl and download every image to the Media Library and rewrite the references before you launch. And don’t count on the design to come over. Squarespace templates are tied to the platform; their block semantics and animations do not translate. Trying for a pixel-perfect match in Gutenberg is a waste of time. > Call it “content and URL migration plus a parallel redesign.” That is the only way to frame it that does not understate the work involved. ## URLs Are the Real Unit of Migration But here is what you should take away from this guide: backlinks and search engines are concerned with URLs, not pages. Change a URL and you do not have a redirect in place, and your rankings will suffer. We hear from SEO agencies and managed hosts all the time about 20 to 40 percent drops in organic traffic on migrations where the content was fine but the URLs were mishandled. Squarespace has its own conventions for these things. A blog post is /blog/post-title/, a product is /products/product-name/. WordPress can mimic some of that with permalinks but not all of it; you will have to put in the work to get pagination and tag archives to align. Approach it as infrastructure: - Use Screaming Frog to crawl the live site and cross reference with Search Console coverage. Get every URL that has ever put in an appearance or earned a link. - Make a spreadsheet to map old to new. Put in the custom slugs, the image URLs that drive traffic and the category pages. - Put 301 redirects in at the server level with an .htaccess or nginx rule. If you have a large site, do not rely on a plugin to store everything in autoloaded options or you will have a memory issue on your hands. - Crawl to verify before you go and again 48 hours in. Then let the “not found” and “crawled, not indexed” reports in Search Console be your watch for the next few weeks. It is the kind of discipline that [keeps a redesign from quietly costing you SEO](https://refact.co/insights/publishing-growth/redesign-website-without-losing-seo). There is a common thread to why migrations and redesigns go wrong: the team regards URLs as a UI nicety rather than the ledger search engines rely on to make sense of your site. ## Planning the Migration Before You Export Anything You can tell a failed migration from a mile off by the export button. The ones that are done right begin with an inventory. Put pen to paper and list everything that is there. We are talking pages, blog and product posts, members, forms, tracking pixels, gated assets, newsletter tie-ins, thank-you pages, internal links, image alts, structured data. Once you have it all down, put it in one of three buckets: - **Must move:** Revenue earners, anything with backlinks or rank, legal copy, forms for lead flow and active campaigns. - **Should improve:** Slow templates, awkward mobile views, broken nav, content that is thin or past its prime. - **Should die:** Old launch pages, duplicates, experiments you have abandoned. A migration is the perfect cover to let dead weight go without a fuss. Then pick your new stack before you start building. People do not give managed WordPress hosting enough credit. According to Candid Creative’s attribution, 40 to 50 percent of the Core Web Vitals chasm between Squarespace and WordPress comes down to hosting; page builders account for another 20 to 30 percent and plugin bloat the rest. Go with cheap shared hosting and a bloated page builder and you will end up with a slower site than you had. A light theme like Kadence or GeneratePress on a managed host with a modest set of plugins won’t. Treat the launch window like a product release. You want to lower the DNS TTL a day or two prior so the cutover propagates quickly. If you are not up on your DNS records, have a look at this [DNS records and configuration guide](https://themailx.com/blog/dns-guide) before launch week. BigScoots will tell you propagation can be 24 to 48 hours, which is no way to run a cutover the night before a campaign. For the nitty-gritty on scope and timelines, we have laid out what a properly handled migration entails on our [WordPress migration services](https://refact.co/insights/wordpress/wordpress-migration-services) page. ## The Process, With the Parts That Usually Break The technical side of things is well covered. [Kinsta has a seven-step guide](https://kinsta.com/blog/squarespace-to-wordpress/) that is hard to fault: install WordPress, get the XML from Squarespace, import it, sort out the authors and permalinks, point the domain. [BigScoots’ playbook](https://www.bigscoots.com/blog/migrate-squarespace-to-wordpress/) follows the same pattern but with more focus on UAT and staging. What they don’t always spell out is where the process has a habit of breaking down. **Do your WordPress install on staging.** Put a password on it or noindex it. You need a parallel environment, not a work in progress for the public to see. **Make a dry run of the XML import.** Pull in a single blog and a few pages to see how the importer handles your tags, embeds and code blocks. Inspect the HTML. Those inline classes from Squarespace mean nothing to WordPress. **Sideload your media ahead of the second pass.** You need a WP-CLI script or plugin to take every `static1.squarespace.com` reference and put it in the Media Library. Block the CDN locally and reload to make sure the images hold up if you were to cancel Squarespace. **Know your post types before you import.** Have a plan for how products or directories map to ACF fields. Trying to refactor default posts after the fact is costly. **Don’t leave permalinks for later.** Changing them once content is live will tangle your redirect map and break internal links. **Have the redirect map ready when you flip the switch on the DNS.** Don’t wait around to see what 404s pop up. > When a migration is any good, it is boring. Boring is the redirect map doing its job, the editor putting out copy on day one and the forms still feeding the CRM. ## Ecommerce, Memberships, and Forms Are Rebuilds, Not Migrations Scope changes if your Squarespace site is used to gate or sell things. WooCommerce can’t make use of the order history, subscriptions or payment tokens that Squarespace Commerce won’t let you export. You might be able to push some products through a CSV with a bit of manual tidying of variants and IDs, but the rest is a data engineering exercise involving API work and telling customers what is and isn’t coming over. Our [WooCommerce development agency guide](https://refact.co/insights/ecommerce/woocommerce-development-agency-guide) has more on that. Memberships are a headache. For PCI compliance, billing details and card tokens stay with your old processor. Your best bet is to re-onboard members with a coupon or free period while you rebuild in MemberPress or Restrict Content Pro and have them re-enter their info. Then there are forms, the silent killer. Rebuilding in Gravity Forms is simple. But if you don’t re-wire the email marketing and confirmation flows behind them, your leads will just stop. Test the whole chain – the autoresponder, the CRM entry, the note to the salesperson. A form that fails for two weeks will go unnoticed until the pipeline shows it. Same goes for tracking. Without a tag manager and an audit on launch day, you will find pixels duplicated or missing because WordPress wants you to put them in via GTM or a plugin, not centrally like Squarespace does. ## Performance and Editor Workflow After the Cutover You will hear that WordPress is faster than Squarespace. In many cases it is not, and for good reason: put cheap hosting with a heavy builder and an endless list of plugins on the table and you get the kind of performance gap the field data would tell you about. But we have seen what happens when you change the equation. Candid Creative took page builders off the same host and saw LCP times improve by 1.5 to 2.5 seconds. In the end, your hosting is more important than any one-off optimization. We follow three rules to make sure a new site has speed: - Go with managed WordPress hosting that is open about its TTFB figures. - Stick to Gutenberg and a light theme as your default. Only reach for a builder if the workflow calls for it. - Be judicious with plugins. They are dependencies and should have an owner and a purpose. Between SEO, caching, security, backups, forms and redirects you are covered. The rest has to earn its keep. Then there is the matter of editor shock once you cutover. Squarespace puts limits on your editors; WordPress gives them a lot of surface area to work with. If you do not have locked templates or custom roles in place, along with a little training, they will be breaking layouts by week two and balking at the very features you made the move for. We make a point of bringing editors into UAT and giving them a one-pager they will actually look at, showing them the three or four block patterns to use. We were there for it when we put together the [St. Louis Magazine’s CMS escape](https://refact.co/work/st-louis-magazine). Moving 30,000 articles was the obvious task. What made or broke the project was the editorial workflow, the URL preservation and the ad and newsletter integrations the team lived with daily. You see the same thing in our [work with Teton Gravity Research](https://refact.co/work/teton-gravity-research), where we had to migrate 10,000 pieces of content without the business missing a beat. ## Cost, Timeline, and When to Bring in Help As for cost, practitioners will put a small-business migration from Squarespace to WordPress at $500 to $2,000. Fine for a blog or brochure site with a tidy URL inventory and no ecommerce. Not a number you can rely on if you have products, members, custom types or a redesign in the mix. The real question is what a poor migration will set you back. On a lead-gen site, a 25 per cent drop in organic traffic for a quarter will run you more than the whole budget. Or a checkout that is down for a week. Or having to re-onboard a membership program because the initial build did not handle the coupon logic. DIY is all well and good if the site is modest and your team knows WordPress and can live with a couple of rough weeks after launch. But you want a partner if: - You have revenue, active SEO or lead flow to support. - You are doing a redesign or new ecommerce build at the same time. - There are memberships, custom content or a publishing operation involved. - Your people do not have the hours to put together the redirect map and monitor things post-launch. It is the same calculus we put forward in our [Wix to WordPress guide](https://refact.co/insights/migration/wix-to-wordpress-migration). Different platform, but the pattern of decision is unchanged. Getting the content over is easy; protecting your traffic and rebuilding the experience is the hard part. And remember, for rankings and authority the months after you go live are what count. This [piece on domain authority](https://domaindrake.com/blog/how-to-build-domain-authority/) is a good reminder that it is about consistency, not the platform you are running. If you are unsure whether your move from Squarespace is a simple content transfer or a full rebuild, Refact’s discovery process is designed to give you that clarity. We start our [website migration service](https://refact.co/services/website-migration) with a money-back guarantee on the planning so we have a solid cutover plan in hand before anyone hits export. ## FAQ ### What actually transfers from Squarespace to WordPress? Squarespace's XML export covers blog posts, basic pages, some galleries, some tags and categories, and some comments. It does not export Commerce products and orders, Member Areas, events, form submissions, email campaigns, or any design and layout. Treat the export as a starting point for content, not a copy of the site. ### Will my images transfer cleanly? Not by default. The XML references Squarespace's CDN (static1.squarespace.com), so images render at first but are not in your WordPress Media Library. When the Squarespace subscription ends, those references break. You need to sideload every image into WordPress and rewrite the references before cutover. ### Will the migration hurt my SEO? It can, badly, when URL mapping and 301 redirects are incomplete. Practitioners regularly report 20 to 40 percent organic traffic losses on migrations that ignored pagination, tag archives, image URLs, or older slugs. A full URL inventory plus 301s at the server or via a reliable redirect plugin is the single biggest determinant of SEO outcome. ### Will WordPress be faster than Squarespace? Not automatically. Field data from Candid Creative shows WordPress sites are about 1.8 times less likely to pass mobile Core Web Vitals than Squarespace. The gap is driven by hosting (40 to 50 percent), page builders (20 to 30 percent), and plugin sprawl (15 to 20 percent). Managed hosting, Gutenberg, and a small plugin set close the gap. ### Can my Squarespace store come over to WooCommerce? Products can usually move through a CSV with manual cleanup of variants, IDs, and images. Orders, customer accounts, subscriptions, discount rules, and payment tokens generally do not transfer. Plan for customer communication about order history and a re-onboarding flow for any recurring billing. ### How much does a Squarespace to WordPress migration cost? Practitioner-cited ranges for small-business sites sit between $500 and $2,000. Sites with ecommerce, memberships, custom content types, or a parallel redesign cost substantially more. The bigger cost is usually a poorly executed migration that drops traffic or breaks checkout, which can exceed the project budget within weeks. ### Do I need to cancel my Squarespace subscription right away? No, and you should not. Keep Squarespace running while you build, test, and validate the WordPress site on staging. Cancel only after you have confirmed media is sideloaded, redirects are in place, forms work end to end, and Search Console looks healthy for at least a couple of weeks after cutover.