The short answer
Moving from Squarespace to WordPress is very doable, but it is not a one-click transfer. Squarespace’s export brings across some of your content and leaves a lot behind: most page types, product pages, style settings, and custom code. The parts that decide whether the move goes well are the ones no export touches: mapping every old URL to a new one, setting up permanent redirects, rebuilding forms and booking, and watching Google Search Console after launch.
Plan for it as a rebuild with content carried over, not as a file you download and upload.
Why businesses make the move
Usually because the site has outgrown the template. Squarespace is good at getting a clean site live quickly. It gets harder when a business needs page layouts the template doesn’t offer, a larger set of service pages with their own structure, custom code, or more control over technical SEO. If you’re still deciding whether WordPress is the right destination, read is WordPress still a good choice for a business website? first. Moving platforms to fix a problem that a better-organized Squarespace site would solve is an expensive detour.
What Squarespace’s export includes, and what it doesn’t
Squarespace can export a site to an .xml file in WordPress’s format. Per Squarespace’s own help article, the export includes:
- Layout pages (regular pages)
- One blog page, with its posts and comments
- Text and image blocks
- Text from embed and Instagram blocks, with minimal structure
- Gallery pages, on version 7.0 sites only
And it does not include:
- Other page types, including store, portfolio, calendar, index, and album pages
- More than one blog (you choose a primary one)
- Product, video, and audio blocks
- Content in page-specific headers, footers, and sidebars
- Drafts
- Style settings and custom CSS
Two practical conditions: the site has to be published with its availability set to Public, and trial sites can’t export at all. If a site has expired, Squarespace warns that its content may already be deleted, so export before you let the subscription lapse.
In practice, the export is most useful for a blog. A typical small-business site’s service pages, homepage, and contact page will need to be rebuilt in the new theme anyway, because none of the Squarespace design comes with them.
Importing into WordPress
On a self-hosted WordPress site, the .xml file goes in through the WordPress Importer plugin, which brings in posts, pages, comments, categories, and tags.
Images are the catch. Squarespace’s help article is direct about it: on a self-hosted WordPress site, “your images might not migrate.” WordPress may pull reference links to the images instead, and those links “stop working after you cancel your Squarespace site.” Its suggestions are to import into WordPress.com instead, or to download the images manually and upload them to WordPress.
So keep the Squarespace subscription active until every image on the new site is confirmed to be served from WordPress, not from Squarespace. A search of the imported content for Squarespace image addresses is a quick way to check. While you’re handling images anyway, this is the moment to resize and compress them and write proper alt text, rather than carrying over oversized originals.
URL mapping and 301 redirects
This is the part that protects your search visibility, and it is the part most often rushed.
Some addresses will almost certainly change when the site is rebuilt, so the plan has to account for every one. Google’s guidance on site moves with URL changes is to map every old URL to its new one, and to use permanent server-side redirects (301 or 308) from each old address straight to its final destination, avoiding chains of redirects. A workable process:
- Inventory every old URL. Pages, blog posts, category and tag pages, image galleries, and anything linked from outside the site, including your Google Business Profile, directory listings, and old emails.
- Map each one. Either to its direct replacement, or, if a page is being retired, to the closest relevant page. Sending everything to the homepage throws away the context Google had for each page.
- Keep the URL where you can. If
/services/consultationscan stay/services/consultations/on WordPress, that’s one less redirect to depend on. - Test the redirects before and after launch. Each old URL should land on the right page in one hop.
- Leave them in place. Google recommends keeping redirects as long as possible, generally at least a year.
Also update internal links on the new site to point at the new URLs directly, rather than relying on the redirects.
Forms
Squarespace form blocks don’t move. They need to be rebuilt in WordPress, and the destination of each submission set up again. Before you switch, download your past submissions: Squarespace lets you export a form’s submissions to a .csv file. It’s worth doing promptly, because a form without a required email field only keeps each submission for 30 days.
Test every form on the new site end to end, including whether the notification email actually arrives, before you point the domain at it.
Commerce and scheduling
Products. Squarespace can export physical and service products to a .csv, up to 10,000 of them, but the file leaves out featured images, variant images, image alt text, and customer reviews. Order history exports separately. Expect to rebuild the store in a WordPress commerce plugin and reattach images by hand, and decide in advance what happens to reviews.
Booking. If you use Acuity Scheduling, it runs on its own account, and Squarespace’s help notes that Acuity can be used separately from Squarespace. The booking system usually stays where it is; what changes is how the new site embeds or links to it. Confirm that before launch, not after.
Launch: staging, then the domain switch
Build the new site on a staging copy where it can be reviewed and tested
without affecting the live one. Staging sites are often blocked from
search engines, and Google’s site-move guidance specifically calls out
removing any noindex rules and robots.txt blocks that were only needed
during development. Forgetting this is one of the most common reasons a
newly launched site disappears from search.
On the day: point the domain at the new hosting, confirm the SSL certificate, check the redirects, and test forms and booking again on the live domain.
After launch: Search Console
If the domain stays the same, Google Search Console carries over, but the work isn’t done. From Google’s site-move documentation:
- Submit the new sitemap with the new URLs.
- Use the URL Inspection tool to check individual pages that seem to be missing.
- Watch for “Not found” errors, which usually mean an old URL without a redirect.
Be patient. Google says that for a medium-sized site it “can take a few weeks or more” for the new URLs to show up in its results, and that fluctuations along the way are normal. A careful migration keeps what the old site had earned. It doesn’t, by itself, improve rankings; that comes from the better structure and content the move made possible.
An example: Lily Lane Aesthetics
Lily Lane Aesthetics, a medical-aesthetics practice in Houston, started as a refresh of its existing Squarespace site. As the work progressed, the layouts, mobile experience, and service structure the practice needed kept running into template limits, and the project expanded into a WordPress redesign and migration. Content worth keeping was carried over from Squarespace. Redirects from the retired Squarespace URLs were planned before anything moved, and the new site was built on a staging environment, with DNS, SSL, and forms tested at launch. The Lily Lane Aesthetics case study covers why the refresh became a migration.
Doing it yourself, or getting help
A small site with a handful of pages and no store is a reasonable do-it-yourself project if you’re careful with the redirect list. A site with a store, booking, many blog posts, or pages that already bring in search traffic has more to lose.
Webbify’s website migration work starts with the URL inventory and redirect map, and the new site is built as a custom WordPress theme rather than a template. If the crawl and indexing side is the part you’re unsure about, that’s covered under technical SEO.