Synthetic Industry

Collection · updated 2026-10-11

Leaving Wix or Squarespace: the order of work from page list to domain switch

An ordered process map for moving a small site off Wix or Squarespace: inventory, what exports, rebuild, posts, forms, redirects, domain switch and checks, with the guide and job for each step. The fixed-price move project builds on Webflow.

1. Make the page list

Before you export or rebuild anything, list every page, post and address, with its title, description and images. This list becomes the parity sheet and the redirect map. If you cannot list the pages, the site is not ready to scope.

  • Sources: the sitemap, the menu, analytics landing pages.
  • Keep the old site live until the end.

2. Find out what the old builder will export

Wix cannot export blog posts or be hosted elsewhere. Squarespace exports some page types to a WordPress file and not others, and images may not migrate. Know the gaps before choosing the new platform.

  • What exports: the leaving-a-builder guide.
  • Export CMS collections and store products first where allowed.

3. Rebuild page by page and compare

Rebuild each page on the new platform from the list and compare text, images, links, titles and descriptions with the old one. Record every difference you approve.

  • Bounded job: the site move project covers up to 60 old addresses in all, for example 10 pages and 50 posts, built on Webflow.

4. Bring in the posts

If posts can be put in a spreadsheet, import them with a written mapping of columns to fields, test on a copy and check every row. Otherwise copy them from the live pages.

  • Mapping traps: the CSV import guide and example.
  • Bounded job: import up to 200 rows with field mapping.

5. Test the forms

Each form on the new site gets a labelled test that must arrive in the named inbox. A form that looks right and does not deliver is the commonest loss at launch.

  • Bounded job: make one form deliver every submission.

6. Load the redirects, check them on staging and carry over titles

Map every old address to its new page, to an approved not-found page, or to a list of addresses that cannot be redirected. On Webflow, load the rules in the project and check each target page on the staging address; the redirects themselves can only be proved on the real domain after the switch. A WordPress target needs its own redirect route, such as a plugin or rules held by the host, and the fixed-price project does not cover it. Copy titles and descriptions across.

  • Tool limits: the redirect guide and the sheet example.
  • Bounded job: redirect up to 60 old addresses and keep titles.

7. Switch the domain, with a way back

Only after you have accepted the new site does your account holder change the domain records, following a checklist that also records how to go back. Allow up to 48 hours for connection and certificate, and keep the old site until the new one has been checked from two networks.

Old addresses on your live domain reach the new site only after the switch, so the test of every old address runs straight afterwards on the real domain, and the way back is ready if it fails.

  • Test every old address for status, final address and hops straight after the switch.
  • If the certificate stalls: the domain certificate guide.
  • Bounded job: connect the domain and issue its certificate.

8. After launch

Keep redirects in place for at least a year, watch for new not-found addresses, and expect search results to fluctuate for some weeks. Nothing in a move can promise rankings.

  • Check the not-found log monthly.
  • A monthly forms and embeds check keeps the new site working.

Sources and limits