Squarespace → WordPress
Analyze and move supported Squarespace content into a prepared WordPress site through explicit extraction, content-model mapping, asset handling, URL planning, dry runs, validation, and controlled cutover. Design, commerce, and platform-specific blocks remain separate implementation scope.
Self-service migration path
Source and target connectors are available. squarespace: Available. wordpress: Available. Review system status and directions. Available migration objects and capabilities depend on the selected source and target systems.
Create an account, connect a staging destination, and let the app analyze the supported scope for this direction.
No credit card required to analyze the migration and run a free sample.
Scope
The app confirms available entities after connection. Final coverage depends on source access, downloadable assets, and the destination model you prepare.
Before you connect
Use a staging destination and the least-privilege access supported by each platform. Do not send credentials through a public form.
Provide an active public site URL. Public extraction and crawl coverage are tested before the project relies on them.
Provide the current WordPress-format export when available. Comments, profiles, private records, or additional source access are accepted only through an approved secure path.
Provide a prepared staging site and an Application Password. Custom post types, fields, taxonomies, SEO storage, and templates must exist before loading.
How it works
You control each stage in the app. Optional expert assistance is available for custom data or destination requirements.
Start in the app and select the real source and target.
Authorize read access to Squarespace and connect a prepared staging WordPress destination.
Review detected records, available entities, media, URLs, and anything that needs a decision.
Choose where supported Squarespace data belongs in the prepared WordPress model.
Move a small set of real records to staging and inspect the result before purchasing the full migration.
Review counts, records, media, links, warnings, and exceptions, then purchase and start the full migration when ready.
Technical detail
Open only the detail you need for planning, mapping, or validation.
This page is synchronized with the stable Squarespace source capability and WordPress destination snapshot. Squarespace is source-only; WordPress supports both directions.
The current catalog exposes Attachment, Author, Comment, Content, Page, Profile, Tag. Public URL extraction, export data, and restricted profile access are reviewed separately before scope is approved.
Authenticated REST and versioned Bridge adapters support authors, categories, tags, posts and pages, comments, media, menus, menu items, slugs, metadata, and approved destination types.
Standard means the current source and destination adapters expose a direct structured path. Review means source availability or the destination model must be confirmed. Custom means the feature is not portable as a standard content entity.
| Squarespace source | WordPress target | Status and boundary |
|---|---|---|
| Blog posts | Posts or a prepared custom post type | Standard: title, body, slug, dates, status, and source identity are mapped. |
| Supported layout pages | WordPress pages | Standard with review: portable page content is separated from Squarespace section and template behavior. |
| Categories and tags | Categories, tags, or another taxonomy | Standard: terms load before content and relationships resolve through the ID map. |
| Authors | WordPress authors | Review: names and available email identities can map; passwords and account behavior do not transfer. |
| Images and files | WordPress Media Library | Standard with validation: files must remain downloadable, pass destination limits, and be rewritten to WordPress URLs. |
| Comments | WordPress comments | Review: availability depends on the accepted source path and each comment must resolve to its destination post. |
| Profiles | CRM, users, customers, or approved custom records | Custom/restricted: personal data requires purpose, minimization, access, mapping, and retention decisions. |
| Slugs and source paths | Permalinks and redirects | Delivery artifact: every valuable old URL is mapped to a relevant destination or an approved removal outcome. |
| Multiple blogs, galleries, and special blocks | Posts, galleries, blocks, or custom fields | Review/custom: the official export does not represent every Squarespace page and block type. |
| Commerce, scheduling, forms, and memberships | WooCommerce, plugins, CRM, or custom applications | Custom: functionality and operational records require separate implementation. |
| Templates, styles, and section layout | Theme, blocks, patterns, and templates | Rebuild: presentation does not transfer as portable content data. |
The mapping workbook records destination types, fields, URL rules, dependencies, fallbacks, and accepted exceptions before the first staging run.
| Squarespace value | Migration rule | WordPress result |
|---|---|---|
| Source item ID and URL | Preserve source identity and add the URL to the approved redirect map | Stable rerun lookup plus destination permalink |
| Title, body, date, status | Normalize portable content and translate editorial state | Post or page title, content, date, and status |
| Category or tag | Create terms first and resolve source references | WordPress taxonomy relationships |
| Image or file URL | Download, validate, upload, and record the asset ID | Media Library item and rewritten reference |
| Author identity | Match an approved account or create a controlled author record | WordPress author assignment without password migration |
| Custom block or profile field | Route to a reviewed field, manual task, custom entity, or exclusion | Documented result rather than silent flattening |
Squarespace documents that its WordPress-format export covers selected content, not every page type, block, style, or operational feature.
Combine the export with a crawl, page inventory, media list, and business-owner review so omitted content does not disappear silently.
Map text, images, metadata, and relationships independently from section layouts, templates, CSS, scripts, and responsive behavior.
Do not assume referenced images have moved. Download, upload, checksum or inspect, rewrite URLs, and record failures before the source closes.
Profiles, customers, subscribers, and donors require explicit legal purpose, secure access, destination ownership, and deletion rules.
Squarespace paths, WordPress permalinks, page hierarchy, and generated metadata differ. The final URL contract must be approved before production.
Combine crawl data, sitemaps, analytics landing pages, linked assets, and manually maintained campaign URLs.
Map each valuable old URL to the closest final page, then test status, target relevance, chains, loops, and parameter behavior.
Review titles, descriptions, canonicals, social fields, headings, body links, image attributes, and destination SEO storage.
Track errors, redirects, sitemap processing, canonical selection, landing-page traffic, forms, and conversions during stabilization.
Acceptance requires evidence that supported records, files, URLs, and priority pages work on WordPress before access to the source is removed.
Compare source, extracted, loaded, skipped, rejected, failed, and unresolved totals by entity and destination type.
Check simple, complex, old, recent, media-heavy, comment-heavy, and special-block examples in staging and production.
Open featured and inline images, documents, galleries, internal links, mobile layouts, and destination templates.
Assign every unresolved omission or transformation an impact, owner, decision, remediation path, and target date.
Before purchase
The free sample migration creates a limited set of records in staging. Check fields, relationships, media, URLs, rendering, and reported exceptions before paying for the full run.
Pricing
Package fit depends on supported record volume and complexity. Analyze the source first, then review the fixed package or dynamic estimate shown for the migration.
Compare migration packagesPlan the move
Compare platform ownership, editing, design, extensibility, SEO, cost, maintenance, and migration tradeoffs.
Open guide →Separate supported content transfer, SEO work, destination rebuilding, and ongoing platform cost.
Open guide →Review export limits, site inventory, destination preparation, mapping, imports, and dry run controls.
Open guide →Plan URL inventory, redirects, metadata, staging checks, launch, and monitoring.
Open guide →Clear answers
No. Squarespace exports selected content types, while special pages, blocks, commerce, styles, and platform functionality need separate extraction, transformation, or reconstruction.
Supported downloadable files can move, but every asset must be fetched, accepted by WordPress, uploaded, linked to the correct record, and validated before the source site closes.
Comments are reviewed against the available source path and destination relationships. They are accepted only when they can be reconciled to the correct WordPress post with authorship and dates.
They require custom scope because the destination purpose, lawful handling, personal-data fields, consent, retention, and account behavior must be approved first.
No. Templates, section layouts, styles, scripts, animations, forms, and responsive behavior require WordPress-native design and implementation.
No provider can guarantee rankings or traffic. Reduce avoidable risk through URL mapping, redirects, metadata review, internal-link updates, sitemap checks, analytics, and monitoring.
Only after production validation confirms required records and files, redirects are working, priority journeys pass, backups exist, and the accountable owner accepts remaining exceptions.
Next step
Create an account, select Squarespace and WordPress, and use the app to analyze supported scope before committing to the full migration.
