When Squarespace stops being enough for the selling part

Four limits come up repeatedly. Product options and variants that need rules, where the platform offers a fixed list. Customer-specific or tiered pricing for wholesale. Catalog and inventory operations at a scale where bulk editing and imports matter more than a pretty admin. And integrations (accounting, ERP, warehouse, marketplace sync) where the answer has to be an API and a manual export will not do. If none of those describe you, the honest recommendation is to stay and spend the money on demand generation instead.

• Variant and option rules the platform cannot express
• Wholesale or tiered pricing per customer
• Bulk catalog and inventory operations at scale
• Integrations that need an API, not a CSV export

Squarespace stores are often content-led: editorial pages, journals, lookbooks and long-form product storytelling that earned real search traffic over years. That content is usually the most valuable thing being moved, and it is the part most often treated as an afterthought while everyone focuses on products. Inventory the content first, keep the URL structure wherever you reasonably can, and migrate the pages that have links and traffic before the ones that have neither. Anything you decide to drop needs a redirect to the closest relevant page, not a 404.

The export comes in two pieces: pages and posts as a WordPress-format XML file, products as a separate CSV. Categories, images, prices and stock come across with normal care. Options and variants need mapping by hand. Customers transfer without their passwords, so the launch plan needs a reset flow. Blog and page content exports, though the block structure will not survive intact and the layouts are rebuilt. Design does not move at all. Any commerce feature you configured inside Squarespace (discount rules, member areas, subscriptions) needs a WooCommerce equivalent chosen and configured. That inventory belongs in the quote. Left out of it, it turns up mid-build as a surprise.

Product and category URLs will change shape: Squarespace 7.1 puts products under the store page with a /p/ segment, where WooCommerce uses /product/. So will some content URLs, depending on how the new structure is designed. Every one of them needs an explicit 301 mapped before launch and verified on staging. Two habits prevent most of the damage: export the complete live URL list before anything changes, and pull your top pages by clicks from Search Console so the highest-value URLs are checked first and not last. After go-live, watch coverage and 404s daily for two weeks — what to do if rankings drop is the recovery path if something was missed.

Ownership of your data, your checkout and your code; no platform commission on top of payment processing, where Squarespace takes 3% on its Business plan and nothing on Commerce; and the ability to express any selling rule you can describe, because nothing is gated behind what the vendor decided to support. For a store with genuine complexity, that is the whole point. For a simple store, it is a set of powers you will not use, bought at the price of maintenance you now own. That is the trade the platform choice page walks through question by question.

Hosting, updates, security patching, backups and uptime stop being included in a monthly fee and become someone's job. That is not an argument against moving; it is an argument for deciding, before launch, who that someone is. Stores that migrate without answering this question do not notice for six months and then discover the cost in a single expensive incident. A maintenance plan or an in-house owner should be part of the plan from day one, not a reaction later.

Build on staging while the current store keeps selling. Migrate content first and verify it renders correctly, then products, then customers. Test checkout with real cards and real refunds. Choose a quiet window, freeze catalog edits, do the final sync, switch DNS, and keep the old subscription active for a month. If the domain was bought through Squarespace, its DNS records live in Squarespace's domain panel, so decide before cutover whether it stays there or transfers out. The launch is done when a real order has gone through end to end: confirmation email sent, payment captured, the sale visible in your reports. A site that merely loads proves very little.