Information checked: 21 July 2026.
Squarespace can export certain content in a WordPress-compatible XML format, but the export does not recreate the full site. Templates, many page types, product behaviour, styling and integrations still require a planned WordPress rebuild.
In brief: Use the Squarespace export as one input to a WordPress rebuild; it is not a complete site-transfer package.
Understand the export boundary
| Item | Available route | What still needs checking |
|---|---|---|
| Supported pages and blog content | Squarespace XML export | Blocks, formatting, images and internal links |
| Products | Separate CSV export | Variants, images, stock, tax and shipping |
| Design and templates | Manual rebuild | Responsive behaviour and reusable components |
| Members and subscriptions | Service-specific process | Passwords, consent and recurring billing continuity |
| Forms and newsletters | Manual recreation or separate export | Delivery, consent records and automations |
| Domain | Reconnect or transfer | DNS and email must be protected |
Prepare WordPress as a maintained system
Choose hosting, backups, staging, a supported theme and the smallest practical plugin set. Import into staging, not directly into a public production site.
Clean the imported content
Check every imported post and page for headings, image paths, excerpts, categories, dates and author attribution. Rebuild unsupported layouts with native blocks or maintainable components rather than embedding the old site.
Map URLs and redirects
Export or crawl the existing URL list. Preserve slugs where appropriate and create direct permanent redirects for every meaningful change. Validate status codes, canonicals and sitemap output before launch.
Handle commerce and subscriptions separately
Product CSVs do not automatically reproduce payments, customer accounts, subscriptions or order history. Define which records must remain accessible and how recurring customers will be treated before cancelling the old service.
Final validation
Compare page counts and product totals, test forms and checkout, inspect mobile pages, connect the domain and monitor Search Console. Keep the Squarespace site available until the acceptance checklist is signed off.
Example: an XML import that appears complete
The import reports success, but gallery blocks become plain links, images remain remotely hosted and summary pages have no equivalent. Review imported content type by type and build a conversion log. An automated import should reduce manual work, not conceal unsupported blocks that visitors discover after launch.
What the business should retain
- Squarespace XML and product exports
- Unsupported block report
- Media-localisation check
- URL and redirect map
- Commerce and subscription record plan
Sources and date checked
Technical and product information was checked against the following primary sources on 21 July 2026. Plans, interfaces and provider terms can change, so recheck them before purchase or migration.
Keep the decision under your control
Retain the relevant accounts, source material, supplier terms and recovery information. Recheck changing prices, interfaces and rules before acting.