Zephyr Squad Migration Guide
Introduction
Over the last few months, we received many requests from clients to upgrade from Zephyr Squad to Zephyr . As of today, this is not a native capability we provide, and upgrading to Zephyr requires implementing scripts that rely on the Zephyr Squad and APIs. To address this issue, we are currently working on a native built-in solution that enables to automatically upgrade from Zephyr Squad to Zephyr.
You will find all the necessary information below and the related sub-sections to make sure that you have all the information needed to:
understand when the solution will be available
identify the additional features from Zephyr
identify the Zephyr Squad features that will not be part of Zephyr
identify the data lost and transformed during the upgrade
understand the impact on pricing and existing license
estimate time and effort required to upgrade
High-level Roadmap
Our team is currently working on a solution to upgrade from Zephyr Squad to Zephyr. The first solution will only be available for an upgrade on our cloud versions.
If you are looking for a Squad Server to Zephyr upgrade, please reach out to our support team.
If you are evaluating the opportunity to make a Squad to Zephyr upgrade, please refer to the following pages to identify the current feature gaps and the data that is not migrated. This will ensure you have all the necessary information.
The registration for our beta program is open. It will be open until beta release of Self-serve migration.
Click here to register for the beta program.
The migration beta interface is now available for selected customers. You can start the migration process using this interface. However, it doesn't support the project selection yet. If you need to migrate specific projects, use the REST APIs.Our support and engineering teams will assist with the migrations. We'll first reach out to selected customers to confirm they're ready to start migrating to Zephyr. In this version, we'll transfer test cases, test cycles, and test executions. BDD data won't be included, so it will be lost.
Also, you won't be able to transfer extra data using the upgrade engine after the migration.
All of the supported data except the BDD test cases and BDD test executions are migrated. Check the detailed Data Transfer page to see what data is migrated.
The feature of execution history does not exist on Zephyr, so cannot be migrated.
Note
All information by or on this site is provided for informational purposes only and is not to be relied upon so for purchasing or planning purposes. The roadmap is subject to change or delay. The development, release, and timing remain dependent on these changes or delays.
Pricing/Licensing
Zephyr Squad and Zephyr licenses are not interchangeable. Thus, you must buy a new Zephyr license for your Jira instance when you upgrade. If there are more than six months left to run on the Zephyr Squad for Jira Cloud subscription, a pro-rata discount is available on request. The discount is in the form of a promo code which you can use to apply a discount on the new Zephyr subscription. You can let the Zephyr Squad license expire.
During the upgrade/UAT phase, we can arrange for dual licensing upon request. We provide a limited free license if you have a paid or commercial license in place. If you have any questions about licenses, feel free to email [email protected]
Time and Efforts Required to Upgrade
To shorten the upgrade process, you can upload attachments to Zephyr Storage before the upgrade. It can take a few days or weeks depending on their size. You can migrate any attachments during the upgrade process even if you didn’t upload them toZephyr Storage earlier.
We don’t recommend using Squad projects during the upgrade to avoid data inconsistencies. If the upgrade fails, you can run it again. However, it will overwrite the transferred data. We do not support delta transfer of objects created after the upgrade.
In the beta stage, you should use the REST APIs to manage the upgrade process
Note:The REST API endpoints are different for Zephyr. If you are doing automation, you need to update your automation scripts with the new endpoints.
You cannot cancel or stop a running upgrade until it is in a completed state. A completed state would mean that upgrade finished or failed.
Register for Beta Program
The registration for our beta program is open.
Click here to register for the beta program.
Should you have any questions, please reach out to our Support team.