If you use on-premises, then you have the opportunity to migrate to the cloud through us. How the steps of migration work, what we migrate, and all details can be found in this article.
Migration to the Haiilo cloud is only possible from the current on-premise version 42, and a return to on-premise is not possible afterward.
Steps of a cloud migration
Contact
Please contact us through your account management contact if you are interested in a migration and if you do not have a direct account management contact, you can alternatively submit a ticket directly through our service desk.
Ticket & preparation call
We will create a ticket via our service desk for you and us, in which we will track and plan the entire migration. There we will also schedule a joint preparation meeting between your technical contact, our technician and a contact from our Customer Success Team. In this meeting, we will go over the individual details and initial questions regarding your migration.
Requirements & preparation
The most important thing is which Haiilo version you are currently on and how much memory your Haiilo occupies. Your Haiilo must be at least on version 42.4.0. and depending on the memory size, the migration time may be longer. If you cannot update to this version yourself, one of our partners can do it for you.
Furthermore, the following conditions must be created for our technicians:
- our technician has access via SSH to the current Haiilo server already from one day before a migration
- the current Haiilo server has access to the Internet
- a local access including password for us has been created in your Haiilo
Before the migrations, we recommend that you test external connections for authentication (SSO) and user provisioning (LDAP) in a demo instance. We will provide you with this instance if required during the planning process. In addition, you should already think about which Haiilo URL (*.coyocloud.com) you would like to have afterwards. We can reserve this accordingly if it is not already taken.
Test migration & productive migration
In total, we will perform two migrations. In both migrations we will take your productive data, but once we will migrate it into a test environment and once into your new productive environment of the cloud. The test migration serves on one hand to identify possible issues of your Haiilo and on the other hand to give you time to check your external connections with the Haiilo cloud infrastructure on your own before the productive migration.
Duration & Downtime
We need two working days for both migrations, whereby only the productive migration will cause a downtime for your users. Please communicate this internally accordingly.
Please note that after the migration you may have to change your external connections for Haiilo to work in the cloud. During these changes, users may not be able to log in to the migrated Haiilo.
Procedure - test migration
On the day of the test migration, we will access your current server via SSH and export the required data to our test infrastructure. This is not connected with any downtime of your Haiilo and will usually not be noticed by you. When we are done with the test migration, we will inform you with the URL and you can test your external connections in this test environment before your productive migration.
Procedure - productive migration
On the day of the productive migration we will access your current server via SSH and export the required data to our test infrastructure. This is connected with a downtime of your Haiilo, which you should announce internally to your users, so that there is a delta between the data at the end. When we are done with this, you will be notified again with the URL and can set up your external connections. The old Haiilo including server you leave from then on stopped and switched off, because only the Haiilo in the cloud should be used.
What will be migrated?
| Content | All contents of your Haiilo (except own translations via API) remain after the migration. |
| Customizing | We do not take over customizings. Please remove them beforehand so that we can perform the migrations accordingly. Otherwise, we will have to cancel the migration. |
| Links | We will perform an adjustment of internal links to the new URL via the database. This refers to links of widgets (e.g. buttons) and texts of articles. An adjustment of e.g. posts on the timeline or home page links is not possible. We cannot guarantee that all links have been replaced without exception. |
What changes after the Cloud Migration?
| URL |
You should inform your employees and colleagues that during the productive migration your Haiilo will be unavailable from 9am and that you will have a new URL (*.coyocloud.com) afterwards. If you are interested in continuing to use your old domain, you can order the custom domain add-on from us. Ask for it directly at the planning stage. |
|
Maintenance work/ updates |
Via the status page we inform you in time about version updates or about the current state of the Haiilo Cloud. We therefore recommend subscribing to the page. You will then receive automated emails when version updates, maintenance work and other information are announced. |
| Version | All users of the Haiilo Cloud are always on the latest Haiilo version. You no longer have any manual effort on your end. |