Connectors
Siteglide
The tool reads a Siteglide site through Siteglide's own service, the same way Siteglide's command line tool does, and copies it to an Insites v6 instance. It only reads. Nothing is ever written back to Siteglide. Migrate a Siteglide site walks through a whole migration.
What you need
- Sign in to the Siteglide Portal and open the site you are migrating.
- Open Site Details. Copy the site's system address, the address Siteglide gives the site (it ends in
us-siteglide.com,uk-siteglide.com,au-siteglide.comor similar). The site's own domain does not work here. - In the same place, reveal the site's API key and copy it.
- In the tool, give the system address, the email you signed in to the Portal with, and either the API key or your Siteglide password.
The email has to belong to an account that can open the site in the Portal: Siteglide checks the key and the email together.
The key screen asks for the API key or your Siteglide password, never both: choose Use the API key or Use my password, and only that field shows. With the password, the tool sends it to Siteglide once, gets the site's API key back, and forgets the password. Either way, the key is kept encrypted for as long as the migration needs it, and removed when you close the migration: how long a key is kept.
Before version 0.5.0 the tool kept the password instead and signed in with it each time. It no longer does, so a site connected that way must be connected again, with the API key or with the password once.
What is copied
| On Siteglide | On Insites |
|---|---|
| Each module (FAQ, Events, Blog and the rest) and each web app | A table in the Data module (Databases in the admin), named after the module's slug and labeled with its name. module_10 holding the FAQ becomes faq. |
| Each field | A column named after the field, so module_field_4_1 called Question becomes question. Each column is labeled, grouped (Content, Fields, Publishing, Search and sharing, Location), and its tooltip names the field it came from on Siteglide. |
| Each item | A row, with its id and the dates it was created and last changed. Items that are switched off are copied too, still switched off. The person an item belongs to (who sent it, or whose web app item it is) is the same person on the new instance, where people have new numbers. |
| Release and expiry dates | Date columns holding the same moment. Siteglide stores them as seconds since 1970. |
| What people sent through each form | A table for the form, named after it with _submissions (Contact Us becomes contact_us_submissions), one row for each time someone sent it. |
| Menus and their items | Two tables, siteglide_menu and siteglide_menu_item, so the site's menus can be rebuilt from them. |
| People | Users, with their names and details. See passwords, below. |
| Images and files | Copied to the new instance, including a file in a module's or web app's upload field, which is read from Siteglide under its own field name. |
| Pages, partials and page templates | Copied with the same addresses, translated so they run on Insites (see below). Only the partials and page templates a copied page uses are copied. |
| The home page | Answers at /, as on Siteglide, and its own address still redirects there. |
| The sitemap and robots.txt | Siteglide makes its own, and they stay. The sitemap is the one Insites serves at /sitemap.xml, listing every copied page that is searchable. The migration writes a robots.txt that keeps the rules the site's robots.txt on Siteglide holds and points to /sitemap.xml. A site whose robots.txt holds no rules gets one that lets every search engine in. Submit /sitemap.xml in Google Search Console once DNS has moved. |
| Redirects made in Siteglide's admin | Each one is copied at the same address, sending to the same place with the same code (a 301 or a 302), whether the place is on the site or elsewhere. The redirects check after the load tries each one. |
| Each form a copied page shows | A form in the Insites form builder (Forms in the new instance's admin), writing to the form's copied table, under the named columns, with the same layout, the same page to go to after sending, and the same hCaptcha. A rule that lets only some people send it moves with it when the rule is the site's own; one that is part of Siteglide's own code is named on the plan and the To do list. The button submits the form itself, so Siteglide's script is not needed. |
| Each form's emails | The form builder's own: a workflow email to the staff Siteglide sent its staff emails to, and an autoresponder made switched off for you to read and turn on, with replies going to the first staff address. Each enquiry also adds a CRM contact, unless you untick it on the Forms step (Each enquiry adds a CRM contact). Siteglide's own emails are copied too, with their wording, for reference, and are not sent. |
How pages are translated
A Siteglide page is ordinary Liquid, except where it calls Siteglide's own code. That code cannot be read and does not exist on Insites, so the tool writes Insites code that does the same:
| The page calls | On Insites it becomes |
|---|---|
siteglide_head and siteglide_foot | The page's title, description and sharing tags from its own settings, and whatever the page hands them with content_for. Siteglide's own script is left out: it only served Siteglide's forms. |
constants | Nothing. Where a page asks whether someone is signed in, it asks Insites instead. |
| A header, footer, content section or code snippet, by id | The site's own partial for it, which is copied with the page. |
| A menu with the default layout | A partial that prints the menu from the copied menu table, in its order, with the current page marked. |
| A form, by id and layout | The copied form, shown with include_form and the same layout. The page is made not searchable, because Insites shows no form on a page its own site search reads, and so it is left out of /sitemap.xml. |
A page that calls Siteglide code the tool does not translate yet, such as a module or web app list, a form that takes a payment, or eCommerce, stays on Siteglide. The plan names each one and the call that kept it, and nothing only that page uses is copied.
What is not copied yet
- Passwords. Siteglide's service does not give out password hashes, so people set a new password, or sign in with an emailed link, on the new site.
- Siteglide's own form emails. Siteglide sent each form's emails from its own code. The form builder's emails send instead: the workflow email goes to the staff Siteglide emailed, as the Forms step of Transform shows, and you can change it there. A test submission on the new site emails them, so tell them, or change the address while you test. Siteglide's own wording is copied for reference, under
emails/siteglide, and is not sent. - Answers copied onto a person's record. Siteglide can copy some answers from a form onto the person who sent it. On the new site they stay with the submission.
- Payment forms. A form that takes a payment through Siteglide's checkout stays on Siteglide, with its page.
- Pages that list module or web app items. They stay on Siteglide for now, named in the plan.
- Siteglide's settings. The table of Siteglide's own settings holds the site's Google and reCAPTCHA keys. Nothing on Insites reads it, and the keys never leave Siteglide. Set reCAPTCHA up again on Insites if a form uses it.
- eCommerce, email marketing and secure zones. These wait for a later version. Members are copied as people, and you set up again on Insites what each zone let them see.
After the migration
The To do list in Launch is written for a Siteglide site. It replaces the jobs written for an Insites instance, and adds the ones only a Siteglide site has:
- Domains. Siteglide's service does not list a site's domains, so take them from the Siteglide Portal, add each to the new instance in Insites Console, and point their DNS at it.
- Passwords. Ask everyone with an account to set a new password.
- Forms. Open each form in the form builder: check who its workflow email goes to, read its autoresponder and switch it on.
- Analytics. If the site's pages carry Google Tag Manager or Analytics, every visit to the new instance before cutover counts as a visit to the live site, the tool's own checks included. Filter the new address out until DNS moves.
- The Siteglide site. Keep it, and its plan, until the new site has run cleanly through the 14-day watch. Then close the migration on the Close step, make a new API key in the Siteglide Portal (or change the password the tool signed in with), and cancel the plan.
If it does not connect
| The tool says | What to do |
|---|---|
| That is not a Siteglide system address | Use the address from Site Details in the Siteglide Portal, not the site's own domain. |
| Siteglide did not accept this API key | Copy the key again from Site Details. |
| Siteglide refused that account for this site | Use the email of an account that can open this site in the Portal. |
| Siteglide did not accept that email and password | Check them by signing in to the Portal, or give the API key instead. |
| This site was connected before the tool stopped keeping passwords | Connect the site again: give the API key from Site Details, or your Siteglide password once. Nothing the migration has done is lost. |