Reference
Transform settings
The rules the plan applies between the source and the destination. They start from the source's own rules: the Insites v5 to v6 rules for a v5 instance, and the Insites v4 to v6 rules for a v4 one, which add how v4's CRM is placed in v6's (what is copied). Every rule that leaves something behind carries a reason, and the reasons go in the report.
The steps
Transform describes what will happen. Until the load runs, each step says what will be copied, and its marks read Will copy or Will skip. While the load runs they read Copying or Skipping, and afterwards Copied or Not copied, as in the report.
Transform opens with Analyze, whose only job is reading the source: every record, person, page and file reference, table by table, into the tool's encrypted copy. Nothing is changed on either site, and you can close the page while it reads. Next is held until the read is done, then opens Pages and code. After Analyze, Transform has one step for each kind of thing a site holds, in this order, and every step shows for every source. Each one lists what the site has, how many, and what happens to each: Copied, Rebuilt, You do this, or Not copied with its reason. Nothing on the old site is changed or deleted. A kind the site has none of still shows, saying This site has none, so you can see it was looked at. Where the tool cannot read that kind from the platform at all, the step says so instead, and a store the tool cannot read yet says Coming soon.
| Step | What it shows |
|---|---|
| Analyze | The read of the source, with how far it has got, what that means in plain words, and the activity log. Once the source is read it says how many rows and tables were read, and the step is marked done. Reading an Insites instance reads several databases at a time, in the order of the steps below, and reads the pages, code, people and files first. Each step opens as soon as its own part is read, to look through, with Ready to look through at the top; its choices open once the whole read is done. A step whose part is not read yet says Waiting, and Next waits for it. A Webflow or Squarespace site is read in parts the same way, several parts at a time: its collections, form submissions, file library, pages and redirects, or its shop, customers, orders, payments, pages and redirects. Analyze says of each part that it will be read, is being read or has been read. A step whose part has been read says Ready. This part of your site has been read., and one still waiting says Waiting for this part of your site to be read. Pages and code opens once the pages have been read, because a site's pages are built from its collections, forms and files. A read stopped part way carries on from the first part not read yet. |
| Pages and code | The site's pages and the code they are built from: page frames (layouts), shared sections (partials), and the rest of its code, such as emails, data queries and sign-in rules. |
| Site files | The site's own files: images, stylesheets, scripts, fonts and documents. |
| Databases | Every database of the site's own, and the tables of the Data, CMS, Assets, Permissions and API modules, each with where it will be copied to. |
| Forms | Every form, that it is recreated in Insites, the database it saves to, and its past submissions. The tables forms save to are here. Check before the load reviews each form the move rebuilds for what is likely to go wrong, and Forms from another service can rebuild a JotForm, Typeform or Google Forms form as an Insites form. Each rebuilt form that asks for an email address adds a CRM contact for each enquiry, unless you untick it. More. |
| CRM | Contacts and companies, and everything else the CRM holds: addresses, activities, tasks and custom fields, with Pipelines in a section of their own. In Insites a contact is a person, so the people themselves are on Users, copied once. |
| Users | Who can sign in to the site, with their passwords and profiles, and whether the site's administrators will be copied. From an Insites instance each administrator will be copied with their administrator profile; from a website platform they are not, and administrators are added in Insites Console. |
| Ecommerce | The store: products, categories, orders and payments. An Insites store and a Squarespace store will be copied. A Webflow or Siteglide store cannot be read yet, so the step says Coming soon. |
| Events | The Events module's tables. |
| Locator | The Locator module's tables. |
| Other | What the site has that Insites has no place of its own for, such as a module Insites does not have, legacy data types, or the old instance's history. A table here will be copied as a database named after it, or left behind with a reason that goes in the report. One with no definition can be created from its data here. |
| Redirects | Every old address that sends visitors on to a new one. |
| Advanced | The rules for an unusual migration, closed until you open them: Renames and rewrites, and Single records and secrets. |
Each table shows on one step only: on its module's step for the CRM, Pipelines (on CRM), Forms, Events, Ecommerce and Locator modules; on Forms when a form saves to it; on Other when it belongs to a module Insites does not have; and on Databases otherwise. Where it goes, or why it stays behind, is set the same way on every step. A link to an old step name opens the step that holds it now: Form submissions opens Forms, and People opens Users.
A table an earlier move made
Nothing the move writes onto the new site is named after the platform it came from. The site's layout is called site, its pages sit at their own addresses under views/pages/, its partials, queries and files go in a site folder, its tables and forms have no platform prefix, a column the platform kept (its id, its dates) starts with source_, such as source_id, and a label says "old site" or "source" where it used to name the platform. A site an earlier move already loaded keeps the names that move gave it: when the new instance already has the platform's layout, a page in the platform's folder or a table with its prefix, the run says so in its log and writes the same names again, so a Run again or a sync never leaves a second layout or a second copy of a page.
A Webflow form table that an earlier move made under its older name, webflow_form_ or webflow_ followed by the form's name, is reused rather than copied twice: its rows and its form are written into the table the new instance already has. The same goes for a form an earlier move numbered because its name clashed, such as email_form_2, when a later read names it plainly: if the new instance has the numbered table, with every column the form has, and not the plain one, the form keeps the numbered name, and every page that shows the form is pointed at it. Once the plan is built, the row on Databases or Forms says so under Will be copied into, with Will reuse an existing table and that table's name, such as webflow_form_newsletter. While the load runs it reads Reusing, and afterwards Reused.
The settings
| Setting | What it does |
|---|---|
| Databases | Where each source table goes, and which are not copied. Tick Copy only some tables for a partial migration. |
| Pages and code | Which of the site's own layouts, partials and pages will be copied, grouped by kind, each ticked to copy. Untick a file, or untick a whole group or the ones a filter shows, to leave it behind; it is written under Code files left behind with the reason Chosen not to copy, which you can change. The page warns when a layout or partial that is not copied is still used by a page that will be copied, and names the page, and so does the plan. An Insites module's own files are not listed. A file someone added inside an Insites module folder, such as a webhook page in modules/insites_api/, is not the module's: it is your own code, so it is copied to the same path, named in the plan's Changes as a custom file inside an Insites module folder, and counted as yours on INVENTORY. To leave one behind, add it under Code files left behind with a reason. If it holds what looks like a secret written into a public file (a name such as token or api_key set to a value), the plan says so without showing the value. |
| Site files | Which of the site's own files will be copied: its styles, scripts, images, fonts and documents, listed by folder with each file's size, every one ticked to copy. Untick a file, a whole folder, or the files a filter shows, so they are not copied, each with the reason Chosen not to copy, which you can change. A folder unticked whole is saved as one rule, for the files directly in it. The load does not copy a file that is unticked, the plan and the report list it with its reason, and the ASSETS and INVENTORY checks count it as left behind with that reason, never as missing. The page warns when a page, partial or layout that will be copied still uses a file that is not copied, and names both, and so does the plan. Uploaded files a database row names are not listed: each will be copied with its row. Nor are an Insites module's own files, or the system pages module's. |
| Code files left behind | Any file of the site's code that must not travel, named by its path, with a reason: an email, an API call, a query or a policy, and every page, partial and layout unticked on Pages and code. The load leaves it out, and the CODE and INVENTORY checks count it as left behind with that reason. When the file is a form, the plan also takes the form out of every page, partial and layout that still draws it, and lists each one, so none shows "Could not find Form with name" on the new site. |
| Renamed fields | A field the new instance calls something else. |
| Fields left out | A field the new instance has no place for. Its values are not copied; the report counts them. |
| Text replaced in values | Text replaced inside values, for example a database name stored as text. |
| Text replaced in the code | Text replaced in your code as it is copied, for example the old instance's address. |
| Lists the new instance already has | Fixed lists, such as the CRM's system fields, that the new instance already has its own records for. Anything that pointed at the old record points at the new instance's one. |
| Single records left behind | One record that should not travel. |
| Single values fixed | One value on one row, changed on the way. Both kinds of single-row rule name the table and the row's id; on a website the row can be named by its id on the old site. A rule that matches no row stops the plan. More. |
| Tables created from the data | A table the plan could not find a definition for, created on the destination from the fields its rows hold. Chosen on the plan with Create it from the data, with a reason, or ticked on Other. |
| Hidden fields | Every value in the field replaced by a scrambled stand-in, so the real value never reaches the new instance. |
| Possible secrets kept | Fields the secrets check flagged that are safe to copy as they are. |
| Files accepted as missing | A file the source cannot serve either. Usually accepted on the Things that need you step. |
| People accepted as they are | A person whose account on the destination differs from the source, usually because they had one there before the migration. Accepted, by email and with a reason, on the Things that need you step. |
| Users | For someone who already has an account on the destination, matched by email. Nobody is created twice either way. Keep their destination account as it is (the default) points everything that names them at that account. Give their destination account the source's identity changes the account instead, so anything already on the destination that names them stops finding them. When nobody on the source has an account on the destination, the choice changes nothing. |
What the Transform pages show for an Insites source
Redirects lists every redirect on the source: an old address, where it goes, and whether it is permanent or temporary. On Insites a redirect is a page, so each one will be copied with the code. To leave one behind, untick its page on Pages and code. When a page or a collection item answers at a new address on the new site, the step also lists it under Addresses that change: the old address, the new one, and a permanent (301) redirect from one to the other, marked as added by the tool and ticked. On the new instance each redirect from a website (those you paste, those the old site keeps, and those the tool adds) is written to Settings > Redirects in the admin, so you can see and change it there. A wildcard redirect, which that screen cannot hold, is written as a page that redirects. Until redirects added on that screen answer visitors, each is also written as a page that redirects, which is what answers; the REDIRECTS check proves every one answers with one hop. An Insites instance's own redirects, kept there as pages that redirect, are written to Settings > Redirects the same way when they name one exact address and a plain target. An old address the new instance's Settings > Redirects already has is left as it is there, with no second redirect: the plan lists it as already on Settings > Redirects with its target, and the checks ask it at that target. Redirects on that screen are answered by the 404 page through modules/insites_crm/functions/redirects/404_redirect, so a 404 page the move copies without that line gets it added at the top. If the move copies no 404 page and the new instance's own does not include it, the plan warns that redirects on that screen will not answer until it does. Untick one to leave its old address without a redirect, and say why. A redirect you gave, or the old site's own, for the same old address wins over the tool's. Forms lists each form, that it is recreated in Insites, and the table its submissions are kept in, with how many there are: they will be copied with the data, so there is no file to add. Each page says when its defaults are ready and changes are optional, and when there are none. A step whose list is still being worked out says Waiting and holds Next until it arrives.
Long lists
For a website, the redirects you paste and the form submission files you add can be long: up to 5,000 redirects, and 20,000 submissions across every form. The page sends a long list to the tool in pieces, each kept encrypted beside the copy of the site, and the settings keep only how many there are. A request that would still be too large is stopped before it is sent, with what to do in plain words.
Saving the Transform pages keeps every setting they do not show, such as the people you accepted as they are on Verify, so a final sync still has them.
Undo all
A step you changed says so in one line under its heading, for example You changed 2 settings on this step. Undo them. Undo removes only that step's changes and leaves every other step as it is. A step with no change of its own shows nothing, and so does a migration with no changes. Analyze names the steps you changed, each a link to that step, for example You changed settings on Forms, Redirects and Databases, with Undo all. The ? beside it says what Undo all does, on hover, on keyboard focus or when tapped. Undo all removes every change, on the Transform pages and the choices made on the plan, which are kept as transform settings too, and builds the plan again from the standard settings. It lists what it will remove, step by step with counts, and asks first. Advanced shows the same list of linked steps, because that is where people look for rules and find none of their own.
The v5 to v6 rules also copy the CRM from insites_core into insites_crm, copy people's profiles into v6's profile types, move the site's own user profile types from modules/ins_permissions/ (and the older modules/ins_permission_manager/) to modules/ins_profiles/, where v6 keeps them, and create each one on the new instance before the people who hold it, change the code that names those types, make each short name of a query, form or database in the code full where only one is meant (the rest go on the To do list with their file and line), switch webhooks off for the migration, and write v5's object logs as text where v6 declares text. Once a load has run, its settings are a record and cannot be changed.
Database tables on v6
v6 lists a site's own databases only when they live under modules/ins_databases/. The v5 to v6 rules therefore move every v5 Data module table (modules/ins_database/<name>) and Content Manager table (modules/ins_content_manager/<name>) to modules/ins_databases/<name>, and change the queries and Liquid that name each table to the new name. Rows keep their ids, their data and the dates they were created and last updated.
Every field is set up the way v6 expects for its type: an upload shows an image or file uploader, a phone number held as text uses a plain text box, and formatted text uses the HTML editor. An email field links to the matching CRM contact. When a table does not choose its own list columns, a few of its main fields (a name, an email, a phone number) are shown, searchable and sortable in its items list. Long text, HTML and uploaded files are never list columns, because v6 cannot show them there.
SEO tags in a layout
A layout from a v5 instance that captures yield 'seo' and then prints the captured text would show the tags as text on v6. The plan offers a fix that yields directly, so the page's SEO tags render in the head.
Each enquiry adds a CRM contact
Every form the move rebuilds in the form builder that asks for an email address adds the person to the CRM. When someone sends the form, the CRM contact with their email address is found, or made with their first and last name and phone number, and the enquiry is linked to that contact. The same address in capitals finds the same contact. An enquiry with no valid email address is still saved, and adds no contact.
It is on by default. The Forms step lists it for each form, under Adds a CRM contact: untick it for a form whose enquiries should stay out of the CRM, then save your Transform choices. A form whose name is one field, such as Name, is split on its first space, so Jane Q Tester becomes Jane, and Q Tester.
It is a short piece of code in the form's Callback actions, under Settings in the form builder, and it starts with imt:crm-contact. Editing the form in the form builder keeps it. To stop it later, delete it there. A form a site already had its own callback actions on keeps them, and gets none added. For a site moved before version 0.8.8, see Add past enquiries to the CRM.
Where replies to the autoresponder go
The autoresponder always has a Reply-To, so a person who answers it reaches someone. It is the first address the form's workflow email goes to. When nobody is named on the Forms step yet, it is the address the old site links to most, such as the mailto: link in the site's footer. When the old site links to no address, the Forms step says Nobody for replies yet: add who the workflow email goes to, and replies go there.
The old reCAPTCHA script
Once every form on the site uses hCaptcha, the old site's reCAPTCHA script, such as www.google.com/recaptcha/api.js, is taken out of the copied pages, layouts and partials, because nothing calls it any more and every page loaded it. If anything on the site still uses reCAPTCHA, the script stays. The plan's Changes lists it under Old reCAPTCHA script removed. Where the old site connected early to its platform's file host, the copied pages connect early to the new site's file host instead.
AI on the Forms step
Check before the load runs once each time the plan is built. Plain checks look at every form the move rebuilds, and AI adds labels and fields that look sensitive. It flags a form that saves to a database that is not copied, so it would post to nothing; a field with no label of its own; a form that emails nobody; a form with no thank-you message of its own; a field that looks like it collects what a website form should not, such as a card number, a password or health details; and a form with no spam protection, which says what a bot sends is saved, or saved and emailed when the form emails someone. Where the tool can fix it, one button does: Use the label, Turn on hCaptcha, Leave this form out or Hide the values already sent. A fix is a Transform choice like any other, applied when you save. Where it cannot, the flag says what to do.
Forms from another service lists each JotForm, HubSpot, Typeform or Google Forms form embedded in the site. Rebuild it as an Insites form explains the proposal and what it builds. Nothing changes until you confirm and save.
Both count against the migration's AI limit. With the AI pass off, or once the limit is reached, the review is the plain checks and the proposal is the form as the tool read it. What is sent to the AI is each form's labels, kinds, choices and settings: never what anyone sent through a form, and never an address a form emails.