Console · Migration Tool
Insites v4
Last updated 18 November 2026
Insites v4
An Insites v4 site moves to Insites with its rows, people, CRM, code and files, the same way a previous-platform Insites site does. The tool only reads it. Nothing is ever written back to the old site.
Is it v4 or previous-platform?
You do not need to know. When you connect, the tool reads which Insites the site is from the modules it holds. If you chose Insites (previous platform) for a v4 site, or Insites v4 for a previous-platform one, it says so and stops before it reads anything: go back to Source and choose the other.
A few signs of a v4 site: its admin is at /admin/insites, and it has no /admin/api page. In the previous Insites Console its folder may be tagged Version 4.
What you need
An Insites v4 site is managed in the previous Insites Console, so you connect it with your previous Insites Console sign-in, as you would a previous-platform site.
- Find the site's UUID. A v4 site has no
/admin/apipage, so it is not there. Sign in to the previous Insites Console and open the site: its UUID is on its details. - In the tool, give the site's address, then either its GraphQL admin key, or your previous Insites Console email and password and the UUID. With the sign-in, the tool signs in once and keeps only the site's admin key. How to get the GraphQL admin key works the same for v4.
What is copied
v4 keeps its CRM in different tables from previous-platform and Insites. The Insites v4 to Insites preset places each, and the plan shows every rule before anything loads.
| On Insites v4 | On Insites |
|---|---|
A contact: their insites_customer profile, with their phone numbers and social links from insites_contact_number and insites_social_links | One CRM contact (crm_contact). A contact switched off on v4 is archived on Insites. |
An administrator (insites_administrator), with their mobile number | An administrator, active or disabled as they were on v4. The company a v4 administrator was given is not moved: Insites administrators have none. |
Activities (insites_crm_activities) | CRM activities, each on the contact it was about, with Insites's type: call, chat, email, event, file note, meeting, SMS or other. |
The CRM's dropdown values (insites_system_fields) | The CRM's system fields, matched to the ones Insites already has. v4's industry_type is Insites's industry. |
| Branding, time zone and date format, import logs, attachments, companies and addresses | The Insites CRM's own tables, under Insites's names. |
The site manager's Global Content (insites_global_content): company name, logos, locations, PO boxes and social links | The CMS Global Content on Insites (CMS, Global Content in the admin), field for field. v4's PO box number is Insites's box number. |
| Your own tables, pages, partials, forms, emails, files and constants | Copied as for any Insites site. |
What stays behind, and why
- Live keys. v4 keeps Google Maps and reCAPTCHA keys among the CRM's dropdown values, and the site manager keeps a key for the old site. The tool never reads a key into the move. Set the Google Maps and reCAPTCHA keys again on the new site.
- Password reset links and tokens (
insites_reset_password,insites_default). They only work on the old site. People's passwords move when you choose to move them. - The event stream (
insites_event_stream). Insites keeps its own. - The site manager's editor keys (
insites_vcl_user_profile,insites_vcl_master). Insites has no site manager.
A v4 column with no home on Insites is dropped only where it holds nothing. Where it holds a value, the plan asks you what to do with it. Nothing is dropped without you seeing it.
Code that calls a v4 module
Some v4 modules are not on Insites: the site manager, v4 activities and the v4 event stream. Their own files do not move, so a page of yours that calls one of their partials shows an error on Insites. Before the plan, the tool names each partial and the files of yours that call it, so you can rewrite them.
One is handled for you: modules/insites_site_manager/seo, which prints a page's title, description, canonical, robots and Open Graph tags. The move adds views/partials/insites_v4/seo.liquid to your own code, which prints the same tags from the same page settings, and changes each call to insites_v4/seo. If your site already has a file at that name, the calls are left as they are and named for you to rewrite.