Unsupported migration pathways for Easy Agile Roadmaps

The only supported/automated pathway for migrating Easy Agile TeamRhythm app data between Jira sites is the Jira Cloud Migration Assistant (JCMA).

If you migrate using a different method, app-specific data will be lost.

If you’re upgrading your existing Jira Server site to Jira Data Center, you won’t need to migrate data.

Unsupported migration methods

Atlassian-supported methods

Atlassian provides some methods other than JCMA to migrate Jira data. However, Easy Agile Roadmaps 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] was previously an option for migrating Jira data. Atlassian discontinued this functionality in late 2023.

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

App data is only automatically migrated with JCMA.

If you migrate Jira data without migrating Easy Agile Roadmaps app data, lost data will include:

Any schedules not synced with date fields on the Jira issues
Theme swimlanes
Date markers
Which Release versions from Jira have a visible version marker (though the Releases versions themselves are native Jira data)

If date syncing is enabled, your migrated Jira issues will appear at the same points on the timeline after migrating.

Theme swimlane data will be lost, so all issues will appear in the “Issues without themes” swimlane underneath an empty “My Theme” swimlane.

Migrations with custom scripts

In some situations, it may be possible to migrate app data by developing custom scripts. This generally requires extensive use of Jira APIs, and access to the Jira database may be also helpful.

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. date markers for the roadmap for a specific 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.

Easy Agile Roadmaps uses:

boardId in issue property "ear-schedules"
issueId in issue property "ear-schedules"
v (release version ID) in board property "ear-markers"

Critical app data is stored in:

Issue property "ear-schedules"
Board properties "EA-themes", "ear-markers"

If you’re planning a custom migration or have any questions about migrating Easy Agile Programs app data, let us know!