Migrate Shopify to Squarespace: records and checks
Migrate Shopify to Squarespace with a verified record map, separating product import from orders, accounts and store functions that need another route.
- Published
- Last updated
You can migrate Shopify to Squarespace by exporting your products and importing them into a Squarespace store, then rebuilding the storefront and checkout settings. Keep historical orders and app records on a separate preservation plan. A product import does not move the whole business.
This process fits retailers ready to rebuild their store around Squarespace’s buying flow. If a subscription service or fulfilment connection still depends on Shopify, keep that service running until its replacement works. Decide those dependencies before moving your domain.
Check what can move to Squarespace
Squarespace supports product imports and a separate contact-list import from Shopify. Its Shopify migration guide requires you to recreate the design and other website content.
For the product file, the supported cross-platform types are physical and service products. Squarespace’s limits are 10,000 products on version 7.1 or 200 on version 7.0, with up to 250 variants per product. This is a one-time transfer, so later Shopify changes need reconciliation.
Use this division to assign a destination for each record before importing anything.
| Record | Transfer route | Work outside the product import |
|---|---|---|
| Products and variants | Squarespace product importer | Map supported fields and inspect the imported options |
| Product images | Hosted image URLs in the product file | Check image order and assign variant images manually |
| Contacts | Separate contact or mailing-list import | Preserve consent and distinguish a contact from a shopping account |
| Historical orders | Retained source records and order exports | Give support staff a lookup route for old purchases |
| Passwords and account access | Separate destination account setup | Plan how returning customers access the new store |
| Subscriptions and app records | Provider-specific transition or retained service | Assign an owner for recurring charges and outstanding commitments |
| Theme and store settings | Destination rebuild | Recreate pages and the rules used at checkout |
A Squarespace page can also link to Shopify products. In that arrangement, Shopify still owns the linked purchase. Moving the domain registration alone also leaves the store’s commerce records where they were. Define completion as the destination taking new orders, with an explicit arrangement for earlier ones.
Preserve exports and map the records
Save untouched exports before transforming any fields. Shopify supports separate exports for products, customers and orders. Its backup guidance also covers other records and the downloadable theme.
- Give the migration owner permission to export the source and administer the destination. Record who controls the domain, payment account and business email.
- Export all products through Products, then Export in Shopify. Save the original file separately from the working spreadsheet.
- Export customers and orders separately. Keep transaction records with the order archive and retain the records needed for refunds or unfulfilled purchases.
- Save original media files and a list of public product and content URLs. Shopify’s product export instructions explain that image files and collection membership are outside the exported file.
- Inventory apps and their records. Include active subscriptions, loyalty balances, gift-card liabilities and review content wherever your store uses them.
Keep the exports read-only in a location available to the people doing the move. Record each export’s scope and time so the final comparison uses the right starting point. Restrict customer and order archives to staff who need them.
Map the product file
Use the destination version’s product CSV template. A comma-separated values (CSV) file is a structured table. Matching the file extension alone does not make Shopify’s columns suitable for Squarespace.
| Source information | Destination field or action |
|---|---|
| Source product and variant identifiers | Keep in a private cross-reference. Leave new Squarespace Product ID and Variant ID cells blank |
| Product handle and original URL | Map the handle to Product URL. Keep the full old URL for redirects |
| Title and description | Map to Title and Description |
| Variant SKU and options | Map to SKU and paired Option Names/Values fields, with a row per option combination |
| Current and comparison prices | Map the intended standard price, sale price and sale status. Enter numeric amounts in the destination currency |
| Saleable quantity | Map to Stock after reconciling the source inventory |
| Images | Put direct web-hosted image URLs in Hosted Image URL |
| Store page and categories | Match Product Page and Categories to the destination’s existing slugs |
Keep this cross-reference after import. Source identifiers remain useful for investigating an old purchase even when the new platform assigns different identifiers.
Treat contact imports separately. Shopify’s customer export guide identifies marketing consent fields. Preserve those values when preparing a mailing list. A contact entry is not evidence that a customer’s password or historical orders now exist in Squarespace.
Rebuild the destination store functions
Build the destination store privately while Shopify continues serving customers. Recreate its pages and navigation, then configure the buying rules before switching traffic.
Run a small import before preparing the whole catalogue. For example, use a fictional shirt with two size variants and one sold-out item. Give each variant a distinct SKU and record the expected quantity. Compare the imported records with that written expectation.
Check the product count separately from the variant count. A product with two variants must remain one product with two selectable variants. Inspect its images and descriptions as well as the numeric fields.
When correcting the sample, distinguish creation from an update. Squarespace’s bulk-edit route uses an export from the destination with its existing identifiers preserved. Repeating a new-product file with blank identifiers risks duplicate creation. Keep a list of the sample’s destination identifiers and decide which records to update before another import.
Work through the store functions your customers use.
- Rebuild the theme in Squarespace. Copy necessary product information and policies into the new pages, then inspect navigation on a phone.
- Connect the destination payment processor. Squarespace supports its own payment service in Australia, and its payment setup guide provides a test-mode checkout route. A working Shopify payment connection does not establish the destination connection.
- Configure tax collection for your registrations and selling regions. Squarespace’s outside-US selling guide covers supported payment regions and tax settings. Compare a representative checkout total with your approved business rules.
- Recreate delivery rules. Squarespace supports flat-rate and weight-based shipping, with regional restrictions through shipping zones. Its shipping setup guide requires a delivery, pickup or shipping option for physical products.
- Review order and fulfilment emails in Customer Notifications. Squarespace’s notification guide explains previews and test emails. Trial sites cannot send those test emails, so include this in launch preparation.
- Reconnect each required external service using its Squarespace-supported route. Confirm which system now owns stock updates and fulfilment. Stop the old connection writing to the new store once its replacement takes ownership.
Keep Shopify responsible for an existing recurring charge until an agreed transition changes that responsibility. Recreating a subscription product on Squarespace does not establish a transfer of the customer’s existing agreement or payment authority.
Verify the destination buying task
Accept the destination only when a customer can select the intended variant and complete the expected purchase. Check old-order support separately against the retained source records.
Use a written acceptance sheet with expected and observed results. Include these checks before moving traffic.
| Customer task | Expected result |
|---|---|
| Select the fictional shirt’s second size | The selected SKU, price and image match the mapped variant |
| Open the sold-out item | Availability matches the intended stock rule |
| Enter an eligible delivery address | The intended shipping option and charge appear |
| Enter an excluded delivery address | Checkout does not accept an unsupported delivery arrangement |
| Complete the test-mode purchase | The destination records the selected items and expected total |
| Ask about a purchase made before the move | Support locates its original order and payment record through the archive or retained service |
For each difference, record the affected SKU or order reference and the system responsible. Correct the mapping or configuration, then repeat the affected buying task before importing the remaining products.
Move traffic with a recovery route
Prepare an old-to-new URL sheet while the source remains available. Squarespace’s URL mappings support permanent 301 redirects from inactive paths to active destinations on connected domains. Use the exact destination product URL from the new store.
- Schedule a pause in source catalogue edits and new source orders. Export the final changes since the initial snapshot.
- Reconcile sales and stock movements during the build period. Update existing destination records through their destination identifiers, avoiding another full new-product import.
- Assign every open order and return to one system. Tell support where to find pre-move purchases and who handles their refunds.
- Record the existing domain and email configuration before connecting the domain to Squarespace. Preserve the settings needed to send visitors back to the source if checkout fails.
- Enable the destination and its redirects. Check an old product link reaches its matching product, then confirm the destination’s purchasing and notification flow.
- Keep the source subscription and required app access until order reconciliation and recovery arrangements are complete. Cancel only services whose responsibilities have ended.
If checkout fails after the switch, pause destination sales before directing customers back to the source. Account for orders already accepted on Squarespace so staff neither fulfil them twice nor lose their stock movements. Retain both sets of records while resolving the fault.
Keep the migration owner responsible for early order reconciliation and broken-link reports. Give support a usable old-order lookup before treating the move as complete.
Give your store its own shopping agent
Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.