Tutorial
Migrate a Squarespace site
This walks through a whole migration of a Squarespace site to a new Insites v6 instance: every page with its design, its forms, its redirects and past form submissions, and its shop, which keeps selling on the new site through the site's own Stripe account. A shop of around 25 pages and 16 products takes about half an hour. You can close the page at any point: the migration carries on, and you come back to it from Migrations in the menu on the left.
- A new, empty Insites v6 instance, the Developer role on it, and an access token from its CLI tab in Insites Console. How to create one.
- A Squarespace API key for the site, with Read access to Products, Inventory, Orders, Transactions and Profiles. Only the site's owner or an administrator can make one. How to make one.
- The site's URL Mappings, copied from Settings, then Developer tools, then URL mappings. Squarespace has no API for them. Without them, the tool finds what redirects it can by asking the live site.
- Each form's past submissions, exported as a CSV, one file per form. In Squarespace, edit the page the form is on, click the form block, then the pencil, and on the Content tab click Export Submissions. More on the export.
- If the site has a shop: access to the Stripe account it will be paid into. You add its keys after the migration.
How the wizard works
A migration has seven stages: Source, Destination, Transform, Plan, Load, Verify and Launch. Each stage is split into a few short steps, listed down the side of the page. The footer at the bottom always holds Back, where you are, and the one thing to do next. When the next thing cannot be done yet, the footer says why. Nothing is written to the new instance until you approve the plan and type its code.
1. Source: connect the Squarespace site
- Sign in and click New migration.
- On Where are you coming from?, choose Squarespace site. A platform that is not listed? The last tile, Request a platform, tells us which one you use.
- The next screen asks only for The site's address: the address visitors use, for example
https://www.example.com. Press Next. - The key screen lists what to have ready for Squarespace and shows how to make an API key, step by step. Paste the key into API key and press Connect and check.
A key reads only its own site, so a key for another site is refused before anything is read. The tool checks what the key can read and lists it: Can read is what you want, and Not given says which part of the shop the key cannot read. Make a new key with Read access to it, or carry on without that part.
What it holds then groups the site the way Squarespace does: Shop, Customers, Orders, and Pages and design. Each part says whether it is copied, and what is left for you, such as gift cards or the shop's Stripe keys.
2. Destination: connect the v6 instance and start a dry run
- Press Log in to Insites Console. Console opens in a new tab. Create a new, empty v6 instance there (how), come back to the tool and press Next.
- In Insites Console, open the new instance and its CLI tab. Press Get my token and copy the token.
- Back in the tool, give the v6 instance URL, paste the token into Console access token, and press Connect and check. The tool checks your role and that the token is for this instance. More on the token.
- What it holds shows what the new instance has already. A new one holds only the platform's own starting content.
- Choose Dry run and press Read the source.
A dry run reads both sides and reports exactly what a migration would do. Nothing is written anywhere, and it can become the real migration later without reading the site again. The tool reads the shop through the API, and every page from the live site, loading each one in a browser to find the files Squarespace's scripts fetch. A progress bar shows while it reads.
3. Transform: give the tool what Squarespace has no API for
The stage opens with Analyze, which reads the whole site, and Next opens once the read is done. Each step after it says first whether it needs a decision. Two of them need you on a Squarespace migration.
- Redirects: the step shows the redirects the tool found by asking the live site. Paste the URL Mappings into Paste the export and press Use this list to use the site's whole list instead. Each line that is a redirect, such as
/old-page -> /new-page 301, becomes a page at the old address that sends visitors on with the same code. A line with Squarespace's[variables]is named and left out. - Forms: every form is recreated in the Insites form builder, with its own table. Type who each form's workflow email goes to: Squarespace does not say. The autoresponder is made switched off for you to turn on later. Add each form's CSV of past submissions under it. Each column is matched to a field by its name, and a column that matches nothing is named. A form with no file starts empty, and fills as people send the rebuilt form.
The other steps usually need nothing, but each shows what is copied: Pages and code, Site files, Databases, CRM (each Squarespace profile is copied as a contact), Users (nobody signs in on the new site, and Squarespace's administrators are not copied), Ecommerce (the shop's products, orders and payments), Events (Squarespace events are copied as pages), Locator, Other and Advanced. Advanced is last, and holds the rules for an unusual migration, closed until you open them. On the last step, press Continue to the plan. The redirects and submissions you added are saved as you add them, and the plan includes them. Every setting.
4. Plan: read what will run
- Summary and decisions: the numbers, and anything that would stop the load, each with a button to fix it. Each fix asks why, and the reason goes in the report. More on resolving the plan.
- What the load carries: the pages and the files.
- Fixes: anything the tool can fix for you, shown line by line, or a note that there is nothing to do.
- Changes and what is not copied: what changes on the way, and what is not copied.
Check three things before you go on:
- The shop. Products, categories, orders and payments go into the Insites Ecommerce module, and every profile with an email becomes a CRM contact. A gift card is left out: gift cards are coming to Insites.
- The pages. Every page the sitemap lists is copied. A password-protected page cannot be read, so it is named for you to rebuild.
- What is left behind. Shipping options, discount codes and order emails have no API. Each is named, and the To do list says what to do.
When the plan reads right, press Run it for real on its last page. It uses this exact plan.
5. Load: confirm with the plan code
Confirm the load shows the plan's code. Type it into Plan code and press Load. The tool loads the shop, the contacts, the files and the pages. You can close the page: we email you when the load finishes, and again when the checks finish. If the load stops, the page says why in plain words, and it can carry on from where it stopped.
6. Verify: see what was checked
The checks start by themselves when the load finishes, and usually take a few minutes. These matter most for a Squarespace site:
- Records, read again from the source: every product, order and contact matches the shop as it is at that moment.
- Pages say the same: each copied page says the same words as the Squarespace page.
- What pages load: no page loads a file from Squarespace.
- Redirects: every redirect, from the URL Mappings or found on the live site, sends visitors to its page.
Verify is five steps. Result opens with two figures: the records copied, out of the records on the old site, and the items checked that passed, out of every item checked. Then the table of what was checked. Send to GitHub sends the new site's code to your repository, where GitHub is connected. Things that need you takes you through what failed, one thing at a time, each with one thing to do about all of it. Worth a look has the page photographs and the errors the new site logged, which do not decide the verdict. The Verification log holds every verification in full. Anything you must do yourself is on the To do list too. After you fix something, press Check again. The checks.
Then try the new site. Send a test from a form: it lands in the form's table, and the workflow email arrives. The form is in Forms in the instance's admin. Add a product to the cart on its page and open /cart. Checkout says Stripe is not set up until its keys are added, which the To do list covers.
7. Launch: the launch, in time order
Launch opens with a timeline of the launch and marks where you are. The jobs only a person can do, written for this site, sit in the step they are done in: Before cutover, Cutover or After cutover. Tick each one off as you go. The jobs most Squarespace shops have, in that order:
- Connect the shop to the site's Stripe account. Add the keys in the instance admin, under Integrations, Stripe, add the webhook the job names, then buy something cheap and refund it.
- Decide what the shop charges for shipping, and what to do about discount codes. Checkout charges no shipping and takes no code. The job lists what Squarespace's orders paid and used.
- Email buyers about their orders: switch on receipts in Stripe, so buyers get an email for each payment and refund.
- Honor Squarespace gift cards yourself. Download them, and the value left on each, before the Squarespace plan ends.
- Open each form in the form builder, check who its workflow email goes to, read its autoresponder and switch it on, and move newsletter sign-ups to the mailing list.
- Add the site's domains to the new instance in Insites Console, and point their DNS at it once editing has stopped and the final sync has run. Leave the email records alone.
- Keep the Squarespace site until the 14-day watch ends. Then export the orders, gift cards and contacts, and end its plan.
- Cutover: going live, in order. Stop editing in Squarespace, run the final sync so the new site has the last changes, move the domain, and check the site on its domain. Copy first, then cut over.
- Nightly sync: chosen when the load finishes, and changed under Before cutover. It keeps the new site in step with the old one every night until cutover.
- Watch: for 14 days after cutover, every page and the log, every 6 hours, with a summary email a day.
- Report: two PDFs, each kept in the tool as well as downloaded. Summary for your client is one or two pages for the site owner, with the Insites logo and no check codes: the old address and the new, what was copied, the result in one line, what was not copied and why, and what is left to do. Send it as it is. The Technical report is the whole migration: every check and what it was first tried on, what was left behind and why, and every decision with who made it and when. The reports.
- Close: when the new site has run cleanly, press Close the migration, type the old site's address, or its Insites name, which the dialog shows, and press Close the migration. The migration becomes a record, and the tool removes its copies of both keys. Until then, a load can be rolled back.
Last, delete the API key in Squarespace, in Settings, Developer tools, Developer API Keys.