Cloud Migration FAQ

There is no certain method to calculate the time data migrations take. You need to be prepared for long hours of migration tasks. We urge you to test the migrations before committing to any timeline. Only a Test Migration will provide a good time estimation.

The duration of migration depends on many things:

To sum up, migrating a thousand entities should take a few hours, whereas a very large migration with thousands to millions of entities may take entire weekends or more.

We recommend that our customers do test migrations exhaustively before advancing to prod migration before committing to any timeline. If you have a large instance, please connect with our Cloud Migrations Manager to learn the best strategy to test the migration.

There are two methods to migrate the Zephyr Squad data from Server/Data Center to Cloud:

It is important to know the limitations on data migration, as not everything will be migrated. Ensure that you know what you will be missing and check the infrastructure requirements.

Yes, there are a few differences in the features. You must know the differences in the features, if you are moving from Jira Server to the Cloud version of Zephyr Squad. Please refer to the comparison matrixto understand the differences in detail.

The JCMA cannot migrate Zephyr-only data. The Zephyr data must be migrated together in the same migration plan as Jira’s data. You must select the Projects before starting Zephyr migration. The JCMA will only trigger Zephyr migration after Jira migration is finished for the selected projects in the migration plan.

If you forget to select Zephyr, you will need to delete the project and run a new migration plan for it with Zephyr selected. It’s not possible to migrate Zephyr for an existing Jira project.

The Zephyr Migration tool migrates all Zephyr Squad data, except for these entities:

Yes, all projects need to be migrated so dependencies can be resolved. We recommend our customers organize their migration plans considering that all projects must be finished before you can use them. It means that you may want to migrate larger projects in separated migration plans, to avoid delaying access to the other projects in the same migration plan.

No. Projects may have dependencies on each other, such as links. The links will be migrated in a broken state until the linked project is migrated. Once all dependent projects are migrated, the dependencies will be automatically fixed.

We recommend our customers organize their migration plans considering that all projects must be finished before you can use them. It means that you may want to migrate larger projects in separated migration plans, to avoid delaying access to the other projects in the same migration plan.

Both the JCMA and the Zephyr Migration tool will allow you to migrate project by project. The JCMA allows you to select multiple projects in the same migration plan.

Yes, you can run multiple JCMA migration tasks in parallel. Please note that it will affect Server performance and may result in dependency issues. All dependencies should be automatically fixed once all projects are migrated.

There is a global queue to process customer’s migration tasks using JCMA, and we estimate that one single customer will hardly be able to migrate more than 3 migration plans at the same time. This queue is first-in-first-out based, and we do not control who gets processed when.

If you are using the Zephyr Migration tool as your migration method, you can run multiple project migrations in parallel. However, please consider the Jira API calls limits. Please raise a support ticket or ask Atlassian to loop Zephyr’s Cloud Migration Manager to your Migration Support ticket for further assistance on running parallel migrations.

No, but if you complete the migration to Cloud before your Server license expires, we can offer a proportional discount for your new Cloud subscription. Please contact the Zephyr Sales team: [email protected].

No, but if you complete the migration to Cloud before your Server license expires, we can offer a proportional discount for your new Cloud subscription. Please contact the Zephyr Sales team: [email protected].

No, but if you complete the migration to Cloud before your Server license expires, we can offer a proportional discount for your new Cloud subscription. Please contact the Zephyr Sales team: [email protected].

If you already decided to purchase a Cloud subscription, please contact the Zephyr Sales team at: [email protected]. We will provide you with a promo code for your Server license so you can upgrade it and test the new version before the migration.

If you are not willing to purchase Cloud at this time, we recommend that you renew your Server maintenance so you can upgrade it and test the new version. Moving forward, if you end up migrating to Cloud before your Server license expires, we can offer a proportional discount for your new Cloud subscription.

This is not possible now. Atlassian is working to provide Cloud-to-Cloud migration support for apps in 2022. Please see Atlassian’s public roadmap for more information on when Cloud-to-Cloud migration will be available and support app migrations.

Yes, given that project keys will not conflict.

Zephyr Squad does not currently support linking data from different instances having either the same or different hosting types (Server/Data Center or Cloud). ). We only migrate web links.

If you need to clear the data of a previous migration attempt, the best practice is to clean up your cloud data by creating an XML backup from an empty Cloud site and re-importing it into the Cloud you need to clean.

You should not follow these instructions from Atlassian, as it will change Jira’s ID and likely cause errors with our migration engine.