# Squarespace to Shopify: Products, Pages and Blog > Plan a Squarespace-to-Shopify migration without losing valuable content: products, variants, images, blog posts, pages, customer data and important URLs. - Author: [Francesco Guiducci](https://ifgdigital.com/en/francesco-guiducci/) - Published: 2026-11-14 · Updated: 2026-11-14 - Topic: [Migrations and platform choice](https://ifgdigital.com/en/ifgwebdesign/ecommerce/blog/topic/migrazioni/) - Language: English · Italian version: https://ifgdigital.com/ifgwebdesign/ecommerce/blog/migrare-squarespace-shopify/ - Reading time: 5 min - URL: https://ifgdigital.com/en/ifgwebdesign/ecommerce/blog/squarespace-to-shopify-migration-products-pages-blog/ **Direct answer:** moving a Squarespace store to Shopify means migrating two connected assets: commercial data and editorial content. A store with a modest product catalogue can still depend on traffic from useful pages, photography and blog posts. Moving products alone will not preserve those routes, their context or the journeys they support. ## Audit what brings visitors and sales today Start with an inventory of products, options, collections, pages, blog posts, image galleries, customer records, past orders and URLs with search traffic or external links. Do not discard an informative page simply because it does not describe a product. Shopify's [official Squarespace migration guide](https://help.shopify.com/en/manual/migrating-to-shopify/migrating-from-squarespace) treats products, customer information, historical orders, reviews and editorial content separately. It also explains that Squarespace cannot export everything. Choose the transfer method for each type of content rather than assuming a single export covers the entire website. Review important page titles, current canonical URLs and the navigation paths that connect articles to products. Record the source URL and an intended destination before rebuilding anything. ## Product CSV files need mapping, not just uploading A product with several options, multiple photographs and stock rules needs a real import test. Make a field-by-field mapping for title, description, SKU, price, options, inventory, primary image, additional images and custom product attributes. Squarespace's product CSV is not identical to Shopify's product CSV. The official guide describes how to adapt headings and option values, and warns that featured images, variant images and alt text are not fully represented in the source export. For this reason, a successful file upload is not proof of a complete product migration. Import a small pilot containing both simple and variant products. Compare them against the source store before moving the rest of the catalogue. Use Shopify product options and metafields where appropriate, instead of placing every attribute into long descriptions. ## Blog posts and pages follow a separate path Many Squarespace sites combine a shop, portfolio, service pages and a publishing archive. Those content types cannot be treated as extra product rows. Their relationships, images, internal links and URLs need separate handling. According to Shopify's migration documentation, Squarespace can export some blog content and pages as a WordPress XML file, with restrictions including the number of blog pages covered. That XML file cannot be imported directly into Shopify. Plan to recreate or transfer legitimate content through a supported workflow and check the rendered result. For every important article, record its title, body, embedded media, author where applicable, internal links and destination URL. A useful article leading readers to a product should still lead to the relevant product after the migration. ## Preserve images, variants and editorial context Do not judge migration quality from product counts alone. Inspect images displayed within articles, galleries that support purchase decisions, responsive image cropping and accessible image descriptions. Some media needs to be recovered or uploaded separately. Similarly, a variant imported with the right SKU but the wrong option name or price is not a passing result. Define representative acceptance cases before bulk migration, including an out-of-stock product and a product with more than one option. A page that looks similar at desktop width also needs a mobile check. Test navigation, reading order, forms, product galleries and links to the cart, rather than relying on a screenshot comparison. ## Map old URLs to meaningful new destinations Export or crawl the existing URL structure before changing the domain. Associate each valuable product, collection, article and service page with its most relevant new location. Use permanent redirects where URLs change, and avoid sending unrelated old pages to the homepage simply to suppress 404 errors. Google's [site-move guidance](https://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes) recommends mapping URLs and monitoring the move. Correct redirects reduce avoidable disruption but cannot guarantee unchanged search traffic. Keep a list of URLs intentionally retired, too. A missing destination should be an explicit decision, not a surprise discovered after launch. ## Keep the brand without recreating the old builder A migration is not an obligation to duplicate every Squarespace interaction through extra Shopify apps. Preserve the visual identity and user journey, then choose maintainable Online Store 2.0 sections and native functions wherever they meet the requirement. Review the menu structure, collection hierarchy, product templates, contact forms and checkout path. Rebuilding an animation is less valuable than ensuring customers can discover products and complete an order reliably. ## Customers, reviews and historical orders The supported customer export needs cleaning and mapping before import. Contact data and first-login behaviour are separate concerns; a customer record does not automatically reproduce an old account experience. Reviews and order history also require their own plan. Shopify notes that Squarespace does not provide a standard export of customer reviews, so do not invent testimonials or assume review history can be moved with a product CSV. If an alternative legitimate source of records exists, verify its provenance and the chosen destination. Preserve the actual evidence of email-marketing consent. Transferring a customer's email address is not, on its own, permission to subscribe that person to a new campaign. ## Test the new shop before changing the domain The acceptance plan should cover a product with variants, an unavailable item, cart, discount, shipping rates, taxes, payment, notifications and customer access. Add a formerly indexed article, a contact form and a redirected URL to the test set. If the Squarespace store remains operational during preparation, plan how to reconcile new orders and inventory changes made after the initial export. Decide who checks the final delta and who can stop a cutover when a critical scenario fails. ### A content sample worth testing Choose one product with variants, one search-visible information page, one article with embedded images and one contact form. For each example, check both the destination content and the action a visitor should be able to complete: purchase, read, navigate or submit. This sample exposes failures that a product import report alone cannot detect. It also makes it possible to distinguish items that should be imported, rebuilt or intentionally archived. ## The migration is finished only after verification A Shopify homepage going live is a milestone, not the acceptance criterion. Verify redirects, accessible editorial content, products, checkout, order flow and monitoring after the switch. When Squarespace was also the brand's publishing platform, the editorial archive deserves the same care as the catalogue. Francesco Guiducci handles [Shopify migration projects](https://ifgdigital.com/en/ifgwebdesign/ecommerce/shopify-migration/) directly, starting with an inventory of the existing website and a test plan for the new store.