Skip to main content
Theme

Connectors

Squarespace

The tool reads a Squarespace site through an API key made in the site's own settings, and copies it to an Insites v6 instance. It only reads. Nothing is ever written back to Squarespace. It copies the site's pages and design, its forms, redirects and past form submissions, and its shop, which sells on the new site through the site's own Stripe account. Migrate a Squarespace site walks through a whole migration.

What you need

  1. In Squarespace, open the site you are migrating. You need to be its owner or an administrator.
  2. Open Settings, then Developer tools (Advanced on some sites), then Developer API Keys.
  3. Click Generate key and name it Insites Migration Tool.
  4. Give it Read access to Products, Inventory, Orders, Transactions and Profiles. Leave everything else off.
  5. Copy the key. Squarespace shows it once. In the tool, give the address visitors use (for example https://www.example.com) and the key.

A key reads only its own site. If the key belongs to a different site, the tool says which one and stops before reading anything. The key is kept encrypted for as long as the migration needs it, and removed when you close the migration: how long a key is kept. Delete it in Squarespace afterwards.

What is copied

On SquarespaceOn Insites
ProductsProducts in the Insites Ecommerce module: name, description, price, sale price, stock, size and weight, images, tags and search settings, each in its shop's category. Hidden products are copied too, still hidden.
Variants and optionsA product with options keeps each variant (its SKU, price, stock and image) and each option, in the module's own tables. A product without options takes its price and stock from its one variant, as the module's own admin does.
Shop pagesEach becomes a category of the Ecommerce module.
Product imagesCopied to the new site, each kept under its own id, and checked by size.
ProfilesEvery profile becomes a CRM contact: customers, people with an account, and people who only gave an email. See passwords, below.
OrdersOrders in the Ecommerce module, with each line, the totals, the addresses and the status, each linked to its contact.
TransactionsEach payment behind an order becomes a payment of that order.
The cart and checkoutBuilt on the new site, so it keeps selling. See The shop below.
PagesEvery page the site's sitemap lists, and the home page, read from the live site and copied to the same address, with its title and sharing tags.
Sitemap and robots.txtThe sitemap is the one Insites serves at /sitemap.xml, listing every page that was copied except the not-found page. The site's robots.txt is copied with its own rules, such as the AI crawlers it blocks, and points to /sitemap.xml.
DesignEvery file the pages load from Squarespace (styles, scripts, fonts and images) is copied, and the pages name the copies. Squarespace's own scripts are copied too, because they draw part of what a visitor sees, and every file they fetch as they run is found by loading each page in a browser, at a desktop width and a phone width, and copied as well. Each image is copied once, at 1,500 pixels wide, and serves every size the page asks for. The copied scripts no longer send visitors' page events to Squarespace's own analytics service; the site's own analytics, such as Google Analytics, keep working.
Forms and newsletter blocksEach is rebuilt in the Insites form builder, where it was on the page and with Squarespace's own look, fields, required fields, button text and the message shown after sending. What people send goes into a table named after the form, one column a field. A form that asked for a captcha asks for one on Insites. See Forms below.
RedirectsFrom the site's URL Mappings, which you paste in, or, without them, found by asking the live site. See Redirects below.
Past form submissionsFrom Squarespace's export of each form, which you add. See Past form submissions below.

Every row is made with an id from its Squarespace id, so a final sync updates it rather than adding it again. The shop's rows are written the way the Ecommerce module's own admin writes them, prices included.

The shop

The Insites Ecommerce module keeps a shop's products, carts and orders. It has no storefront of its own, so the tool builds one on the new site from what the Squarespace site has:

  • Product pages keep Squarespace's design. Add to Cart adds the product to a cart on the new site.
  • The cart is at /cart, inside the site's own header and footer, with quantities to change.
  • Checkout uses Stripe Checkout, through the site's own Stripe account. The new site prices every line itself and checks the stock. An order is marked paid only when Stripe confirms it was paid for the order's own total. The stock goes down by what was bought.

Before the shop can take payments, the site's owner adds their Stripe keys in the instance admin, under Integrations, Stripe. In Stripe, add a webhook for the checkout.session.completed event that sends to /shop/stripe/webhook on the new site. It marks an order paid when the buyer pays and never returns to the site.

Shipping is free, and discount codes are not taken, until they are set up on the new site. Squarespace has no API for its shipping rules or discount codes.

Forms

Squarespace draws a form with its own script and sends it to Squarespace, so neither works once the site has moved. Each form and newsletter block is built the way the Insites form builder builds one, so you edit it in Forms in the new instance's admin like a form made there:

  1. Its database table comes first, named after the form. The past submissions you add go into it too, so they show as the form's own.
  2. Then the form, on that table, with Squarespace's fields and the ones it required.
  3. Then its two emails: a workflow email to the site's owner for each submission, and an autoresponder to the person who sent it.

The page keeps the form as Squarespace drew it, with Squarespace's own classes, so the site's styles still apply. It sends to the form on Insites, which checks the captcha when the form had one, saves the row, and sends the visitor back to Squarespace's message. A form set to send visitors to another page still does.

Squarespace does not say who its form emails go to, so the Forms step of Transform asks who each form's workflow email goes to. You can give more than one address, separated by commas. A form you give no address to saves every submission and emails nobody, and the plan says so. The autoresponder is made switched off, so nothing is sent until you have read it and turned it on in the form builder. Replies to it go to the first address you give, or to the address the old site links to until you give one. Each enquiry also adds a CRM contact for the email address it was sent with, unless you untick Adds a CRM contact for the form. Each enquiry adds a CRM contact. A file upload field is named on the plan and left off the rebuilt form.

Redirects

Finding none from the outside does not mean the site has none. The Redirects step says so in amber when nothing was found, and the To do list carries a job to confirm it, until you paste the URL Mappings or tick This site has no redirects and say why. The reason goes in the report. It never stops the load.

Squarespace has no API for a site's redirects, so the tool finds what it can from the outside when it reads the site: every old address the Internet Archive has seen on the site, and every link on its pages, is asked of the live site, and each one the site sends somewhere else becomes a redirect. The Redirects step shows how many were found. A redirect nobody linked to and no archive saw cannot be found this way.

The URL Mappings are the site's whole list, so they are better. Copy them from the site's URL Mappings (in Squarespace, open Settings, then Developer tools, then URL mappings) and paste them into the Redirects step of Transform. Each line, such as /old-page -> /new-page 301, becomes a page at the old address that redirects to the new one with the same code. A line that is not a redirect, such as one using Squarespace's [variables], is named and left out. An old address with a query string, such as /news?page=2, becomes a page at its path, /news, because a page answers its address whatever the query string; of several lines for one address, the one without a query string is kept and the plan counts the others. Up to 5,000 redirects can be given. Once you give the URL Mappings, they replace every redirect the tool found: nothing found on the live site is used.

Past form submissions

Squarespace has no API for what people sent through its forms. Squarespace keeps a form's submissions for as long as the form has a required email field, and for 30 days otherwise. Export them as a CSV, one file a form: edit the page the form is on, click the form block, then the pencil, and on the Content tab click Export Submissions. On the Form submissions step of Transform, add each file beside its form's table. The file is sent to the tool, where the Squarespace connector reads it: each column is matched to a field of the form by its name, and a column that matches no field is named, never dropped silently. A date the export writes without a time zone is read in the site's own time zone, as Squarespace reports it. The same file added twice, or again for a final sync, adds nothing new. Up to 20,000 submissions can be given across every form; a long file is sent to the tool in pieces and kept encrypted beside the copy of the site.

What is not copied yet

  • Form email wording. Squarespace sent its form emails from its own code. Each rebuilt form has the form builder's own workflow email and autoresponder instead: change their wording in the form builder if you want Squarespace's.
  • Shipping rules and discount codes. Squarespace has no API for them. Checkout charges no shipping and takes no discount code until they are set up on the new site.
  • Gift cards. Insites keeps no gift card balance yet, so the gift card is not sold on the new site, and its page says gift cards are coming soon. Gift cards are coming to Insites. Until then, you honor the cards already sold on Squarespace yourself.
  • Order emails. Squarespace emailed buyers when they ordered and when their order was fulfilled or refunded, and emailed the shop about each new order. Stripe can send buyers a receipt; the checklist says how.
  • The newsletter pop-up. Squarespace's server draws it when a page asks, so it does not appear on the new site.
  • Password-protected pages. Only their password prompt is public, so each is named on the plan, for you to rebuild.
  • Customer accounts. Squarespace never gives out passwords, and the new site has no customer sign-in: everyone checks out as a guest, and each customer's past orders are kept with their contact in the CRM.
  • Download and service products. They sell on the new site, but nothing sends the download or books the service after payment.
  • Scheduling, Email Campaigns, Member Areas and Google Workspace. They are separate Squarespace products. The checklist says what happens to each when the site's plan ends.

After the migration

The To do list in Launch is written for a Squarespace site. It replaces the jobs written for an Insites instance, and adds the ones only a Squarespace site has. Each one names what this site has: its domains, the shipping its orders paid, the discount codes they used, its forms by name.

  • Domains and DNS. Add the site's domains to the new instance in Insites Console. For a domain bought through Squarespace, replace the records under Squarespace Defaults in its DNS settings with the ones Console gives, and leave the email records as they are.
  • Stripe. Add the site's Stripe keys in the instance admin, under Integrations, Stripe, and switch live mode on. In Stripe, open Workbench, then Webhooks, and send the checkout.session.completed event to /shop/stripe/webhook on the site. Then buy something cheap and refund it.
  • Shipping and discount codes. Checkout charges no shipping and takes no code. The checklist lists what Squarespace's orders paid for shipping and the codes they used, so you can decide what the new site does.
  • Order emails. In Stripe, switch on receipts for successful payments and refunds, and an email to yourself for each payment.
  • Gift cards. Download the gift cards and the value left on each from Squarespace before its plan ends, and honor them yourself until gift cards come to Insites.
  • Forms. Open each form in the form builder: check who its workflow email goes to, read its autoresponder and switch it on, and send a test from the copied page. Move newsletter sign-ups to the mailing list.
  • Customers. Tell the shop's customers the site has moved and that they check out as guests.
  • Search engines. Submit /sitemap.xml in Google Search Console once DNS has moved.
  • The Squarespace site. Keep it, and its plan, until the new site has run cleanly through the 14-day watch. Export the orders, gift cards and contacts, close the migration on the Close step, delete the API key in Squarespace, and cancel the plan. Scheduling, Email Campaigns and Google Workspace bought through Squarespace keep billing until you end or move them.

If it does not connect

The tool saysWhat to do
Squarespace did not accept this API keyMake a new key in Developer API Keys and paste it again.
That API key belongs to another Squarespace siteMake the key in the settings of the site you are migrating.
The key cannot read everything the migration needsMake a new key with Read access to Products, Inventory, Orders, Transactions and Profiles.