Azure DevOps to Jira migration
Last updated
Last updated
Migrating Epics, tasks, and issues from Azure DevOps 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 Azure DevOps to Jira. We address not just the data but also 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 Mastering Jira Migration: A Comprehensive Guide with Getint.
For migrating historical items, you will need to 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. If you want to learn more about and purchase our migration license, please access our pricing page and select the "Migration" tab for more details.
Before buying a license, you can use our trial application to preview the migration process. The trial allows up to 20 migration runs, each with a maximum of 5 historical items. After reaching the 20 migration runs threshold, further migrations require a license.
To access our app and install the trial version, please go to: https://marketplace.atlassian.com/apps/1223931/azure-devops-for-jira-integration-migration-enterprise?hosting=cloud&tab=overview
1. For the integration between Jira and Azure DevOps, you can check the steps to configure this integration here: https://docs.getint.io/guides/integration-synchronization/jira-azure-devops-integration
When you set up the integration, new items created in Azure or Jira 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:
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: https://docs.getint.io/billing-and-services/licensing
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.
If you have applied filters, they will exclude items that don't meet the criteria from being migrated. This setup is useful for migrating specific items without manually entering each ID—just set the date range at the bottom and let the filters handle the rest. Ensure your filters are correctly configured for your workspace to get accurate results.
You can learn more about filters here:https://docs.getint.io/getintio-platform/workflows/items-filtering#where-to-find-items-filtering
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)
If you experience any issues while performing the process above, please raise a ticket through our support portal.
