Connectors
Insites v4
An Insites v4 instance moves to Insites v6 with its rows, people, CRM, code and files, the same way an Insites v5 instance does. The tool only reads it. Nothing is ever written back to the old instance.
Is it v4 or v5?
You do not need to know. When you connect, the tool reads which Insites the instance is from the modules it holds. If you chose Insites v5 for a v4 instance, or Insites v4 for a v5 one, it says so and stops before it reads anything: go back to Source and choose the other.
A few signs of a v4 instance: its admin is at /admin/insites, and it has no /admin/api page. In the Insites v5 Console its folder may be tagged Version 4.
What you need
An Insites v4 instance is managed in the Insites v5 Console, so you connect it with your Insites v5 Console sign-in, as you would a v5 instance.
- Find the instance's UUID. A v4 instance has no
/admin/apipage, so it is not there. Sign in to the Insites v5 Console and open the instance: its UUID is on its details. - In the tool, give the instance's address, then either its GraphQL admin key, or your Insites v5 Console email and password and the UUID. With the sign-in, the tool signs in once and keeps only the instance'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 v5 and v6. The Insites v4 to Insites v6 preset places each, and the plan shows every rule before anything loads.
| On Insites v4 | On Insites v6 |
|---|---|
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 v6. |
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: v6 administrators have none. |
Activities (insites_crm_activities) | CRM activities, each on the contact it was about, with v6'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 v6 already has. v4's industry_type is v6's industry. |
| Branding, time zone and date format, import logs, attachments, companies and addresses | The v6 CRM's own tables, under v6'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 v6 (CMS, Global Content in the admin), field for field. v4's PO box number is v6's box number. Every logo, icon and location image is copied as a file, whether v4 kept it as an uploaded file or as the address of an image, and the v6 field points at the copy. If a file field the old site had set holds no file on the new site, the COVERAGE check fails and names the field. An address v4 kept as single fields (Address Line 1, Address Line 2, City, State, Post Code, Country) goes into Globals > Locations > Location 1 (Address 1, Address 2, City, State, Postal Code, Country), unless Location 1 already holds a value there. A field with no clear match on v6, such as a search address, a location image, a phone or a fax, is named on the plan and not moved: set it on the new site yourself. If any Global Content value has no field on the new site, COVERAGE fails and names it. |
| Your own tables, pages, partials, forms, emails, files and constants | Copied as for any Insites instance. An uploaded image with versions (for example Mobile, Desktop, List-View or OG sizes) is fetched by the new site as an image, so the new site builds every version its table defines, and the old site's version addresses are not kept. v4 lists pages in its sitemap through its own site manager page, which v6 does not use, so each page a visitor opens is marked for the v6 sitemap, and a page that already has a sitemap setting keeps it. |
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 instance. The tool never reads a key into the move. Set the Google Maps and reCAPTCHA keys again on the new instance.
- Password reset links and tokens (
insites_reset_password,insites_default). They only work on the old instance. People's passwords move when you choose to move them. - The event stream (
insites_event_stream). v6 keeps its own. - Form Submission activities. The v4 CRM logged one activity for every form submission, with the type Other and a subject such as "Form Submission: Get in touch - 7". On v6 a submission is kept on its contact under Related data, so these activities are left behind, as they are from a v5 instance. The plan and the run report give the count and the reason. Every other activity is copied, and so are the submissions, each with the person it belongs to.
- The site manager's editor keys (
insites_vcl_user_profile,insites_vcl_master). v6 has no site manager.
A v4 column with no home on v6 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 v6: 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 v6. 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.