Migrating

Migrating from Server to Cloud

We understand many of our customers are undergoing a shift from on-premises to Cloud instances of Jira given Atlassian announcement to end of life Server. To compare cloud migration methods, please visit this page by Atlassian Support.

The following methods can be used to migrate data to cloud:

The Jira Cloud Migration Assistant (JCMA): is a free Jira Server/DC app offered by Atlassian via the Marketplace. Once installed, you will be able to select what you want to move to your Cloud instance.
Site Import: this method can be used if you are looking to migrate more than 1000 users. Using this method you can create a backup to import everything from current instance to Cloud.

You will be able to migrate all the data for TeamRhythm including Saved Views, Issue Hierarchy and Card Configuration in User Story Map via Site Import and JCMA.

Retrospective data can be only migrated using JCMA using app versions 9.1.0 or later (on the origin Jira Server or Jira Data Center site).

Data related to retrospectives will not be migrated:

on app versions earlier than 9.1.0
for non-JCMA migrations such as using Site Import

Jira Cloud Migration Assistant

If you are using JCMA to migrate to your Cloud instance, you can use JCMA for migrating data for User Story Maps as well. Learn more about the compatibility of the Jira Cloud Migration Assistant.

What do you need?

JCMA can be used to migrate TeamRhythm data only under the following conditions:

You have Jira Administrator permission.
JCMA is installed in your Jira Server or Jira Data Center (DC) instance
The Easy Agile TeamRhythm on the Server/DC instance is updated to version 9.1.0 or later.
- While versions 7.4.0 and higher support migrating data for the User Story Map, Retrospective data is not migrated without version 9.1.0 or later.
Easy Agile TeamRhythm is installed in the Cloud instance.

Are you eligible for dual licensing? Learn more about it here.

We recommend always using the latest version of Easy Agile TeamRhythm when running migrations.

How does it work?

Follow the steps on how to use the Jira Cloud Migration Assistant to migrate TeamRhythm data to your Cloud instance. During the Assess your apps stage, status of Needed in Cloud should be assigned to User Story Maps to enable it for JCMA migration. Using JCMA, you will be able to migrate User Story Maps data related to Saved Views, Issue Hierarchy and Card Configuration.

As the migration occurs based on project selection, the data migrated for TeamRhythm will depend on the projects being migrated. Story maps data will only be migrated for the boards which belong to the Projects selected during migration. When migrating Story Maps where Issue Hierarchy is enabled, the project for Issue Hierarchy should be selected during the migration for migrating the issue hierarchy for the Story Map to Cloud instance.

Please note, JCMA currently does not support migrating references to quick filters

You can track the progress of the migration of TeamRhythm data by navigating to the Migration Assistant page.

Click on the Jira Administration cog in the top-right corner and select Manage Apps
Navigate to Easy Agile User Story Maps in the sidebar and click on Migration Assistant.

Here you can view the list of ongoing and past JCMA migrations and the number of saved views, issue hierarchies and card configurations migrated for the selected projects for each migration. Click on view log button to access detailed log regarding each migration.

Site Import

If you are using Jira Site Import to migrate to your Cloud instance, you can use Site Import for migrating data for TeamRhythm as well.

TeamRhythm Site Import can also be used for the following migrations:

Server to Data Center
Data Center to Server

Retrospective data is not currently included when migrating using Site Import.

What do you need?

Site Import can be used to migrate TeamRhythm data only under the following conditions:

Jira Site Import has been used to migrate Jira data
You must have Jira administrator permission
You must be on TeamRhythm version 7.3.0 or higher
Easy Agile TeamRhythm should be installed in the Cloud instance

Are you eligible for dual licensing? Learn more about it here.

We recommend always being on the latest version of Easy Agile TeamRhythm for performing migration.

How does it work?

After you have migrated your Jira data using Jira Site Import, you can start Site Import for TeamRhythm.

Site Import for TeamRhythm can be accessed via the Manage Apps admin page in Jira. You will be able to export a backup file consisting of User Story Maps data related to Saved Views, Issue Hierarchy and Card Configuration and then import this data into your Cloud instance.

Step 1: Jira Site Import

Ensure Jira migration has been completed via Jira Site Import.

Step 2: Back up your TeamRhythm Server data

Log in to your server instance using Jira administrator permission.
Click on the Jira Administration cog in the top-right corner and select Manage Apps.
Navigate to Easy Agile TeamRhythm in the sidebar and click on Site backup.
Click on Create backup button to start backup.
You will be able to see the progress of the backup on the screen.
Once the backup is complete, you will see a success message on the screen.
Click on Download Jira Backup to export the backup file.

Step 3: Import your TeamRhythm Server data into Cloud

Log in to your Cloud instance using Jira administrator permission
Click on the Jira Administration cog in the top-right corner and select Manage Apps
Navigate to Easy Agile TeamRhythm in the sidebar and click on Site restore.
Click on Choose file and select the backup file from Downloads.
Click on Restore data.
Once the import starts, you will be able to view the progress of the import on the screen
Once the import is complete, you will see a success message on the screen.

Migrating from Server to DC

You do not need to uninstall the Server version of Easy Agile TeamRhythm to migrate to Data Center. You are only required to swap out the license key.

Visit Atlassian’s documentation on migrating from Server to Data Center.

Migrating your license between Jira Server, Data Center or Cloud

As all Easy Agile licensing is handled via the Atlassian Marketplace, you will need to contact Atlassian about transferring your license. Note that licenses cannot be directly transferred or credited; however, you may be eligible for a free trial in order to make the transition process smoother.

To raise a Billing, Payments and Pricing request, contact Atlassian Support here.

FAQs

Can I migrate from a multi-node Data Center (DC) site?

There are currently some issues migrating from multi-node DC site which Atlassian are aware of. We hope to have a fix implemented for this limitation in the medium term.

If you encounter problems with JCMA migrations from a multi-node DC site, Atlassian suggest that users with multi-node DC instances using only one node as a workaround.

We are here for you!

If you have any questions or concerns about migrating to Jira Cloud, feel free to reach out to support@easyagile.com or via our Support Desk.

All Easy Agile apps are available on both Cloud and On-premises Jira instances. Wherever you are migrating, we are here to make it easy. For more information on our migration support, please visit our Migration Hub.