Skip to content

Console · Migration Tool

What is copied

Last updated 18 November 2026

What is copied

Everything a site holds is counted and shown, grouped by the eleven Insites modules, then the site's own settings. Nothing is left out of the list: a part that is not copied says why.

Each part carries a status: Copied, Replaced, You do this, History or None. Statuses says what each one means, with every other status the tool shows.

This page is about migrating from an Insites site. For a Webflow site, see what is copied from Webflow. An Insites v4 site keeps its CRM in different tables, and Insites v4 says where each one goes on Insites.

What the Insites admin made for you is copied too

When you build with the Insites admin, it writes the result into your site: a CMS collection's pages and partials, a Site Manager page and its layout, a form's emails, an API address, a Databases table. These live in folders named modules/ins_... and they are yours, so they are copied and checked like the rest of your code. Only the modules/insites_... folders are the platform's own: the destination's modules bring those.

Code at the app's root

All of your code is copied, wherever it sits: the app's views, graphql, forms and emails folders, its API calls under api_calls, its SMS messages under smses, its policies under authorization_policies, the older notifications folders, and any module of your own. Each file keeps its path on the new site. Only the modules/insites_... folders stay behind, because they are the platform's own.

A partial whose file name starts with an underscore, such as _hero.liquid, is copied too. If the new site will not take it through its admin API, the tool writes it as a file, the way the Insites CLI does. Insites then gives it an address without the underscore, so CODE counts the two as the same when that underscore is the only difference.

A partial kept in a layouts folder, such as modules/website/public/views/layouts/blog/_header.liquid, is moved to the partials folder, here modules/website/public/views/partials/layouts/blog/header.liquid. Insites keeps partials under views/partials and refuses one under views/layouts with “Physical file path is invalid”. In its new place the partial keeps its name, here modules/website/layouts/blog/header, so every page and layout that shows it works as before. If the old site gave it another name, the move gives it the new one and changes every include, render, function and background that names it. A layout in the same folder stays where it is. The plan's Changes lists each move under Partials moved out of the layouts folder, and the CODE check, Copy this one again and Copy all again use the new place. When the code builds a partial's name while the page runs, the migration cannot tell whether it names a renamed partial, so it leaves that partial where it is and lists it on the To do list, with each call to check, its file and line, and where to move it.

A module of your own is copied with its public files. Its private files, under modules/<name>/private, cannot be read through the admin API, so each module of your own is named under Left behind with the step to take: deploy its private files to the new site from the module's own repository with the Insites CLI, then plan again or run a final sync.

By module

On Transform, each of these has a step of its own or shows on the step for its kind: CRM and Pipelines on CRM, Forms on Forms, Events, Ecommerce and Locator on their own steps, the people on Users, and Data on Databases. Anything Insites has no place for is on Other. The steps.

ModuleWhat is copied
CRMContacts, companies, addresses, activities, tasks, attachments, custom fields and every CRM setting. The import log is copied too. Each person's column choices in the contacts list start from the defaults on Insites.
PipelinesPipelines, stages, opportunities and their contacts, field values (won and lost reasons, divisions, lead sources) matched to the destination's own. Webhooks are copied switched off.
DataEvery database and its rows, with their ids and dates, and your own tables. A table the destination lacks is created with its labels, groups and field settings, including one with no rows, so the site can write to it after the migration. A table with no definition the tool can find, such as one a module's own setup created, can be created from its data: the plan offers Create it from the data. Each row keeps its owner: the person who owns it, and any column that names a person by number such as user_id, point at the same person on Insites, where people have new numbers. A row keeps its own external id where the new site can keep it, and the load report counts any it cannot. A row is never written over a different row the new site already has: when a row there, in the same table or another, already carries a row's id as its external id, the plan names those rows and offers Leave the database behind. A file column that holds an address as text, not an uploaded file, is copied as text: the plan names it, because the file the address names is not copied.
CMSYour pages, partials and layouts, with every setting: a page's response headers, its cache settings, how deep its address nests, its handler (such as markdown) and its subdomain, and a redirect with its code, 301, 302 or 307. A new Insites site's starter pages at the same addresses are replaced by yours, and put back by a rollback: the home page, the 401, 403, 404 and 500 pages, and the maintenance page at /maintenance.
FormsYour forms and their submissions, with each form's spam protection and the email, SMS and API call notifications it sends. A form made in the form builder stays one, and the Forms step lists it with who its workflow email goes to, which you can change. Its emails send from the new site's sender in Insites Console, like every other moved email: see Email and SMS notifications below. A website's forms are recreated in the form builder too: see Webflow and Squarespace. A rollback removes each form, its emails and its table.
Events, Ecommerce, LocatorEvery table. The store's test product and settings are copied under Insites's names; the currency, payment gateway and inventory switch are for you to set again.
AssetsEvery file the destination is missing, with its cache setting, and every uploaded file a row names, copied and checked. A site's own file can be unticked on Transform, Assets, so it is not copied, with a reason; an uploaded file a row names is always copied with its row. An upload column whose files are private stays private: its files are read through signed addresses and written private, and the plan lists those columns. A link in your code or records to an uploaded file or a site file on the old site, by its full address, is pointed at the copy the new site serves once that copy opens. That includes a page's settings, such as its Open Graph image, which shows when the page is shared. A file the old site links to that no row or site file of the move carries is copied from the old site into Assets, under ins_assets > old-site, and the link is pointed there. The new site keeps an uploaded file in a new folder, so only changing the start of the address would leave a link that does not open. A link the tool cannot point at a copy that opens is listed by the Links to the old site check and on the To do list.
PermissionsYour authorization policies.
APIAPI call notifications, after the secrets check reads their headers.

The site itself

