Unsupported migration pathways for Easy Agile Programs
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 Programs 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 Programs' integration for Site import is not compatible with other Jira migration method. It has been removed from the app.
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
If you migrate Jira data without migrating Easy Agile Programs app data, you may need to re-create your Programs and Increments on the destination site manually.
However, configuration and other app-specific data are stored separately and will not be migrated if you migrate Jira data. Data that isn’t sourced from Jira will be lost if you migrate only Jira data:
Plans made on the Team planning page for Kanban boards (i.e. in columns instead of sprints from Jira)
Sprint capacity estimates entered on the Team planning page
In some cases, the data can be easily re-synchronized after migrating to make this process quicker:
If the Program is configured to use date syncing, issues planned on the Program roadmap also store the schedules in the date fields on the Jira issue. This means that you can recreate the Program roadmap by creating a Program and Increment with the same configuration. The roadmap will automatically re-populate with the same Jira issues.
Sprints from Scrum boards can be synchronized with an Increment. Syncing the migrated sprints to a new Increment will add the same issues back to the Team Planning page.
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 Programs 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_349192_“.
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. which Jira boards are selected as Teams in a Program). 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_349192_INCREMENT" references a "AO_349192_PROGRAM"."ID". the "AO_349192_PROGRAM" data must be imported first.
Some data is stored in issue properties and sprint properties. The issue properties also reference app data by ID.
For example, a Team PI Objective can be linked to one or more Jira issues. The property “EAP-team-objectives” will be added to those issues and use the ID number of the Objective.
Check or test if your Jira data migration tool migrates issue/sprint properties.
If the destination Jira site already has Easy Agile Programs 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_349192_PROGRAM"."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 your migration updates app data ID numbers (e.g. to avoid overlapping with existing app data on the destination site), you’ll need to update the ID numbers in the issue properties as well.
If you’re planning a custom migration or have any questions about migrating Easy Agile Programs app data, let us know!