Jira to Azure DevOps Migration
Last updated
Was this helpful?
Last updated
Was this helpful?
Migrating Epics, tasks, and work items from Jira to Azure DevOps is a critical step for organizations consolidating platforms or transitioning development and support workflows. With Getint, this migration process becomes straightforward, accurate, and reliable.
Getint ensures that all essential data, including issue types, custom fields, and relationships, are transferred while preserving the integrity and hierarchy of your records. Whether you're moving an entire backlog or selectively migrating specific items, this guide walks you through the process step-by-step.
Migrating historical data requires a migration license, as integration licenses alone do not support this functionality. Migration licenses are billed separately.
To purchase a license, visit our and select the "Migration" tab. You can also contact our team via the for assistance.
Before purchasing, we encourage you to test the process using our trial version, which allows:
Up to 20 migration runs
A maximum of 5 items per run
To begin your trial, visit:
For best practices and advanced tips, see:
Before starting your migration, ensure that custom fields used in Azure DevOps also exist in Jira. If the destination field is missing, it must be created manually to enable proper mapping.
For steps to create fields in both tools, refer to:
If a field in Azure DevOps doesn’t have a direct counterpart in Jira or you want to avoid the 1:1 mapping, you can use the Use label from the other side option to inject its value into a custom text field.
Steps:
Create a text custom field in Azure DevOps.
In the Getint field mapping screen, map the source Azure DevOps field to the Jira text field.
Enable Use label from the other side to insert the original value.
This approach will insert the label/value of the original field into the destination field. Especially helpful for migrating the Assignees. You probably don’t want to recreate the accounts of people no longer in the company in Jira. This way, no mapping is required; we will inject the value into a text field.
After setup, we recommend disabling the integration or pausing activity in both tools during migration to avoid sync conflicts.
Once your integration is set:
Click Migrate Data from the left-side menu.
If you're on a trial version, a warning will appear regarding your migration limits (5 items per run, 20 runs).
Enable Migration on Next Run to proceed.
Migration Direction: Choose whether data flows from Azure DevOps to Jira or vice versa.
Handling Previously Migrated Items: Choose how to handle items that were already migrated:
Replace (overwrite existing items).
Update (sync only new changes).
Skip (ignore already migrated items).
Selective Resync (Optional): If a previous migration was incomplete, choose specific fields to resync, such as Assignee, Status, and Description.
To resync all fields, enter ALL.
Selective Item Migration (Optional):
Enter specific item IDs to migrate only selected tasks.
Use JQL filtering for refined selection.
Time Range Filtering:
Select a creation date range in the UTC timezone.
Only issues created or updated within the selected period will be migrated.
When your settings are complete, click Schedule Migration at the bottom of the screen.
Click Schedule Migration to queue the process.
The system will begin migration during the next synchronization run.
Monitor progress in the Reporting section or the Latest Runs tab.
If you want to keep the items in sync after migration:
Open the Integration Settings
Click More > Enable Continuous Sync
You can also uncheck the box below when you are setting up the migration.
This ensures that newly created tasks, issues, and updates flow between Jira and Azure DevOps moving forward.
Traditional CSV imports require manual data manipulation and lack automation, often leading to data loss and inconsistency. Getint eliminates these issues by providing:
✔ Getint enables precise manual field mapping, ensuring correct data alignment ❌ CSV imports require manual restructuring after import
✔ Getint supports JQL filtering, item ID selection, and date-based migration ❌ CSV imports transfer all data, requiring manual clean-up
✔ Getint provides sync logs, error tracking, and live migration updates ❌ CSV imports offer no real-time feedback
✔ Getint automatically syncs data post-migration ❌ CSV imports require additional steps to align projects and workflows
You can also migrate values from multiple source fields into one text field. You can read more about how to set up this option
For more tips, refer to: .
Before migrating, you must set up a working integration between Jira and Azure DevOps. Follow our full integration guide, , to configure your connection properly.
Important: Ensure that your JQL filter or item IDs align with the creation/updating date range to avoid missing items during migration. Learn more:
For additional assistance or troubleshooting, visit our .
Considering migration? with our experts to explore how Getint can optimize your Jira to Azure DevOps migration.
