We strongly urge our customers to NOT migrate using the Jira Cloud Migration Assistant (JCMA) until Atlassian enables it for app migrations later in 2021. The JCMA does not enable app migrations at this time.
We are currently working with Atlassian to release beta support for this tool for Zephyr Scale, and you can follow along the progress and sign up for the Early Access Program via Atlassian’s migration platform ticket.
The JCMA steps outlined below are for EAP members only.
Supporting your journey to Cloud
Atlassian’s shift in strategy to become a cloud-first company has accelerated the journey to cloud with next-level offerings. On this journey, customers will start migrating their Jira instances and Apps from Server to Cloud (or Data Center) later in 2021 when Atlassian updates the Jira Cloud Migration Assistant with support for Jira apps.
At SmartBear, we are committed to facilitate a smooth transition to all our customers as the Server end-of-life date approaches on February 2nd, 2024. We have created a guide that will help you plan your migration. You will be able to migrate your instance and your Zephyr app data once Atlassian makes JCMA generally available later in 2021.
In Jira Server
Upgrade Zephyr Scale Server to at least version 8.4.3 (this is the minimum recommended version for JCMA migration).
Back up the data of your server instance.
Install the Jira Cloud Migration Assistant plugin in your Jira Server or Data Center instance.
Note: If you are using Jira version 8.14, the migration assistant is automatically installed in your server instance.
To install the plugin manually:
In Jira Server or Data Center, go to Settings > Manage apps.
Choose Find new apps in the sidebar.
Enter Jira Cloud Migration Assistant in the search bar.
Once the plugin is found, click Install:
Alternatively, you can install it from the Atlassian Marketplace.
In Jira Cloud
Install Zephyr Scale Cloud in your Jira Cloud instance.
If you are already using Zephyr Scale Cloud and it has projects with the same name or project key as Zephyr Scale Server projects, delete those projects from Zephyr Scale Cloud.
To start migrating your projects, users, and groups, navigate to Settings > System > Migrate to cloud in your Jira Server instance and follow the steps described in the Atlassian Jira documentation:
Make sure to wait until the migration completes (the status must be Complete):
Now you can open your project in Zephyr Scale Cloud and validate the migrated data. If no issues are found, you can start working with your project.
First, let’s start the limitation of data migration for Zephyr Scale. This is what would be and what would not be migrated in Zephyr Scale.
What data is mgirated:
- Projects (the project itself, whether permissions are enabled on the project, whether Zephyr Scale is enabled, what issue types are disabled on the project)
- Priorities (including custom priorities, although you can’t create custom priorities on Cloud currently)
- Labels (and the relationships between labels to entities, so you see the correct labels on each entity)
- Datasets (and the options within a dataset)
- Test Cases (along with the test script, and the steps if it’s a step by step test case)
- Test Data
- Test Case Parameters (and the values passed via call to test)
- Test Plans
- Test Cycles
- Test Executions (and steps within test executions)
- Traceability (issue links and weblinks)
- Custom fields (and the options within single choice or multi-choice select list custom fields)
- Custom field values (the values in all of the entities)
- Rich Text Attachments (for all fields where rich text attachments are usable)
- Attachments (including test cycle attachments despite not having this feature on Cloud yet)
- Change History
What data is NOT mgirated:
- Analytics settings
- Automatic traceability links
- Folders custom fields
- Global access restrictions
- Project restrictions
- Show/Hide traceability sections
- Test Case / Cycle / Plan comments
- Traceability to Confluence pages
All of the above are not supported due to the lack of features on Cloud. Some of these may be implemented, most of them most likely won’t be, but then we could add them to the migration.