If you use Azure DevOps, you might find yourself in the situation where your company decides to switch to Jira. Your projects need to move from one environment and into another. Some of your team players will already be using Jira, and the others will do anything to stay with Azure DevOps as long as possible. There will be a lot of confusion and misunderstanding caught in between. And you'll have to do all the work of migration to Jira.

Of course, you have options:

You can do it manually with CSV, which involves copying and pasting, downloading, and uploading files. This might take weeks, if not months, of your team’s time. Plus, you will expose your projects to threats like losing some essential data along the way.
You can hire an IT company to take care of this migration, but this is an expensive proposition.
You can use the TFS4JIRA app to migrate more information than through a CSV import - and much faster.

Let's see how TFS4JIRA-based migration addresses CSV-based migration limitations. But in a nutshell, with a CSV import, you will leave some essential data behind. With TFS4JIRA, you will not.

Keeping both Azure DevOps and Jira synchronized in the process of migration

TFS4JIRA app offers a live synchronization feature.

If you consider that your projects need continuity, the migration needs to run in the background without interfering with your sprints. If you use TFS4JIRA, your developers can still work in the original environment in Azure DevOps and slowly merge to Jira. Every change made in Azure Dev Ops work item will automatically translate to a Jira issue change.

The live sync feature will help you secure the transition process by migrating smaller chunks of data, one by one, rather than trying to do the whole lot within one sitting. This way, you will finish the relocation without losing any precious belonging down the road. When you’re ready, you can safely leave the old platform behind (or to keep it running, just in case).

Migrating comments and history

A typical CSV file will not contain your or your teammates’ comments left in a work item. It will not store any attachments and linkages, such as issue parent/child relationships or related links between user stories at the same level of importance.

Not taking comments and attachments with you to another environment means dismissing your team’s previous work. Post-migration, you can add attachments manually all over again - even though it will take significant time. However, the recovery of comments - usually meaningful for the project - will be impossible.

With TFS4JIRA, it can be done easily.

Keeping the relationship between related user stories

A CVS-based migration will "unlink" all your relationships. Those user stories linked to each other will be "torn apart" after a manual migration.

Map Azure DevOps values not available in Jira

With TFS4JIRA, you can map default value when some users are not available in Jira, but they exist in Azure DevOps. Those unmapped users can be synced as “anything else” to a user value option.

TFS4JIRA gives you a faster, secure, and more efficient way to connect Azure DevOps and Jira environments. With the TFS4JIRA app, you can migrate all your work times, convert them to Jira issues, and take your legacy with you. This means saving all the comments, attachments, and linkages during the migration process.

Read the guide

Migrating from Azure DevOps to Jira with TFS4JIRA

Subscribe for updates