In this guide, we will run you through the steps to migrate your data from Zephyr Enterprise to QMetry Test Management. This documentation enlists all the information on migration process like what can be migrated, and what are the assets/data that may not be migrated, features of the migration utility along with System Requirements, Pre-requisites and steps to be taken care before proceeding with migration.
Organization Code: Enter QMetry Organization Code, or leave it empty.
Step 3: Pre-requisite
Make sure you comply with the pre-requisite mentioned on the screen.
Step 4: Project Selection
Select the Zephyr Enterprise Project you would like to migrate into QMetry. Also select the QMetry Project Template to be used to create the project structure.
Step 5: Entity Mapping
Under this section, map your Zephyr Enterprise assets being migrated into relevant QMetry Assets.
Step 6: Custom Fields
You can select system fields and user-defined fields that are part of your Zephyr Enterprise project that needs to be migrated to QMetry.
NOTE: This is an important step to ensure there is no data loss when the project is migrated to QMetry. Make sure all the required fields are mapped correctly. Once migrated, the data cannot be reverted back.
Selected fields will be converted as custom fields in QMetry and will be auto mapped with the appropriate fields on the field mapping page.
Custom Field for Zephyr Enterprise Requirements
Custom Field for Zephyr Enterprise Test Case
Custom Field for Zephyr Enterprise Execution Cycle
Custom Field for Zephyr Enterprise Defect
Step 7: Field Mapping
Field mapping helps you to migrate the data from the fields of your Zephyr Enterprise assets to respective QMetry fields. Complete the field mapping for as many fields as possible to get their data migrated to QMetry. Fields can be mapped for Requirements, Test Case, Execution Cycle, and Defects.
Field Mapping for Zephyr Enterprise Requirements → QMetry Requirements
Field Mapping for Zephyr Enterprise Testcase → QMetry Test Cases
Field Mapping for Zephyr Enterprise Execution Cycle → QMetry Test Suite
Field Mapping for Zephyr Enterprise Defects → QMetry Issues
Step 8: Field Value Mapping
You can map the values of your different fields of Zephyr Enterprise to that of QMetry.
Migration Tool provides an option of "Add value" if user wants to create a new field value in QMetry same as Zephyr offers. To create the new values > Click on the checkbox beside the field value > Click on "Add value" button below > Now map the Zephyr field values to the newly created QMetry fields values.
NOTE: The Add Value option is not available for test execution values and test step execution values.
Field Value Mapping for Requirements
Field Value Mapping for Test Case (QMetry Test Cases)
Field Value Mapping of Execution Cycles (QMetry Test Suites)
Field Value Mapping for Defect The defects will be created in QMetry internal issue module.
Step 9. Migration
Click on the Migrate Button to start the migration process.
The migration progress can be monitored until it is completed.
Once the migration completes, you can log in to QMetry and verify all the migrated data in your given projects.
The migration utility is designed to support resuming the data migration from the same point in case an error is encountered due to data issues or other reasons. In such cases re-migrating the project is not necessary. At times when you run into errors, you can try to resume the migration after capturing the logs as follows.
Capture Migration Logs
The logs should be present in the logs folder of the migration utility directory containing the .war file. Zip the logs folder and send it to QMetry Support for investigation.
Resume the Migration
The migration can be resumed by refreshing the existing page and clicking "Resume" OR from the URL : http://<utility_url>/migrate2qtm/migration
Reverting API metering, Audit history logging and Email Notifications.
Once the projects have been migrated, or in cases when users would use QMetry and no projects would be migrated for significant amount of time, in those cases these changes should be reverted.