Moving to Insites is easy.
Bring your Webflow, WordPress or Squarespace site across in a few steps.
- Records12,903of 12,903
- People1,745of 1,745
- Code89of 89
- Files112of 113, one listed with the reason
- Source records accounted for13,270of 13,270
Where you can migrate from
Every migration lands on an Insites v6 instance. Each source reads through its own key, only reads, and never writes back to the old site. Not on the list yet? Pick a platform marked coming soon and we will tell you when it opens.
-
Available
Insites v5
Every table and its rows with their ids and dates, people, the CRM, pages, partials, layouts, forms, notifications, constants and files, from a v5 instance to a v6 instance. The GraphQL admin key, or your Insites v5 Console sign-in, is all it needs.
-
Available
Insites v4
Rows, people, the v4 CRM placed into the v6 CRM, Global Content, code and files. Connects with your Insites v5 Console sign-in, the same as a v5 instance.
-
Available
Siteglide
Modules and web apps with every item, pages with their design, forms and what people sent through them, menus, people, files and redirects. Reads through Siteglide's own service, as its command line tool does.
-
Available
Webflow
Collections and every item in them, every published page with its design, images and files, redirects, the sitemap, and what people sent through forms. A site API token is all it needs.
-
Available
Squarespace
Pages with their design, forms rebuilt to send to Insites, redirects, products, customers and orders.
-
Available
WordPress
Every page with its design, whatever built it, posts and every post type as tables with their custom fields, comments, menus, media, people, forms, redirects and a WooCommerce shop. An Application Password, or the site's export file.
-
Available
GoDaddy
A Website Builder site's pages with their design, menus, images, blog posts, forms and redirects. The online store and contacts stay on GoDaddy.
-
Available
GitHub
A static site in a GitHub repository: its built pages, files, Formspree and Netlify forms and redirects. A public repository needs no token.
-
Beta
Wix
Pages with their design, the blog, CMS collections, forms, contacts and members, media and redirects.
How a migration runs
Three steps, and nothing is written to your new instance until you have read the plan and confirmed it.
Extract
Connect your source. The tool reads it into a locked copy and counts everything the source holds, so nothing can go missing unnoticed.
Transform
Review exactly what changes on the way: tables renamed, lookups matched to what your new instance already has, and secrets kept out.
Load and verify
Start with a dry run to see what would change, row by row, with nothing written. When you confirm the plan, it loads, and every row, person and file is checked against the source.
Why move to Insites
One admin for the website, the people who use it and the business behind it. The CRM, forms, data tables and ecommerce are part of the platform, and so is Insites AI, so the migration is the start of something new, not just a copy of what you had.
After the migration
Put Insites AI to work on your site
Once your site is on Insites v6, Insites AI is in the admin, with your pages, tables, CRM and forms in reach. It answers questions, drafts changes and runs the routine work. Nothing is written until an administrator confirms it.
Insites AI is in early release on Insites v6 instances.
Add a Request a quote form to the Services page, and tell sales when one comes in.
Here is the proposal. It adds a form with name, email, company and a message to /services, saves each request in the CRM, and opens an opportunity in the sales pipeline.
- Form Request a quote, 4 fields
- Page /services, form added below the pricing table
- Automation New quote request: CRM contact, opportunity in Sales, email to sales
- Ask about your dataWhich enquiries from last month have no reply? Which products sold most this quarter? It answers from your tables, CRM, pipelines, events and forms, with a chart when you ask for one.
- Build by describingA whole page, with its partials, assets and a form, arrives as one proposal. You see a preview first, and the change goes to the site only when you confirm.
- Automate what happens nextWhen a form is sent, a record changes or a date arrives, an automation checks its condition and carries out its actions. Every run is logged.
- Reports that keep themselves currentSave a question to run on a schedule, pin a chart, and get a nightly summary of what changed.
- In Slack and Microsoft TeamsAsk from your team chat and approve a change with a button, without opening the admin.
- Safe by designEvery conversation and change is recorded and can be reverted. Owners can hide whole tables, or single fields such as email and phone, from the assistant.
Already on Insites v4 or v5?
The same tool moves your instance to Insites v6, with its rows, people, CRM, code and files, and checks every one of them on arrival. Here is what v6 gives you.
-
Insites AI
Insites AI runs on v6 instances. Moving is how a v4 or v5 site gets it.
-
The new Console
One sign-in for every instance, with members, roles, billing and the CLI tab in one place, and a sign-in to each instance's admin without another password.
-
Modules kept current
The CRM, forms, data, ecommerce, events and the other modules are built and updated for v6. New features ship there.
-
Nothing lost on the way
Rows keep their ids and dates, people keep their sign-in, and a v4 CRM is placed into the v6 CRM field for field. The old instance is only read, so it keeps running until you switch over.
Start with a dry run
Connect your source and read the plan. A dry run shows what would change, row by row, with nothing written. When the plan is right, confirm it, and the tool loads, checks and reports.