Console · Migration Tool
Insites (previous platform)
Last updated 18 November 2026
Insites (previous platform)
A previous-platform Insites site moves to Insites with its rows, people, CRM, code and files. The tool only reads the old site. Nothing is ever written back to it. Your first migration walks through the whole move.
Is it v4 or previous-platform?
You do not need to know. When you connect, the tool reads which Insites the site is from what it holds. If you chose Insites (previous platform) for a v4 site, it says so and stops before it reads anything: go back to Source and choose Insites v4. A v4 site keeps its CRM in other tables, and only the v4 source places them on Insites.
What you need
- The site's address, for example
https://example.com. Use the live (production) site, not a UAT or staging copy. The final sync copies the changes made on it. - One way in. Either the site's GraphQL admin key, or your previous Insites Console email, password and the site UUID. Fill in one way, not both. The tool refuses a form with both.
With the previous Insites Console sign-in, the tool signs in once, takes the site's admin key, and keeps only that key. It never keeps the password. How to get the GraphQL admin key shows both ways.
The key that starts with instance_ is refused. That is the site's REST API key. It cannot read ids or history, so the tool stops and asks for the GraphQL admin key.
Allow about an hour for a site of around 10,000 records. A bigger one takes longer.
What is copied
The Insites (previous platform) to Insites preset sets where each part goes, and the plan shows every rule before anything loads.
| On Insites (previous platform) | On Insites |
|---|---|
| Every table and its rows, including the tables that modules keep (the CRM among them) | Copied with their original ids and dates. The tool reads every record table, not only the tables the admin lists, because a module's own tables are not in that list. |
| People | Their email, names, slug and the id the CRM uses for them. Their passwords move only when you choose to move them. |
| Pages, partials, layouts, notifications, authorization policies and forms | Copied as the live code. |
| Files: assets and uploaded files | Copied from the old site to the new one while the load runs. The tool does not store them. |
| Constants | Copied value for value, in memory, when you leave them ticked. |
| Module versions | Read, so the plan can check that every module the old site uses is on the new one. |
| Translation files and the code that uses them | Listed in the plan as a code job. A row or a page is copied whatever language it is written in. |
What is copied lists every part, module by module.
What stays behind, and why
- Live keys. Two module tables hold live keys: the site configuration key and the constants. The tool replaces each value with a fingerprint before the row is stored. One of these keys can be the site's own REST API key.
- Password reset links. Every value in a reset table is scrambled as it is read, except the email, and the table is left behind. The new site makes its own.
- The private files of a module of your own. The admin API does not list them. Each module of your own is named in the plan under Left behind with the step to take: deploy its private files to the new site from the module's repository with the Insites CLI.
After the first copy
An Insites (previous platform) source supports a final sync, which copies only what changed on the old site since the last copy, and a drift check that shows what changed there. Both are on the Load and Launch steps. Copy first, then cut over explains the order.