Migration from On-Premises to Relution Cloud
Introduction
Relution installations can be easily transferred to the Relution Cloud. Only a few steps and specific configurations are necessary for a successful migration.
Requirements
The following components are required for migration to the Relution Cloud: A current dump of the Relution database The S3 storage bucket, if used in the existing on-premises installation Both components are provided in the cloud by the Relution infrastructure team.
Important: The URL of the Relution instance used previously must continue to point to the new cloud instance after migration – usually by means of a DNS CNAME entry to the new target address (e.g. customer name.relution.io).
Implementation
Relution Support should always be contacted before migration. If the migration has already been requested, the support team will usually have a corresponding ticket on file, allowing them to provide targeted assistance during the process. First, an SQL dump of the current database is created and provided to Relution Support. The new cloud instance is then set up and the database imported. The duration depends on the size of the database and can take several hours. During or after the import, the DNS CNAME entry is configured: The previous URL (e.g. relution.customername.co.uk) then points to the new Relution Cloud instance (e.g. customername.relution.io). Note The end devices do not need to be re-registered after the migration. Operations continue without interruption – all MDM profiles, apps and certificates are retained.
Summary: Steps for migration
- Contact Relution Support
- Schedule an appointment for backup and migration
- Provide the database (and S3 bucket, if applicable) in coordination with Support
- Configure the DNS CNAME entry for the new cloud instance