Jira to Jira migration
Last updated
Was this helpful?
Last updated
Was this helpful?
Migrating Epics, tasks, and issues from Jira to Jira can be a significant move for a team or organization.
Getint specializes in handling complex data migrations, ensuring that all relevant data/fields—including Epics, tasks, and issue item types—are accurately transferred from Jira to Jira. We address the data and the relationships and hierarchies between different elements.
Our emphasis on data accuracy and integrity is often a standout feature, ensuring that no important information is lost or corrupted during the migration process.
Discover our comprehensive guide to mastering Jira migrations with Getint. To learn more about how our tool works and how you can maximize its potential, visit
For migrating historical items, you must have a migration license with us as an integration license won’t suffice in this case.
The migration licenses offer different features depending on the scale of your migration. To learn more about and purchase our migration license, please visit our pricing page and select the "Migration" tab for more details.
When you set up the integration, new items created in either of the Jira instances will sync across both platforms. To avoid issues with live environments, you can disable the integration right after setup, schedule migration with the integration off, or pause work in both systems during the migration.
2. With your integration set, click on the "Migrate Data" button, located in the left side menu:
Check the "Enable Migration on Next run" box to continue.
3. On this screen, you can customize your migration by choosing the direction (Right to Left or Left to Right), determining the handling of previously migrated items (replace, update, or skip), and specifying any fields you want to resync to capture updated data post-migration.
Configure your migration preferences, then either enter the specific item IDs you wish to migrate or leave the field blank to, instead, add a date range at the bottom to include items created within that period. The tool will migrate all items that fall within the specified date range, so please make sure that in case you want to migrate specific items by their IDs, to fill a date range that covers the date of creation of these items.
4. With the migration set per your preference, click "Schedule Migration" at the bottom. The tool should migrate the items based on the specifications on the next synchronization run.
5. After scheduling a migration, you can observe the results of your migration through the reporting section or the "latest runs" from the left menu.
Your items should have been successfully migrated, you can check the receiving end to verify the integrity of the migrated data (note that migration runs are displayed as "MIGRATION," under the "Mode" column)
Below you can see an example of how tasks will be migrated from one side to the other.
To migrate data based on creation dates, use our calendar to select the relevant dates for your tasks. Getint will then recognize the specified timeframe and fetch only the tasks from that period.
To migrate data based on item IDs, simply copy the relevant IDs to sync only the specified tasks. Getint will then identify these IDs and retrieve the associated tasks.
To migrate data based on the filters you applied to the integration, use the relevant filters to sync only the specified tasks. Getint will then recognize these filters and retrieve the associated tasks.
1. For setup integration between Jira and Jira, you can check the steps to build this integration here:
If you are using the app's trial version or have a limited integration license, you'll see a warning indicating that you have a restricted number of Migration Runs available. Each Migration Run is capped at migrating a maximum of 5 items. If you’d like to learn more about the different licensing models and pricing, please visit
When it comes to Jira Jira migrations, the most common scenario is syncing Jira Software with Jira Service Management or vice-versa. With Getint this is achievable by simply connecting the corresponding projects to both Jira instances. For more information on how to connect Jira instances, please refer to this .
If you experience any issues while performing the process above, please raise a ticket through our
