AIO Tests- Jira Cloud Migration Assistant (JCMA)
AIO Tests allows Jira Server and Data Center users to move their data to Jira Cloud using the AIO Tests JCMA feature.
Recommendation:
Before doing data migration in Production, please perform at least 1 or 2 migrations on a test instance and verify your data. In case of any issues, please reach out to mailto:help@aiotests.com or open a ticket in our support portal.
Please ensure you are on the latest version of AIO Tests.
You should migrate all the needed projects from Jira DC/Server to Cloud first before starting AIO data migration. This will ensure that there are no broken links in Cases/Sets/Cycles, etc.
The migration process will transfer all the data for Cases, Cycles, Sets, and Runs along with attachments, requirement links, and defect links.
Any existing AIO Tests data on the Cloud (destination instance) will be deleted and overridden with the data from the Server/DC (source instance).
To to ensure JCMA runs correctly and migrates AIO Tests data, verify you have the correct Cloud and Data Center versions of AIO Tests. See the table below for compatibility details
We highly recommend that you are on the latest and compatible versions on both DC and Cloud
Click here to know how to check which AIO Tests Cloud version you have.
AIO Tests Cloud Version | Compatible AIO Tests Data Center Version |
|---|---|
AIO Tests Cloud Version 2.3.0 (Connect app) | 4.9.1.3.10 |
Version 3.0.0 & above (Forge app) | 4.9.1.4 & above |
If at any point, you feel that the AIO Tests migration is stuck, please reach out to support and provide migration logs. You can also reach out to us to monitor your migration. (help@aiotests.com)
Please note the following items will not be migrated as part of the move:
Saved Reports: Users will need to setup their saved reports in the Cloud again.
Saved Filters: Users will need to create new saved filters in the Cloud.
Sharing of Reports: The reports that have been shared will lose the sharing information and will need to be shared on the Cloud.
Dashboards: Existing dashboards won’t be migrated.
Jira Custom Fields: Custom fields that have been created and mapped with any single-select Jira field will not be migrated along with its data.
History Section: The history tab on Cases will be empty once cases are migrated.
If certain projects are not migrated from the Server to the Cloud then the following issues will be observed:
Cases with linked steps belonging to non-migrated projects will error out.
Sets/cycles containing cases of non-migrated projects will error out.
Cases/cycles that have defects linked from non-migrated projects will error out.
AIO Tests Defect Creation preferences (General Preferences):
The settings done for Custom Fields will not be migrated. Users are requested to review their General Preferences section.
Check Cloud AIO Tests version
For further queries and suggestions, feel free to reach out to our customer support via help@aiotests.com.