Unsupported migration pathways for TeamRhythm
If you migrate using a different method, app-specific data will be lost.
Unsupported migration methods
Atlassian-supported methods
Atlassian provides some methods other than JCMA to migrate Jira data. However, Easy Agile TeamRhythm cannot integrate with these migration methods at this time.
Copy product data (previously “Jira cloud-to-cloud migration”) is Atlassian’s pathway for migrating from one Jira Cloud site to another Jira Cloud site. Apps and app data cannot yet be migrated with Copy product data.
Migrating from Jira Cloud to Data Center has limited support, and app data is not migrated.
Site import [discontinued]
Site import was previously an option for migrating Jira data. Atlassian discontinued this functionality in late 2023.
Easy Agile TeamRhythm’s integration for Site import is not compatible with other Jira migration methods.
You may still see Easy Agile TeamRhythm’s “Site backup” and “Site restore” pages in Jira’s “Manage apps” settings. However, these are no longer applicable now that Atlassian has discontinued Site import.
Site backup is deprecated and is not a supported method of exporting app data.
Retrospective data cannot be exported using Site backup.
Third-party migration apps
Easy Agile apps do not integrate with other third-party apps for migration.
This includes:
These tools will migrate Jira data, but not Easy Agile app data.
Data lost if app data is not migrated
Some parts of Easy Agile TeamRhythm will still function as expected after migration, even if only the Jira data is migrated:
The User story map page uses epics and issues from your Jira board. After migrating your Jira data, the app will display the same User story map using the migrated Jira issues.
Optional configuration for the User story map view is app-specific data, and will be lost if you migrate only your Jira data: Saved Views, Additional issue hierarchy (above epic-level), and Card Configuration
Data on the Retrospective page is not Jira data, and will be lost if you migrate only your Jira data.
Action items converted to Jira issues will be migrated with your Jira data, but will no longer be connected to any Retrospective data.
Planning poker votes will be lost when migrating only Jira data. However, any estimates copied to the “Story points” field on the issue will be migrated with the Jira issue data.
Migrations with custom scripts
In some situations, it may be possible to migrate app data by developing custom scripts. Since this requires access to the Jira database, it is only possible when both the origin and destination Jira sites are on-premise (Jira Data Center / Jira Server).
This may apply when merging multiple Data Center / Server instances.
App data for Easy Agile TeamRhythm on Jira Data Center/Server is stored in additional tables in the existing Jira database. The names of the app’s tables begin with "AO_D4FD13_".
Easy Agile does not provide custom migration/scripting services and cannot guarantee data integrity during custom migrations. We can help you understand the scope and structure of app data to migrate based on your app version.
An Atlassian Solution Partner may be able to assist with custom migrations.
Technical challenges when migrating
Easy Agile apps uses Jira ID numbers to connect app data with the associated Jira data (e.g. Retrospective data with the Jira board). When Jira data is migrated from one site to another, the ID numbers of the Jira data change (e.g. issue ID, board ID). As a result, migrating app data along with Jira data requires mapping or “translating” the Jira ID numbers that the app uses.
Atlassian’s JCMA tool provides ID mapping for this purpose. This enables us to build an integration with JCMA to migrate app data alongside JCMA-migrated Jira data. Without this ID mapping integration point, it isn’t possible for Easy Agile apps to automate app migrations with other tools.
App data tables reference each other using foreign key constraints. It’s important to import table data in the correct order to maintain this constraint by importing each “parent” table before its “child” table(s).
For example, each row in "AO_D4FD13_RETRO_ITEM" references a "AO_D4FD13_RETRO"."ID". The "AO_D4FD13_RETRO" data must be imported first.
If the destination Jira site already has Easy Agile TeamRhythm app data, there is a risk that the ID numbers of the existing/imported app data may overlap. To handle this, imported data needs updated ID numbers.
For example, the "AO_D4FD13_RETRO"."ID" values typically start at 1 and are automatically incremented for each new row. Imported data needs to not re-use the ID numbers already in use.
If you’re planning a custom migration or have any questions about migrating Easy Agile TeamRhythm app data, let us know!