Summary

This page provides an overview of things you should consider when assessing and migrating your Zephyr Scale - Test Management for Jira app data to Cloud

General guidelines

• Test app migration early
  Testing app data migration late in your migration journey can lead to unforeseen delays and complications in your overall process. If your app data is essential for cloud functionality, it is advisable to conduct migration tests early, in tandem with your core Jira product migration planning.
  
  

• Communicate directly with your Marketplace Partner
  Contact and establish a communication channel with SmartBear (the Marketplace Partner/app vendor), who owns the Zephyr Scale app. 
  
  

• Refer to SmartBear’s documentation for 'Zephyr Scale' migration guidance.
  
  

• Check for Marketplace Partner updates
  You should check for scheduled maintenance or incidents on the Marketplace Partner’s platform that can impact app migration.
  
  

• Check for the level of support you can expect from the Marketplace Partner for migration. 

Planning the Zephyr Squad app migration

Estimating app migration time

Migrating the Zephyr Scale to the Cloud is usually a swift process. It is estimated that the migration can handle up to 50 million objects within just 48 hours. 

SmartBear believes that most customers can effectively migrate their on-premises data over a weekend. As a result, the Zephyr Scale does not include an estimation tool and does not necessitate any specialized assessment screening.

Consider cross-project dependencies

Zephyr Scale's key features enable users to establish various types of cross-project relationships for test-related data. For instance, users can add Test Cases from multiple Projects within a single Cycle, enhancing the flexibility and organization of their testing processes.

Migrating data from Server/DC to Cloud requires customers to include all dependent projects within the same migration plan. Failing to do so will result in an INCOMPLETE migration, as any objects linked to the omitted projects will be skipped during the process.

If you intend to execute multiple migration plans, it is essential to reach out to SmartBear and request a review of these dependencies.

Plan your test phase carefully

While time-to-process is not a concern, the Zephyr Scale requires thorough tests before the production migration date. SmartBear recommends that customers:

• Validate the primary QA processes in the Cloud.

• Ensure that the JCMA migration concludes with a 100% SUCCESS/COMPLETE rate. If you encounter an INCOMPLETE result, promptly raise a support ticket with SmartBear to identify the missing objects and determine the necessary steps to resolve the issues on the Server/DC side.

Please allocate sufficient time for potentially multiple rounds of testing to ensure that the data is thoroughly prepared for migration. If setting up a testing environment demands excessive effort, SmartBear suggests conducting tests on the Zephyr Scale independently to prevent unnecessary workload.

The Zephyr team is committed to assisting customers in rectifying data on the source as many times as necessary until the migration achieves a 100% success rate. This process will likely involve several rounds of test migrations.

Once your testing phase is successful and the dataset is validated, you should not encounter any further issues with your migration.

Review key points

Customers should carefully read and follow Zephyr Scale’s migration guide, paying special attention to:

• Minimum required version

• Increasing log levels for com.adaptavist, com.kanoah, and com.smartbear to INFO.

• What data gets migrated

• Review allowed domains