We are currently creating a migration utility that you can use to move your risk data from Server to Cloud. This should be available within a few months, and we advise clients to wait for it.
For those who cannot wait, it is possible to migrate the data manually. Because of significant differences in the underlying technical platforms, risk information is stored differently in the Cloud version and the Server version. This difference complicates the migration process.
The following process must be followed. The process is reasonably involved, and is only recommended if you have a) more than 200 risk issues, and b) someone with script programming experience.
Migrate all risk issues using Jira's built-in migration utilities. See Use Jira Site Import to migrate from server to cloud.
Manually adjust the risk model in the Cloud to your liking. Note that the Cloud version of the product enables only one risk model for the entire server, whereas the Server version allows different risk models for different projects. See Administering the Risk Register Application.
Export the values of the impact and probability fields, both inherent and residual, and import them into custom fields in your cloud instance.
Create a script that creates an entity property for each risk issue, based on the values of the impact and probability fields you imported in step 3. See here for details of the entity property.
Remove now-redundant custom fields. See Edit or delete a custom field.
It’s possible that you defined a screen schema specific for risk issues on the server. If so, it’s important that you migrate that schema over to the cloud and point your risk screens at it. See Associating screen and issue operation mappings with an issue type.
On the server version, when you set the status of a risk to “closed” it no longer appears on the risk matrix and risk register. The cloud version behaves differently. In order to remove a risk from the matrix and register you must set the resolution field with a value (which can be anything).
The best way to preserve the server behavior on the cloud is to set up a function that assigns a value to the resolution field whenever the issue moves to the closed status. See Advanced workflow configuration.