QTM4J Server/DC 4x To QTM4J Cloud 4x Migration via JCMA
This document is intended for users who are on the QTM4J 4.x interface Jira server hosting. Users, who are still using the QTM4J 3.x interface, should migrate their QTM4J to 4.x interface before following this document. They can verify their interface from the QMetry > About screen.
Notes:
Migration with JCMA is supported only on QTM4J Server v4.6.0 onwards.
We recommend running a test migration on a sandbox or lower environment of cloud Jira before performing the actual production migration.
The storage limit applies to production instances. Prior to migration, please consult your Account Manager (sales@qmetry.com) regarding the storage limit and whether there's a necessity to increase it based on the size of data and attachments in your server QMetry instance. It's important to note that exceeding the storage limit won't halt or fail the migration process. However, after migration users will be unable to create/update data or upload new attachments from the UI.
Considerations for Successful Migration
Please be aware of the following aspects while planning your migration.
Cross-Project Linkages: If your QTM4J Data contains cross-project linkages or references, it is crucial to include all relevant projects in a single migration plan. Migrating projects partially will not maintain cross-project linkages.
For example, you have the following projects:
Project A
Test Cycle 1
Linked Test Case 1 [Project B]
Project B
Test Case 1
In this case, it is essential to include both Project A and Project B in a single migration plan to maintain these cross-project linkages.
Migration Plan Options: Please be aware of the following limitations while planning your migration.
In the Migration options screen, the first option Migrate all data at once is not supported. Instead, you must select all projects manually in the second option.
In the second option Choose what to migrate, the “Attachments only” option, migrates only Jira Attachments.
QTM4J attachments and data will be migrated with the “All Project Data” option.
Pre-migration Steps
In Jira Server
Pre-Migration Checklist: Prior to beginning the migration, adhere to the pre-migration checklist recommended by Atlassian support. Ensure that your Jira Server instance is prepared for a smooth transition.
Confirm that the latest version of the Jira Cloud Migration Assistant App is installed on your Jira Server instance.
Confirm the QTM4J app interface, if you are already in the 4x interface then you can skip this step.
If you are using a 3x interface, you need to first migrate your app from 3x to 4x interface.
Ensure Storage Space, A minimum of 10 GB is available for the data export process of QTM4J.
Set Debug Level Logging: To enhance troubleshooting and diagnosing any potential issues that may arise during the migration, Enable the debug level log for “com.qmetry”.
In Jira Cloud
QTM4J App Installation: Ensure that the QTM4J App (QMetry Test Management for Jira) is installed on your target Jira Cloud instance.
Project Check: Before migrating, verify that the projects you are going to migrate do not already exist in your target Jira Cloud instance. To prevent conflicts, ensure that project names and keys are unique.
Backup Your Jira Cloud Instance: Create an XML backup of your Jira Cloud instance. of your empty Jira Cloud instance in case, you need to reset it. This backup will serve as a safeguard in case you need to revert to the previous state or perform a rollback.
What data gets migrated?
What is migrated | What isn't migrated |
Configuration | Test Reports |
Test Case | Gadgets |
Test Cycle | Filters |
Test Plan | BDD configuration and its linkage with stories |
Test Step | System Fields |
Folders |
|
Mappings |
|
Executions |
|
Automation Data |
|
Exploratory Testing Sessions |
|
Attachments |
|
Audit Logs |
|
Migration Steps
1. Navigate to Jira Administration > System > Migrate to Cloud in your Jira Server and follow the steps provided in Atlassian's JCMA documentation.
2. Ensure that the QTM4J app and relevant Jira projects are included in the same migration plan, as shown in the image below.
3. Save and run your migration plan. Jira data will be migrated first, followed by QTM4J App data.
4. Monitor the migration progress and wait for some time to complete it.
The status turns COMPLETE once the migration is completed successfully,
Migration progress statuses
Status | Description | Next steps |
RUNNING | QTM4J app data migration is in progress. | Monitor the progress and wait for the next updates. If you do not see any updates within an hour, contact QTM4J Support. |
COMPLETE | The migration is completed successfully, and all data has been migrated to your Cloud instance. | Verify the migrated data by reviewing your Cloud projects. If you notice any discrepancies, contact QTM4J Support. |
INCOMPLETE | The migration could not start due to failed validations. | Please review the validation error message, take appropriate action, and then re-run the migration. Contact QTM4J Support for any further queries. |
FAILED | The migration failed due to an unexpected event, leading to its termination. | Please review the generated log files and contact QTM4J support for further investigation. |