Skip to content

Console

Migration Tool

Last updated 18 November 2026

Migrate a website or an Insites site to Insites, and prove nothing was lost.

The Insites Migration Tool reads a website or an Insites site, shows you everything it holds, plans the migration, loads it onto an Insites site, and then checks every row, person, file and page against the source. You approve every step, and a PDF report keeps the record after the old site is gone.

Start with the guide for where you are migrating from

Each guide walks one whole migration, from connecting the source to the jobs after the migration.

  • Migrate a Webflow site. Collections and their items, every published page with its design, redirects and form submissions.
  • Migrate a Squarespace site. Pages and design, forms, redirects, and the shop with its products, customers and orders.
  • Migrate a WordPress site. Pages with their design, posts as collections, the media library, people, forms, redirects, and a WooCommerce shop.
  • Migrate a Wix site. Pages with their design, the blog, CMS collections, forms and their submissions, contacts and members, media and redirects. In beta.
  • Migrate a Siteglide site. Modules and web apps, form submissions, people, files and pages.
  • Migrate a GoDaddy site. Website Builder pages with their design, menus, blog posts, forms and redirects. The store and contacts stay on GoDaddy.
  • Migrate a site from GitHub. A static site's built pages, files, Formspree and Netlify forms and redirects, read from its repository. In beta.
  • Migrate a previous-platform Insites site. Every module, person, file and piece of code, from a site to an Insites site.
  • Migrate an Insites v4 site. The same move as previous-platform, with v4's CRM placed in the Insites CRM: contacts, administrators and activities.

Not sure your platform is there? Where a site can migrate from lists every platform, and the ones coming soon. To run migrations with your team, see agency workspaces and what each role can do. What is copied lists every part of a site, by module.

The seven steps

A migration follows the same path every time. Each step is split into short pages, and the footer takes you through them in order. You can open any step you have reached from the list down the side, and nothing is written to the destination until you approve the plan and type its code.

  1. Source: Connect it and see what it holds
  2. Destination: Connect the new Insites site, pick a dry run
  3. Transform: Where each table and field goes
  4. Plan: Read and approve exactly what runs
  5. Load: Type the plan code to write, then choose a nightly sync
  6. Verify: Every row, person and page checked
  7. Launch: The launch, in time order: before, cutover, after, watch

A dry run stops after the plan and writes nothing.

Where to go next

Where the tool runs

The Migration Tool runs at migrate.insites.io. Sign in there with your Insites account. Its change log, with every release of the tool, is at migrate.insites.io/docs/changelog.