Tutorial
Migrate a Siteglide site
This walks through a whole migration of a Siteglide site to a new Insites v6 instance: its modules and web apps, what people sent through its forms, its people and files, and its pages and forms, translated to run on Insites. A small site takes about twenty minutes. The steps are the same as in your first migration; this page covers what is different for Siteglide.
- A new, empty Insites v6 instance, the Developer role on it, and an access token from its CLI tab in Insites Console.
- A Siteglide Portal account that can open the site.
- The site's system address and API key, from Site Details in the Siteglide Portal. Or your Siteglide password instead: the key screen asks for one of the two, not both. Where to find them.
1. Connect the Siteglide site
Click New migration and, on Where are you coming from?, choose Siteglide site. The next screen asks only for the system address (for example https://my-school.us-siteglide.com, not the site's own domain). Then the key screen shows where to find the key in the Siteglide Portal: give the email you sign in to the Portal with, then choose Use the API key and paste the key, or Use my password and give your password, and press Connect and check.
What it holds groups the site the way Siteglide does: modules and web apps, form submissions, menus, people, files, pages and code, settings and history. Each group says what is copied and what is not. For example, a site with a contact form shows Contact Us under form submissions, as contact_us_submissions.
2. Connect the destination and start a dry run
Press Log in to Insites Console, create a new, empty v6 instance in the tab it opens, come back and press Next. Connect the v6 instance with the access token Console shows on its CLI tab, and choose Dry run. The tool reads the whole site through Siteglide's service and builds the plan. Nothing is written anywhere.
3. Read the plan
Transform opens with Analyze, which reads the whole site; Next opens once the read is done. The Siteglide preset is already chosen, so most sites need no changes after that. Each Transform step shows one kind of thing the site holds: its modules and web apps are on Databases, its forms on Forms, its people on Users, and its menus and settings on Other. A Siteglide store cannot be read yet, so Ecommerce says Coming soon. To skip some of the site's own files, untick them on Assets, each with a reason, and they are not copied. On the plan, check three things:
- The tables. Each module, web app and form has a table named the way the site names it (FAQ becomes
faq), with its fields named. - The pages that stay. A page that lists module items, takes a payment or uses eCommerce stays on Siteglide. The plan names each one and the call that kept it. Decide now whether you will rebuild it yourself.
- The forms. Each form a copied page shows is recreated with it, as a form in the Insites form builder. On Transform, Forms, check who each form's workflow email goes to: it starts with the staff Siteglide emailed. The autoresponder is made switched off.
4. Migrate
When the plan reads right, turn the dry run into a migration and confirm the load with the plan's code. The tool loads the tables, people, files, pages and forms, then checks every one: each row identical, each person present, each file the same size, and each copied page answering with the same words as the Siteglide page and loading nothing from Siteglide.
Open a copied page with a form on the new instance and send a test. The submission lands in the form's table, and the page goes where it went on Siteglide. The workflow email goes to whoever the Forms step names, so if that is still the client's staff, tell them first or change it while you test.
5. Work through the checklist
The To do list in Launch is written for this site, and each job sits in the step it is done in: Before cutover, Cutover or After cutover. The jobs most Siteglide sites have, in that order:
- Check the forms. The checklist names each form and who Siteglide's emails went to. Open each in the form builder, check its workflow email, read its autoresponder and switch it on.
- Filter the new address out of the site's analytics, if its pages carry Google Tag Manager or Analytics, until DNS moves.
- Add the site's domains to the new instance in Insites Console, taking them from the Siteglide Portal, and point their DNS at it once the editors have stopped and the final sync has run.
- Ask everyone with an account to set a new password. Siteglide does not give out passwords.
- Keep the Siteglide site until the 14-day watch ends. Then press Close the migration on the Close step of Launch and type the old site's address to confirm, make a new API key in the Siteglide Portal, and cancel the Siteglide plan.
If anything is wrong after the load, roll it back: the destination goes back to exactly what it held before.