What the Squarespace export does
Squarespace can produce a WordPress-format XML file for selected content. Treat it as one extraction path. The migration still needs to confirm what the file contains, inventory what it omits, map the destination, transfer accessible assets, and validate the rendered result.
The export does not become a Squarespace theme for WordPress and does not reproduce platform applications or business workflows.
What can move and what needs separate work
| Squarespace item | WordPress path | Status |
|---|---|---|
| Blog posts and supported pages | Posts, pages, or prepared custom types | Standard with source review |
| Authors, categories, and tags | Users and taxonomies | Map identity and relationships |
| Comments | WordPress comments | Review availability and post relationship |
| Accessible images and files | Media Library and rewritten references | Validate every download and upload |
| Profiles | CRM, users, customers, or custom records | Restricted custom scope |
| Multiple blogs, galleries, and special blocks | Posts, galleries, blocks, fields, or rebuild tasks | Review or custom transformation |
| Commerce, scheduling, memberships, and email | Plugins, services, or custom applications | Custom scope |
| Templates, styles, forms, scripts, and animations | Theme, blocks, plugins, and code | Rebuild, not export |
Inventory beyond the XML file
Crawl the live site and combine the results with sitemaps, analytics landing pages, Search Console data, backlinks, media lists, navigation, campaign URLs, and business-owner review. Compare that inventory with the export so omitted pages, blocks, and assets remain visible.
Record every item as migrate, transform, rebuild, archive, consolidate, or exclude. Restricted profiles and personal records need approved purpose, minimization, secure access, destination ownership, retention, and deletion rules.
Prepare WordPress before importing
- Create protected staging and required backups.
- Define destination post types, fields, taxonomies, author rules, comments, media settings, SEO storage, and plugins.
- Implement templates that render representative migrated content.
- Confirm authentication, upload limits, file types, permissions, and rollback ownership.
- Approve final URL patterns before redirects and internal links are generated.
Map and import representative content
Record source identity, value, format, WordPress destination, transformation, dependency, fallback, and validation rule. Load authors and taxonomies before records that reference them, and preserve stable identifiers for reruns.
Import simple and complex examples from every included type. Test long articles, several authors and terms, comments, galleries, remote media, unusual markup, old dates, drafts, and known exceptions. Fix systematic rules before full volume.
Validate before the source is closed
Reconcile extracted, loaded, skipped, rejected, failed, and unresolved totals. Inspect field accuracy, relationships, comments, media delivery, internal links, metadata, rendering, editability, and destination workflows.
Complete the final or delta run, apply tested redirects, verify priority journeys, analytics and forms, and keep Squarespace available until acceptance and rollback conditions pass. Use the SEO checklist and cost guide for connected planning.