The catalogue is generally small and the content is generally good. The risk is losing the editorial pages and the routes that earn the traffic.
Which inverts the usual migration priorities.
Squarespace stores are typically content-led: a brand with a considered site, a modest catalogue, and editorial pages that carry both the positioning and a meaningful share of the search traffic.
That changes what the project has to protect. On most migrations the catalogue is the risk. Here the catalogue is usually the straightforward part, and the risk is losing the pages, the posts and the routes that a business has built up over several years of publishing.
Squarespace commerce data extraction is more limited than an open platform, and what can be retrieved varies by plan and by how long the store has been trading. Product data is generally workable. Order and customer history is the area where the answer has to be confirmed for your account rather than assumed.
The move is usually made because the commerce functionality has become the constraint: variants, discounts, stock control, multi-channel selling or shipping rules. That is worth stating in the scope, because it tells you which parts of the destination store deserve the budget.
Confirmed against your account, because the export limits vary.
| Entity | Normally transfers | Where a decision is needed |
|---|---|---|
| Products | Yes, in a workable form | Variant structures that were compressed to fit the platform’s limits |
| Product images | Yes, once retrieved | Whether image sizing and cropping still suit a commerce template |
| Blog posts | Usually, including publication dates | Which posts move to the Shopify blog and which become pages |
| Pages | Content usually, layout no | Which editorial pages justify a bespoke template on the destination |
| Customers | Partially, depending on plan | How reactivation is communicated to a partial list |
| Orders | Limited, confirmed before it is promised | Import a window, archive separately, or accept the gap |
| Discounts | Rules that map to Shopify discounts | Conditions with no equivalent, which need a different mechanism |
| URLs | Mapped from a crawl and the site structure | Product and blog route families, each handled as a rule |
Squarespace product and blog routes follow predictable patterns, which makes rule-based mapping practical. It still needs verifying against a crawl, because sites accumulate exceptions.
The editorial quality is usually worth carrying forward. The layout is not portable.
Squarespace layouts do not export. The remedy is to identify the small number of genuine editorial patterns on the site and rebuild them as reusable Shopify sections, rather than recreating every page individually.
Catalogues on Squarespace are often compressed to fit the platform’s option limits, with size and colour combined into one field or separate products created to work around a constraint. The move is the moment to correct that.
Shipping rules, discount logic, stock control and multi-channel selling are usually why the business is leaving. Those need designing on the destination rather than reproducing, since the current versions are workarounds.
Squarespace bundles forms, campaigns and member areas. Each needs a Shopify-side equivalent chosen and costed, and each needs its data exported before the source subscription lapses.
Keep the writing and the photography. Rebuild everything that holds them.
On a content-led site this is the highest-value part of the project.
Squarespace routes are predictable enough for rule-based mapping, which makes thorough coverage realistic rather than aspirational.
Where an editorial page is the reason a business ranks for something, it gets a destination that is at least as good, not a redirect to the homepage.
The design bar is usually higher here than the data complexity.
Swipe the parts
Design
Squarespace sets a reasonable visual standard, and a Shopify build that looks worse than the site it replaced is a failure regardless of its commerce capability. The design budget is worth protecting.
Systems
Email campaigns, forms, scheduling and member areas each need a replacement chosen and costed, with data exported before the source subscription ends.
Proof
Small catalogues can be validated exhaustively. Content is validated against the crawl, which matters more here than the product count.
Switch
A short delta run, a planned switch and the Squarespace site retained until the destination has traded and the redirects are verified.
Content volume and design standard, more than catalogue size.
A Squarespace migration is priced from the site, not from the shop.
Standard Squarespace moves estimate well. Stores with large publishing archives or bespoke commerce workarounds route to manual scoping.
Published starting figures in GBP and USD, excluding VAT.
From-price or scoped after a source review
Data only
From £1,000From $1,300
Products, customers, orders and content mapped into a Shopify store that already exists or is priced separately. Fixed once source access and a sample migration are reviewed.
Starting price · scoped after discovery
Migration and build
From £5,000From $6,500
Moving to Shopify and building the store in one project, so the data and the storefront land together rather than in two disconnected pieces of work.
Starting price
Where the editorial site is substantial, the content rebuild is the larger half of the project and is priced as build work rather than as data migration.
That is the main thing the project is designed to protect. Posts are carried across, routes are mapped under a consistent rule and verified after launch, and pages that earn traffic get a destination at least as good rather than a redirect to the homepage.
Yes, but not by accident. Squarespace sets a decent default standard, so the design has to be a deliberate part of the scope. A migration that trades visual quality for commerce features is a poor exchange for a brand that sells on presentation.
Usually because commerce has become the constraint: variants, stock control, shipping rules, discounts or selling across channels. If none of those are limiting the business, moving is not automatically the right call, and we will say so.
They need exporting before the subscription lapses and a chosen replacement on the Shopify side. It is a small task that becomes a large problem if it is left until after the switch.
On a content-led store, the list of routes that must survive shapes the project more than the catalogue does.
