As projects evolve, they need maintenance and sometimes migration. Maybe there has been a reorg within the company, or the work was created in a temporary holding spot but now needs a permanent home. Whatever the reason, moving work items between projects or organizations in Azure DevOps is no simple feat. Today, you could utilize the REST API and Excel to accomplish this. However, learning how to leverage the REST API can be tricky. Getting the Excel sheet just right is also a challenge. We at PRAKTIK developed a set of tools to make this effortless.

What is PRAKTIK’s Azure DevOps Migration Tools?

These tools are a set of proprietary utilities that enable the migration of various artifacts between a source instance of Azure DevOps and a target Azure DevOps instance using REST APIs. The source can be on-premises or in the cloud.

The focus of these tools is to migrate your data in as high-fidelity a way as possible. So, these tools are designed to retain the entire history of the data  while you migrate your work items, test plans, suites, and teams from one team project or organization to another. The tools also retain things like sprint history, shared queries, project iterations, and attachments. This is paramount, especially for long-standing projects. The history of a project can help with planning for the future and understanding what worked in the past.

Furthermore, during the migration, you’ll have the ability to re-map fields if desired. For example, all work items assigned to one identity can be automatically reassigned to another identity. This is helpful in reorgs in which team members are shuffled between teams and no longer work on a particular project.

However, data retention doesn’t stop with history. These migration tools also retain relationships between work items. This means you’ll keep the context of your work items to enable better future development. You’ll also keep source code GIT commits and custom work item fields. Therefore, you won’t have to redo any of the work required to create custom work items or lose any of that documentation.

Because the tools are driven by the Azure DevOps REST APIs, some of the migration functionality is limited by the capabilities of the API. Although the work items will store the old work item ID for easy audit and cross-reference, work items will be assigned new IDs in the target Azure DevOps instance.

Advantages of Working with PRAKTIK

When you choose to work with PRAKTIK and take advantage of this proprietary solution, you can be confident in the knowledge that your migration is being handled by a team of experts. We have performed hundreds of work item migrations, which means we can assist with important migration decisions and even fast-track the migration. We also perform dry runs before the actual migration. This gives you the ability to validate the migration while your team continues to work in the source system.

PRAKTIK’s Azure DevOps Migration Tools provide a comprehensive solution for migrating work items between Azure DevOps instances, offering flexibility and high fidelity while ensuring data integrity during the migration process. Contact our team of experts for more information or to get started today.