CLOUD | DATA CENTER AND SERVER
Migration Path from Data Center to Cloud
Overview
Requirements in easeRequirements are, at the bottom, Jira issues. So when you migrate your Jira Data Center instance to a Jira Cloud instance, you have thereby also migrated your requirements - albeit without the extra data created by easeRequirements.
easeRequirements data can be migrated using Atlassian’s official Jira Data Center to Cloud migration path. During this process, Jira issues — which underlie easeRequirements — are moved to your Jira Cloud instance, and compatible easeRequirements data is transferred alongside them according to Atlassian’s app migration framework.
The following sections explain which data can be migrated and the different migration methods, as well as which data can be recreated by hand.
What easeRequirements data can be migrated or recreated by hand?
Data | Can be migrated by the JCMA tool? | Can be recreated by the self-service method? | Comment |
|---|---|---|---|
Project Tree |
| Project tree data, including folders (folder name, description and attachments), can be completely migrated using one of the methods described below. References to Confluence pages in project trees cannot be migrated. | |
Coverage | Only public Coverage views can be automatically migrated to the cloud. Private views of users needs to be manually created in the cloud. | ||
Traceability | Only public Traceability views can be automatically migrated to the cloud. Private views of users needs to be manually created in the cloud. | ||
Baselines | Baseline data can be migrated with a few limitations:
Due to differences in storing data in DC and Cloud, some migrated baselines in cloud are not 100% the same as in DC. | ||
Administration configuration | All cloud related configurations are migrated. | ||
Export templates | Cloud template uploads have size limits. Check your cloud instance for the maximum data allowed. Not all features of the template language are as yet supported in Cloud, so export templates should be reviewed and possibly modified to work as expected. See the items labeled Data Center only in Context Item Types, Expressions and Statements. |
Migration Methods
Automated Migration via JCMA
We strongly recommend that you first verify the final migration using a test instance of Jira Cloud.
Prerequisites
Before migrating, check the following.
easeRequirements Data Center version 5.4 is installed.
easeRequirements Cloud is installed.
Folder Issue Type is configured in Cloud. Refer to Configuration | Specify Folder Issue Type .
The correct server location and API token are configured in Data Center. Refer to Configuration.
Configuring the wrong server location or invalid API token will result to general warnings in pre-migration app checks.Identified the list of projects using easeRequirements functions in Data Center.
Include all projects to the migration which have issues included in a project tree or baseline.
The list can include projects which are not activated.
The migration tool will highlight missing projects.
Skipping these projects may lead to inconsistent tree migration or baselines missing certain issues.
To know more about this migration path and how to use it, refer to Atlassian’s official documentation to perform this migration.
Existing data of the selected projects in easeRequirements Cloud (like tree structures, coverage views, baselines) will be overwritten.
Self-service using ReqIF Files
Only use if the installed Data Center version is lower than 5.4.
With this method, you export the desired projects in the Jira DC instance to exchange files and then import these files into the Jira Cloud instance. The files are formatted in the Requirements Interchange Format Specification (REQIF).
In the DC instance, you first export project trees. The ReqIF files generated here will be used to import the structures to easeRequirements Cloud.
In your Cloud instance, you then import the exported trees.
For a full description of the migration process, see How to migrate from Jira Data Center to Jira Cloud using ReqIF.
Self-service using Python scripts and REST APIs
This method is suited for advanced users with programming knowledge. We provide an open-source Python script that illustrates the use of APIs to migrate easeRequirements trees - see https://github.com/easesolutions/r4j-cloud-api-samples. The readme file provides all the needed information to run the script.
Please note we cannot provide any support or warranties for the use of this method.
Professional Services
To minimize effort and reduce risks, you can have us perform the entire migration. Please contact our support team for more information.
Once the migration is complete, please review the easeRequirements data in your Cloud site to confirm everything is working as expected. If you experience any issues or have questions about the migration, please submit a ticket in our support portal.