Azure DevOps Migration Tools naked Agility with Martin Hinshelwood & Co.

Ask Questions on Github: https://github.com/nkdAgility/azure-devops-migration-tools/discussions

Compatability

These tools run on Windows and support connecting to Team Foundation Server 2013+, Azure DevOps Server, & Azure DevOps Services. They support both hosted and on-premise instances and can move data between any two.

• Supports all versions of TFS 2013+ and all versions of Azure DevOps.
• You can migrate from any TFS/Azure DevOps source to any TFS/Azure DevOps target.

What do you get?

• Move Work Items, Test Plans & Suits, and Pipelines between projects, collections, and even organizations.
• Merge multiple projects into a single project even from different organizations.
• Split one project into several projects even between projects, collections, and even organizations.
• Change Process process from Agile to Scrum or any other template.
• Bulk edit Work Items.

What does this tool do?

For the most part we support moving data between ((Azure DevOps Server | Team Foundation Server | Azure DevOps Services) <=> (Azure DevOps Server | Team Foundation Server | Azure DevOps Services)) for any version greater than 2013.

• Work Items (including links and attachments) with custom mappings for fields and types
  • Copy Work Items between locations with history
  • Bulk Edit in place of Work Items (Great for cleaning up data, process template changes)
  • Optionaly includes Teams, Shared Queries
• Test Plans & Suites
  • Copy Test Plans & Suites between locations
  • Includes Configurations, Shared Steps, Shared Parameters
• Pipelines
  • Copy Pipelines between locations
  • excludes XAML & Classic Builds & Release
• Processes
  • Copy Processes between locations

Note: 'Locations' includes Projects, Collections, Organizations

Important: This tool is intended for experienced users familiar with TFS/Azure DevOps object models and debugging in Visual Studio. It was developed by 100+ contributors from the Azure DevOps community to handle various scenarios and edge cases. Not all cases are supported.

Support Options: Community support is available on GitHub. For paid support, consider our Azure DevOps Migration Services.

Quick Links

• Documenation
• Installation
• Permissions
• Getting Started
• Configuration Reference
• Community Support
• Commercial Support
• Change Log

The documentation for the preview is on Preview]

Metrics

These metrics come directly from Custo Metrics in Application Insights and are updated every 10 minutes. They are experimental and may not be accurate.

This tool uses OpenTelemetery to collect metrics and logs, and Application Insights to store and analyse them. Exceptions are also sent to Elmah.io for analysis and improvement.

Advanced tools

There are additional advanced tooling available on Azure DevOps Automation Tools. These are a collection of Powershell scripts that can be used to;

• Generate Migration Tools configurations across many projects on many organisations
• Export Stats on many projects on many organisations
• Publish Custom fields across many projects on many organisations
• Output the fields and other data for many projects on many organisations

These tools are designed to help you manage migration of Work Items at scale.

Support

1. Question & Discussion - The first place to look for usage, configuration, and general help.
2. Issues on GitHub - If you have identified a bug and have logs then please raise an issue.

Professional Support

You can get free support from the community above and on social media on a best effort basis if folks are available. If you are looking for paid support naked Agility with Martin Hinshelwood & Co has a number of experts, many of whom contribute to this project, that can help. Find out how we can help you with your migration and book a free consultation to discuss how we can make things easier.

We use these tools with our customers, and for fun, to do real world migrations on a daily basis and we can:

• Consult with your internal folks who need help and guidance in running the tooling.
• Make changes to the tool to support your needs; all additions are committed to the main repo.
• Run the migration for you:- you would need to pay for the hours that we would spend baby-sitting the running migrations