Migrating and JCMA
Easy Agile TeamRhythm data migrates with the Jira Cloud Migration Assistant (JCMA).
Migrating to Jira Cloud
We understand many of our customers are undergoing a shift from on-premise (Server and Data Center) to Jira Cloud following the Atlassian announcement of the end of support for Server. To compare Jira migration methods, please visit this page by Atlassian Support.
Easy Agile TeamRhythm integrates with JCMA, a free Jira Server / Data Center app offered by Atlassian on the Atlassian Marketplace.
When the app is included in a JCMA migration, app data for migrated Jira projects (including Saved Views, Issue Hierarchy and Card Configuration) will automatically be migrated.
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).
Migrating with the Jira Cloud Migration Assistant (JCMA)
If you are using JCMA to migrate to your Cloud instance, you can use JCMA for migrating data for Easy Agile TeamRhythm 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.
We recommend always using the latest version of Easy Agile TeamRhythm when running migrations.
Expired app license on Jira Server? You can still download the latest version of the app from the Atlassian Marketplace, and upload this to your Jira Server site.
The app will show an “Unlicensed” page when using a version your license does not include access to. However, the JCMA integration will still work without an eligible license.
Are you eligible for dual licensing? Learn more about it here.
How does it work?
Update the Easy Agile TeamRhythm and JCMA apps to the latest version.
During the Assess your apps stage, select “Needed in Cloud” for Easy Agile TeamRhythm.
Follow the steps on how to use the Jira Cloud Migration Assistant to migrate data to your Cloud instance.
App data associated with your migrated Jira data will be migrated as one of the last steps in the JCMA migration.
When running a JCMA migration, you’ll choose which Jira projects will be migrated. Easy Agile TeamRhythm will migrate all app data associated with the Jira data that is now on the Jira Cloud site.
For example, Retrospectives will be migrated when the Jira board they were created on (and sprint, if applicable) have been migrated.
When an additional level of hierarchy is configured for the User Story Map on a migrated Jira board, it can only be migrated when the other Project selected in that hierarchy has also been migrated.
Staged migrations
If you are planning a staged migration, we recommend enabling Easy Agile TeamRhythm for all migrations. This allows it to migrate the app data associated with the Jira projects in each migration. The app does not need a separate migration.
Including the app in more than one migration is safe. It will not create duplicates, or overwrite new Retrospectives.
Easy Agile TeamRhythm will migrate app data associated with any Jira data which can be found on the destination Jira Cloud site. This includes data from the current or previous migrations.
Limitations
JCMA currently does not support migrating references to Quick Filters.
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).
App data cannot be migrated if the associated Jira data is not found on the destination Jira Cloud site.
Logs
You can review the results of a migration of Easy Agile TeamRhythm data on the destination Jira Cloud site. This is available for Jira Administrators by navigating to:
Jira Cloud’s global settings → “Manage Apps”
Then, in the left navigation pane under “Easy Agile TeamRhythm” → “Migration Assistant”
Here, you can view the list of ongoing and past JCMA migrations. Click on “View Log” to access detailed logs for each migration.
Our support team may ask for a copy of these logs while troubleshooting a migration.
Cancelling a migration
As of 18 Jan 2024, customers have been able to initiate a cancellation of an app migration with version 1.10.10 of JCMA. This is currently not supported by Easy Agile TeamRhythm.
Site import [deprecated]
Earlier versions of Jira and Easy Agile TeamRhythm supported migrations using Site Import (or “Site Backup” / “Site Restore”). This was compatible ONLY with migrations where the Jira data was also migrated with Site Import.
As of November 2023, Atlassian has discontinued support for Site Import. This means that Jira and app data can no longer be migrated using this method. App pages “Site backup” and “Site restore” will be removed accordingly.
Migrating Easy Agile TeamRhythm app data using site import is NOT compatible with any other migration paths.
Migrating from Server to Data Center
You do not need to uninstall the Server version of Easy Agile TeamRhythm to migrate to Data Center. If you are upgrading your existing Jira Server site to Jira Data Center, you are only required to swap the license key used for the app.
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 sites 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 suggests running the migration 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.