Updated Microsoft Azure DevOps (ADO) Migration Tool Available

8-Dec-2021 by Inflectra Product News

Those following the Microsoft software development ecosystem closely will have heard about the planned depreciation of Microsoft Azure DevOps (ADO) formerly known as Microsoft Team Foundation Services (TFS) and Visual Studio Team System (VSTS) in favor of GitHub Enterprise. We have heard from many current ADO users that they are looking for alternatives to ADO as well as a way to migrate to GitHub and have access to features (like requirements management, test case management and Scaled Agile) not available in GitHub. Well, SpiraTeam is ready for you, and we have just released an updated ADO migration tool to make the process even easier.

What's New?

Previously our migration tool was known as the Microsoft Test Manager (MTM) Migration Tool and it only was able to migrate the Microsoft Team Foundation Server (TFS) or Azure DevOps (ADO) Test Plans data into SpiraTest. With the recent announcement that ADO is being eventually replaced by GitHub Enterprise, we decided it made sense to extend the functionality of the migration tool to cover all work item items, hence it has been renamed the Microsoft Azure DevOps (ADO) Migration Tool:

  • Backlog Items
  • Iterations
  • Test Cases
  • Test Plans
  • Test Runs
  • Defects / Bugs

Migrating from ADO/TFS to SpiraTeam

The migration tool for ADO lets you connect to an instance of Microsoft Azure DevOps (ADO), Azure DevOps Server, Team Foundation Server (TFS), or Microsoft Test Manager (MTM) - which are all basically the same system - and specify which items you would like to migrate. For on-premise installations, you log in with a Windows ActiveDirectory domain, login, and password, for ADO you will typically use a Personal Access Token (PAT) instead:

ADO Import Tool for Spira

Once that is done, the import tool will seamlessly migrate over the different artifacts, maintaining the relationships between the items:

Azure DevOps Boards

From the Boards section, the importer will migrate over the following:

  • Bugs > Incidents [type = Bug]
  • Features > Requirements [type = Feature]
  • Stories> Requirements [type = Story]
  • Epics> Requirements [type = Epic]

Bugs and Backlog Items in ADO

Azure DevOps Test Plans

From the Test Plans section, the importer will migrate over the following:

  • Test Suite > Test Set
  • Test Case > Test Case
  • Test Step > Test Step
  • Test Run > Test Run

Test Cases and Test Plans in ADO

In addition, the Iterations from the Iteration Path will be migrated over as Releases and Sprints into SpiraTeam, and the Areas from ADO will become a new custom property in SpiraTeam called "Area".

Once the migration is complete, all the data will be seamlessly migrated over to SpiraTeam:

ADO Import to Spira Completed


The Product Backlog Items (PBIs) from ADO will be migrated over as the appropriate type of requirement in SpiraTeam. We maintain the priority, status, and other fields:

Requirements in Spira

Releases / Iterations

The Iterations from ADO will be migrated over as the appropriate type of release or sprint in SpiraTeam:

Releases and Sprints/Iterations in Spira

Test Cases and Test Sets

The Test Plans from ADO will be migrated over as test cases, test steps, test sets and test runs in SpiraTeam. We maintain important items such as the folder structure, shared test steps and execution history:

Test Cases and Test Folders in Spira


The Bugs from ADO will be migrated over as the appropriate type of incident in SpiraTeam. We maintain the priority, status and other fields:

Bugs/Defects/Issues in Spira

Once the migration is complete, you are now ready to use the migrated project in SpiraTeam.

Connecting SpiraTeam and GitHub

Once you have the project migrated from ADO to SpiraTeam, you can now connect the project to GitHub. The following article describes the different integrations available with GitHub, both present (issues and code repositories) and planned (GitHub actions).

Plugin button for launching GitHub Actions

With the migration from ADO to SpiraTeam completed and the connection to GitHub established, you now have your enterprise Agile and DevOps toolchain in place.