The export is partial by design
Squarespace exports blog posts, text and image blocks on standard pages — and skips product pages, events, albums, audio and index/portfolio pages. Knowing what will not arrive is half the job.
Migration · Squarespace → WordPress
Squarespace is polished until you need something it does not offer — deeper SEO control, real plugins, ownership of your stack. It does provide an export, but a partial one, and the gaps catch people out. We move the content, recover what the export skips, and redirect every URL so nothing is lost on the way.

Why switch
Squarespace templates are elegant but closed. Custom layouts, custom functionality and third-party integrations all hit the same wall.
Monthly fees buy a lease, not an asset. On WordPress the software is yours and hosting is commodity.
The export covers some content types and not others — the platform decides what you can take with you.
Structured data, performance work and technical SEO are only adjustable within what Squarespace exposes.
What moves
The Squarespace specifics
Every platform has traps that generic migration checklists miss. These are the Squarespace-specific ones — the difference between a clean move and a rescue job.
Squarespace exports blog posts, text and image blocks on standard pages — and skips product pages, events, albums, audio and index/portfolio pages. Knowing what will not arrive is half the job.
The XML references images on Squarespace servers. If the subscription lapses before assets are pulled, they are gone. We download everything first, at original quality.
Squarespace index/portfolio stacks are a platform-specific layout. They are rebuilt deliberately in WordPress — usually better — rather than translated automatically.
Member Areas content and store data do not travel in the XML. Stores migrate via a separate product/customer path (or to WooCommerce properly).
Squarespace blog URLs (/blog/post-slug with date variants) need explicit mapping to WordPress permalinks, or the blog loses its search equity.
Process
Every migration is a parallel build: your Squarespace site keeps running while the new WordPress site is built and verified beside it. The switch is a planned window, not a leap.
Questions
If your situation isn't covered here, send us the details and we'll reply with a straight answer.
Partially. The XML export covers blog posts and standard page text, but skips products, events, albums, index pages — and the image files themselves. A complete migration combines the export with direct extraction of everything it leaves behind.
Yes, but not via the export — it only references files hosted on Squarespace. We download every image at source quality and re-host it in your WordPress media library before your subscription ends, so nothing is orphaned.
Yes — store data (products, customers, orders) travels a separate route from the content export, into WooCommerce. That turns the move into a store migration with its own checklist, which we scope alongside the content work.
Yes, with the same method as every migration we run: full URL inventory, one-to-one 301 redirects including Squarespace’s blog URL variants, and metadata parity checks before launch. Rankings follow content when the redirects are right.