Migrations to the COYO Cloud are possible from all on-premises versions. A return to On-Premises is not possible.
In advance, an appointment to exchange additional questions, scheduling and handover of contact information is advisable.
A technical contact and their contact information (email address and phone number) must be defined.
It must be checked whether the COYO Cloud can be reached from your internal network without restrictions, e.g. through a firewall or proxy. A list of IP addresses can be found in our Knowledge Base.
Before the migration date, it is recommended to successfully test external connections for authentication (SSO) and user provisioning (LDAP) in a demo instance.
The duration of the whole process depends on the data size of the COYO tenant and the speed of the transfer. About 90% of the data consists of the filestore of MongoDB and contains all documents of your COYO.
For an export of ~400GB we expect a downtime of 2 business days.Duration
URL / Accessibility
The customer should inform its employees and colleagues that there will be a downtime of the platform during which it cannot be used and point out the new URL (subdomain.coyocloud.com).
The new subdomain of the URL will be chosen by the customer if it is still available.
It is not possible to take over an existing URL. Forwarding the old URL to the new one is a common workaround. It is up to the customer to set up such a forwarding.
If the COYO Cloud is not available, a status page informs about the current status of the COYO Cloud.
Updates of the status can be subscribed via email, these are sent in case of announcements about version updates, maintenance work and other information.
All users of COYO Cloud are on the current version. It is not possible to select it. Information about backups in our cloud, you can find here.
All contents remain.
Optionally, we can perform an adjustment of internal links to the new URL via the database. This refers to contents of widgets, e.g. buttons and texts of articles. An adjustment of posts on the timeline is not possible. There is no guarantee that all links have been exchanged.