WordPress hosting for sites moving off Squarespace.
Squarespace exports to WordPress format, which sounds like the whole job is done. What it leaves out is the part worth planning for.
What the Squarespace export actually carries.
It produces WordPress XML, which imports cleanly - and quietly omits several kinds of page without saying so.
Pages and posts, but not everything
The export covers standard pages and blog posts. Product pages, album pages and index pages are not included, and nothing in the process tells you they are missing.
Date-based blog URLs redirected
Their default blog URLs embed the full publication date, which almost never matches the permalink structure you want to keep. Every one gets a rule.
Blocks rebuilt, not pasted
Squarespace blocks come out as inline markup carrying their own class names and none of their styling, so they are rebuilt as real blocks here.
Commerce handled separately
Products are not in the content export at all, so a store needs its own migration path rather than being assumed to follow along.
Media pulled from their CDN
Image URLs point at their CDN and keep resolving there until each one is rewritten to your own domain.
Import, then find what did not come.
The failure mode here is a migration that looks complete because the import succeeded. We reconcile the new site against the old one page by page.
- Export contents reconciled against the live site
- Redirect map for dated URLs prepared
- Cutover at a time you choose
- Squarespace site left live until you confirm
Caching you control.
Squarespace decides how your pages are served. Here that is a set of settings, which is most of what changes.
What this move needs that a host migration does not
The export does most of the mechanical work. The value is in catching what it left behind.
| Setting | What we do | Why |
|---|---|---|
| Export scope | Reconciled page by page against the live site | The export covers pages and blog posts but omits product, album and index pages, and it reports success either way. |
| Dated blog URLs | Each mapped to the new permalink with a redirect | Their default structure embeds the full publication date, which rarely matches the permalinks you want to live with afterwards. |
| Blocks | Rebuilt as blocks rather than imported as markup | Exported blocks arrive as inline HTML carrying Squarespace class names and none of the styling that made them work. |
| Commerce | Migrated on its own path, separate from the content export | Products are absent from the XML entirely, so a store treated as part of the content import simply arrives without its catalogue. |
| Media | Pulled from their CDN and rehosted under your domain | Attachment URLs point at squarespace-cdn.com and keep resolving there until every one is rewritten. |
Simple, transparent pricing.
Every plan includes free migration, daily backups, SSL and 24/7 support.
- 1 WordPress site
- 10 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Support tickets
- 5 WordPress sites
- 50 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Priority support tickets
- 20 WordPress sites
- 200 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Dedicated support
Questions, answered.
Squarespace exports to WordPress. Is that not the whole job?
What happens to my blog URLs?
My pages use a lot of Squarespace blocks. Do they survive?
I sell products on Squarespace. Can those move?
Will my images keep working?
Move off Squarespace with the pages the export forgot.
Free migration, gaps reconciled against the live site, and dated URLs redirected.