Squarespace to Wix Studio: the complete migration guide

Partly. Squarespace gives you one .xml file in WordPress format containing your layout pages, one blog and its posts, and your text and image blocks. It leaves out index, portfolio, album, cover, info, calendar, and store pages, plus audio and video blocks, drafts, style settings, and custom CSS. So the words come across and the site doesn't. Everything the XML omits gets rebuilt, which is most of the visual design.

On its own, no, and it's worth being precise about what happened because the reporting was messy. In July 2026 Squarespace raised annual list prices by up to around 26%, with Core going from $23 to $29 a month and Plus from $39 to $49, according to trade press including PetaPixel and TechRadar. Squarespace published no announcement and told customers by email, then later apologised for what it called a pricing implementation error that overstated the increase for some plans, saying no customer was incorrectly charged. It told TechRadar it had recently added capabilities to every plan that were previously on higher tiers. So the honest read is a real increase, imprecisely communicated. A price rise is a good moment to reassess and a bad reason to rebuild on its own. What makes the move worth it is everything else on this page: what your export doesn't contain, and what your template stops you doing.

Not if the URLs are handled deliberately, and fewer of them have to change than most people assume. Standard pages keep their slugs, so /about stays /about. Blog posts come down to one build decision: Wix's Blog app forces a /post/ prefix that can't be removed, while a blog modelled on the Wix CMS lets you set the prefix and keep your existing /blog-name/post-name paths. Whatever does change gets a one-to-one redirect, tested against the URL inventory before the domain moves, then watched in Search Console for 30 days after.

Only one exports. Squarespace prompts you to select a primary blog page and the rest aren't in the file. We capture the others by crawling the live site before anything is switched off, which works fine but has to happen while the site is still up. It's the most common thing to discover too late on this migration.

Physical and service products come across through a separate CSV export, not through the XML. The CSV leaves out additional product information, customer reviews, featured images, product image alt text, and variant images, so budget a pass to re-attach those. Digital products have no export at all and get rebuilt by hand. Orders export for your records but can't be imported anywhere.

Three to five weeks of active work for most sites, then a 30-day monitoring window that runs after you're already live. The blog archive is what moves that number: a site with fifteen posts and one with four hundred are different projects, because every post needs a mapped redirect either way.

For a small site with a short blog, yes. The trap is that the export looks like a complete backup and isn't, so the DIY question here is really "how much of my site is in the file?" A five-page brochure site with no store is a reasonable weekend project. A single blog with thirty posts is manageable, though on the Blog app you'll be mapping thirty redirects by hand. Beyond that it turns: a second blog page, an index or portfolio page, a store, a members area, or a few hundred posts each move it into territory where what you don't notice missing costs more than the help. The reliable signal is your blog archive. If it earns traffic, the URL decision is the one worth getting help with, and it's the part people skip.

Your standard pages keep their addresses. Squarespace uses clean, flat paths for regular pages and Wix Studio imposes no structure of its own, so /about stays /about and a brochure site needs almost no redirect work. Your blog depends on how it gets built. Wix's Blog app puts every post under a /post/ prefix that can't be removed, so on a site with two hundred posts that's two hundred mapped redirects. A blog modelled on the Wix CMS lets you set the prefix and the slug, which is how an existing /blog-name/post-name structure survives the move untouched. The quieter risk is metadata, which doesn't travel in the XML at all, so titles and descriptions get re-entered and diffed against the old site before the domain moves.

From €1,250, quoted as a fixed price before any work starts. What moves the number is almost entirely the blog: every post needs its own mapped redirect, so a fifteen-post site and a four-hundred-post site are different projects. After that it's the store, since products come across by CSV and then need their reviews, alt text and variant images re-attached by hand, and any page types Squarespace refuses to export at all.

WordPress solves the ceiling by handing you a maintenance job: plugin updates, security patching, hosting. Webflow solves it but leaves editing to whoever understands the class system, which recreates the bottleneck you're leaving. Studio gives you the responsive control and the CMS without either, and the people who write your content can publish it. If you want the custom-code answer instead, we build those too, and we'll say so if that's what your case actually calls for.

Yes, and it's the default. The Studio build lives on a staging URL while Squarespace keeps serving your domain, so there's no maintenance page and no gap in enquiries or sales. You sign off on a working site you can open on your own phone. The domain moves in a single afternoon at the end, once the redirect map has been tested.