Skip to content

Console · Migration Tool

Connectors

Last updated 18 November 2026

Connectors

Every source reads through its own key, only reads, and never writes back. The tool keeps the key encrypted for as long as the migration needs it, and removes it when you close the migration. How long a key is kept.

SourceStatusWhat it readsKey
Insites (previous platform), and Insites sitesAvailableEverything the site holds: data, people and their passwords, code, files and constants.The GraphQL admin key, or your previous Insites Console sign-in
Insites v4AvailableEverything the site holds, its CRM placed in the Insites CRM: contacts, administrators, activities and dropdown values, plus people and their passwords, code, files and constants.The GraphQL admin key, or your previous Insites Console sign-in
WebflowAvailableCMS collections and every item in them, images and files, every published page with its design, collection pages and lists, redirects, the sitemap, and what people sent through its forms.A site API token
SiteglideAvailableModules, web apps and what people sent through forms, each as a table named the way the site names it, plus menus, people, files, and pages and forms translated to run on Insites.The site API key, or your Siteglide password
ShopifyComing soonProducts, orders, customers, content, themes, files, scripts and discounts.A custom app with Admin API scopes
WordPressAvailableEvery published page with its design, whatever built it, posts and every other post type as a table each with a collection page, the media library, its people, its Contact Form 7, WPForms and Gravity Forms forms rebuilt in the Insites form builder, redirects, and a WooCommerce shop: products, orders and customers in the Ecommerce module and the CRM, with a cart and a Stripe checkout on the new site.An Application Password
SquarespaceAvailableEvery page with its design, its forms rebuilt in the Insites form builder, redirects and past form submissions from the files you give, and the shop: products, orders and customers in the Ecommerce module and the CRM, with a cart and a Stripe checkout on the new site.An API key
WixBetaEvery published page with its design, the blog, CMS collections as databases, forms rebuilt in the Insites form builder with their past submissions, contacts and members in the CRM, media and redirects. A Wix store stays on Wix.An API key and the site ID: get them
GoDaddy (Website Builder)AvailableEvery published page with its design, menus, blog posts and files, its forms rebuilt in the Insites form builder, redirects, and past form messages from the files you give. The online store and contacts stay on GoDaddy.The site's address, and optionally a Domains API key
GitHub (a static site)BetaA static site in a GitHub repository: plain HTML, a GitHub Pages site, or the built output of Jekyll, Hugo, Eleventy, Astro or a Next.js static export. Every built page, every file, its Formspree and Netlify forms rebuilt in the Insites form builder, and its redirects. Build pipelines, serverless functions and secrets stay behind, and the plan lists each.A read-only fine-grained token, the repository and the published site's address
Custom backendComing soonYour own REST API, with a schema agreed during the build.Agreed during the build

Available: anyone can choose it in the Source stage. Beta: built, and being proved on real sites; anyone can choose it in the Source stage, marked Beta there and on the connect step. If a beta connector does something wrong, tell us with Report a problem. Coming soon: planned, with no connector yet. On the Source stage, press a Coming soon platform to join its waitlist, and we email you when it opens. Your platform is not listed? Press Request a platform and tell us which one. A beta connector becomes available when a migration of a real site passes every check and its rollback leaves the destination as it was.

The tool tells an Insites v4 site from a previous-platform one when you connect. If you chose the other, it says so and stops before it reads anything. Is it v4 or previous-platform?

Every destination is an Insites site, reached with an access token from Insites Console.