Important notice:

The app data migration via Jira Cloud Migration Assistant (JCMA) is in public beta to all users.
For more information about Atlassian’s app migration timelines, visit their blog and Cloud Roadmap.

What data gets migrated

When migrating the Zephyr Scale Server data to Cloud using JCMA, some things are not migrated because the Cloud version lacks the corresponding features. Some of these features may be implemented in the future, most of them most probably won’t be, but then we could add them to the migration.

What is migrated

What is NOT migrated

Projects (the project itself, whether permissions are enabled in the project, whether Zephyr Scale is enabled, what issue types are disabled in the project)
Permissions
Priorities (including custom priorities, although you cannot create custom priorities on Cloud currently)
Statuses
Folders
Labels (and the relationships between labels to entities so you see the correct labels on each entity)
Environments
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)
Change history
Rich text attachments (for all fields where rich text attachments are usable)
Attachments

Note about attachments: Even though the Cloud version does not currently support attachments for test steps and test cycles, they are still migrated, but will not be displayed in the Cloud just yet. When support for attachments is added to Cloud in the future, all migrated steps and cycles will have the attachments they had in the Server version, even if you migrate before this feature is available.

Analytics settings
Automatic traceability links
Filters
Folder custom fields
Global access restrictions
Iterations
Project restrictions
Show/Hide traceability sections
Test case, cycle, and plan comments
Thresholds
Traceability to Confluence pages

Pre-migration steps

In Jira Server

Upgrade Zephyr Scale Server to at least version 8.6.1 (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:
  
  Click the image to enlarge it.
  
  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.

Begin the migration

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 documentation:

Use the Jira Cloud Migration Assistant to migrate

Click the image to enlarge it.

Track migration progress

Because the JCMA is still in beta, its progress feedback might take around 10 minutes to be updated. It is possible (and common) that the progress will jump from 0% to 100%. If you do not see the progress moving, wait for 10 minutes and see if it is still stuck.

We expect that progress tracking will be improved when the JCMA hits General Availability in 2022.

Make sure to wait until the migration completes (the status must be Complete):

Click the image to enlarge it.

You can watch your Jira Server’s atlassian-jira.log file for errors during the migration. More detailed information about the export process can be obtained by increasing the log level for com.adaptavist to INFO.

Migration status

The possible statuses are:

Status	Description	Action required
RUNNING	Zephyr Scale data migration is in progress.	Monitor the progress updates you receive and wait for the process to change the status. If more than 10 minutes have passed and you do not see an update, contact Zephyr Scale Support.
COMPLETE	The process has completed successfully, and all data was migrated.	Review your new cloud project to validate the migration.
INCOMPLETE	The process has completed, but some data was excluded from the migration due to validation problems.	Review the log file that is provided to understand what data was excluded and why. Sometimes data will be skipped for valid reasons, such as traceability that references Jira issues that no longer exist, or attachments which reference files that no longer exist. If there is any doubt about the entities that have been skipped, contact Zephyr Scale Support.
FAILED	The migration process was interrupted due to an unexpected error, and the execution of the migration was stopped at that point. There will be data missing from the migration as the rest of the process was aborted.	Please review the log file provided and contact Zephyr Scale Support for further investigation.

FAQ

See our Cloud Migration FAQ for quick answers to some commonly asked questions.

Support and troubleshooting

Should you have any questions, please visit our Support Portal where you can search for an answer in Zephyr Scale Community or contact our Customer Care team.

Zephyr Scale Server-to-Cloud Migration Guide