Comes across
- Pages and blog posts, through the WordPress XML export
- Images embedded in that content
- Basic SEO titles and descriptions
- Comments, where you had them
Migrations
Moving from Squarespace to WordPress
Squarespace does export a WordPress-format file, which helps, but it quietly leaves out several content types. The gap between what the export contains and what your site shows is the whole job.
Before anyone quotes
What survives the move, and what does not
Most migration disputes come from this list being assumed rather than agreed. So we agree it first.
Gets rebuilt
- Layout, since Squarespace blocks have no WordPress equivalent
- Product pages: Commerce data is not in the export
- Album, gallery and index pages
- Forms, scheduling and member areas
The expensive surprises
Three things specific to Squarespace
The export is narrower than it looks
It carries one blog, pages and text. Products, galleries, album pages and index pages are simply absent. Auditing what is missing before quoting is the difference between a fixed price and an argument.
Dated blog URLs
Squarespace blog paths often carry the publish date. Match the permalink structure or write the redirects, but decide deliberately rather than discovering it after launch.
Images point back at Squarespace
Content comes across referencing their CDN. Left alone, your images disappear the day the subscription lapses. Every asset gets pulled local and relinked.
How it runs
Five steps, same every time
-
1
Crawl what is live
Every URL currently indexed, exported to a sheet. This becomes the redirect map and the definition of done.
-
2
Audit the export
What the platform gives us, compared against what the crawl found. The difference is the rebuild, and it gets priced before we start.
-
3
Build on staging
The new site goes up somewhere private, with real content imported, so you review the actual thing rather than a mockup.
-
4
Map every redirect
Old URL to new URL, one row at a time, tested as 301s on staging before anything points at production.
-
5
Cut over and watch
DNS moves, then we monitor crawl errors and traffic for the fortnight that follows, because that is when problems surface.
Before you commit
Leaving Squarespace, answered
Something not covered here? Ask us directly and an engineer will answer.
Ask a questionFrom Squarespace we can bring over: pages and blog posts, through the wordpress xml export; images embedded in that content; basic seo titles and descriptions; comments, where you had them. Everything else on the site has to be rebuilt, and we agree which is which before quoting.
The parts with no equivalent on the other side: layout, since squarespace blocks have no wordpress equivalent; product pages: commerce data is not in the export; album, gallery and index pages; forms, scheduling and member areas. This is where the cost sits, so it is priced up front rather than discovered halfway through.
Not if the redirects are done properly. We crawl every URL that is currently indexed, map each one to its new address, and test those as 301s on staging before anything points at production. Then we watch crawl errors and traffic for the fortnight after cutover.
It carries one blog, pages and text. Products, galleries, album pages and index pages are simply absent. Auditing what is missing before quoting is the difference between a fixed price and an argument.
Squarespace blog paths often carry the publish date. Match the permalink structure or write the redirects, but decide deliberately rather than discovering it after launch.
Start here
Send us the Squarespace site
We will crawl it, work out what the export actually gives us, and come back with a fixed price and the redirect map included.
-
A free audit first
We'll look at your site and tell you straight what needs doing.
-
Fixed scope, fixed price
Agreed in writing before any work starts. No hidden fees.
-
A real engineer on the call
You talk to the people who do the work, not a sales script.