PartStatusHow
PeopleCopiedWith their created dates and profiles: a contact's CRM details and an administrator's settings. A user profile type the site made itself, such as a member's answers, is copied too, under modules/ins_profiles/ where Insites keeps them, with every person's profiles of it. External ids are kept, because that is how the CRM refers to a person. Someone who already had an account on the destination, such as whoever set it up, takes the date they were created on the source. If the site will not change it, USERS says so on its own line rather than failing. Sign-in and activity dates, such as the last sign-in, the sign-in count and the last activity, stay behind: a person shows no sign-in on the new site until they sign in to it.
PasswordsCopied by choiceEach person's password is copied as the one-way scrambled form the source keeps, in memory during the load, for people the load creates. A person who already has an account on the destination keeps theirs and resets it.
ConstantsCopiedEvery constant by default, value for value, in memory. If the source's constants could not be read, none are copied: the plan warns, and INVENTORY fails until the source is read again. Untick any the new site must not have. One the new site already holds with a different value starts unticked, so its own value is never replaced unless you tick it. The keys Insites issues to each site for itself are never copied: every constant named insites_, such as insites_console_sso_key, which Console signs people in with, and jwt_encryption_secret. The new site has its own. Payment keys stored as constants for known providers, such as Stripe and PayPal, are not copied or offered either, such as insites_stripe_sk_live_key or a site's own stripe_sk_live. The tool knows one by its name, so a key under a name that does not say it is one is copied like any other constant: they belong to the client's account with the payment provider, and a To do job names each one to add on the new site. The same To do job is made when the site's code reads payment keys, such as the ecommerce module's Stripe payments, even if the old site holds no key with a value, so the new site's log accepts the error that code writes until the keys are set.
SendGrid keys (constants)Never copiedA constant that is a SendGrid key, by its name (such as SENDGRID_API_KEY) or by the shape of its value under any name, is never copied and cannot be chosen. Insites sends email through its own built-in SendGrid account, so the new site needs no SendGrid key from the old one.
Email and SMS notifications, GraphQL queriesCopiedYour own, with every setting. Each email sends from the new site's sender in Insites Console. One that sent from your own address keeps it whenever Console lists it for the new site, and replies go to it when the email had no Reply-To. One whose sender was worked out from the form, such as the visitor's address, sends from the new site's sender, with replies going to that address. One that chooses between senders in code is moved as it was and is on the To do list. An email with a blank From never sends on Insites, so it gets the new site's sender too. The new site's CRM module must be 6.1.2 or later, or none of these emails would send: the plan is blocked until you update the CRM in Insites Console and plan again. The emails of the Insites modules themselves, and SMS and API call notifications, which have no sender, are not changed. The plan's changes list every email with its old sender and its new one.
Site settings in config.ymlYou do thisNo admin API sets them, so they are not copied. Each setting that differs between the two sites, such as liquid_raise_mode or string_interpolation, is a job on the To do list, with its value on each site. If either site's settings could not be read, the job asks you to compare them yourself.
IntegrationsYou do thisEvery integration except SendGrid is set up again in Insites Console with the provider's key.
Email sending (SendGrid)Built in on InsitesNot moved, and nothing for you to do. Insites sets up email sending (SendGrid) for every new site automatically, with its own SendGrid subaccount, so there is no SendGrid key to bring and no SendGrid integration to set up again.
Git repository connectionYou do thisThe repository's address and SSH key are kept in Insites Console, not on the site, and the private key is never given back, so they are not copied. When the old site has Sync CMS changes to Git on, the To do list has a job to connect the repository on the new site, under Integrations, then Git Repository.
The site's own migrationsRecorded as run by choiceA migration in app/migrations or in a module of your own runs once on each site, and the site remembers it ran. The new site has never run the old site's, so the first deploy of the site's code there would run every one of them again, over the copied data. A migration that adds rows, such as a seed of sample locations, would make duplicates. So after the data is copied, the load records each migration the old site has run as already run on the new site, without running any of it: it sends the migration with an empty body, runs that, and sends the real file back. A later deploy then finds it done. The plan's Worth knowing names each one, and one that does more than add rows, because it changes a table or a setting such as a constant, is named on the To do list, to check the new site has what it does. One the old site has not run, or that failed there, is left alone and named. Untick Record the site's migrations as already run on the plan to leave them to run on the first deploy. Recording one cannot be undone: a rollback of the load leaves it recorded.
TranslationsCopied from Insites (previous platform) and InsitesThe site's translation files (app/translations, one file per language, every language) are copied after the code. No admin API lists them, so they are read from the old site's export of its code, the way insites-cli pull reads them, and written the way insites-cli sync writes a file. They are merged with any the new site already has: a translation the new site holds with other words keeps its words, unless they are the words this migration put there, and a translation it keeps in another file is not written a second time. The TRANSLATIONS check confirms every translation the copied code names shows its words on the new site. A file the tool cannot read, or the new site does not take, is a job on the To do list, and so is a translation the code names that the old site never had. A rollback puts the new site's own files back. From Insites v4 and other platforms, translations are a job on the To do list.
Password reset linksReplacedNever copied, on Insites v4 and previous-platform alike. They are scrambled as they are read and the table is always left behind. The new site makes its own.
Sent notification log, data exportsStays on the old siteThe sent log is the old site's history of every email, SMS and API message it sent, kept by the platform, not in a database: Insites cannot load past history, and the new site starts its own log. Data exports are CSV copies someone downloaded from the old admin; every record they came from is copied. Download either from the old site's admin before you switch it off. Both are counted in the report.
Module codeReplacedEvery site has every Insites module, so their code is never copied. The plan compares each module's version on the two sites, and lists one only when the new site runs an older version.