Tutorial: Get started with the Azure DevOps Migration Tools

[MrHinsh]

This discussion is for questions, feedback, and community support related to the Tutorial: Get started with the Azure DevOps Migration Tools.

Quick Reference

• Documentation: Tutorial: Get started with the Azure DevOps Migration Tools

How to Use This Discussion

• Ask Questions: If you need help configuring or using this component
• Share Examples: Post your configuration examples or use cases
• Report Issues: Describe any problems you encounter (though bugs should be reported as GitHub Issues)
• Request Features: Suggest improvements or new features

Related Documentation

Please refer to the official documentation for detailed configuration options and examples.

[rpollick]

What is the command to run a test migration without moving data?
I thought I remember it being something like this:
devopsmigration.exe execute -validate -c configuration_SOM.json

[MrHinsh]

There is no -validate option.

[PSammeta]

I have installed devopsmigration 16.2.9 version in my local computer. For above basic configuration file for 16.2 version when i run devopsmigration execute --config .\configuration.json.
I am getting below issue even i am using Area english language and project name correct.

An error occurred in the Migration Tools causing it to stop! This is likley due to a configuration issue and is not being logged remotely. You can always ask on https://github.com/nkdAgility/azure-devops-migration-tools/discussions
MigrationTools.Exceptions.MigrationToolsException: Unable to load Common Structure for Target.This is usually due to TFS having a different installed langauge version than was expected.. Validate that 'Area' is the correct name in your version. This would be something like 'Fläche' or 'Aire'. If you open the area tree in Visual Studio, or web access, you should see the name your langauage uses for 'Area' or 'Iteration. Do not try to add a specific area or iteration path to this field. Check the defaults on https://devopsmigration.io/Reference/Endpoints/TfsTeamProjectEndpoint/ for an example fro English.
   at MigrationTools.Tools.TfsNodeStructureTool.ProcessCommonStructure(String treeTypeSource, String localizedTreeTypeName, String projectTarget, TfsNodeStructureType nodeStructureType) in D:\a\azure-devops-migration-tools\azure-devops-migration-tools\src\MigrationTools.Clients.TfsObjectModel\Tools\TfsNodeStructureTool.cs:line 464
   at MigrationTools.Tools.TfsNodeStructureTool.MigrateAllNodeStructures() in D:\a\azure-devops-migration-tools\azure-devops-migration-tools\src\MigrationTools.Clients.TfsObjectModel\Tools\TfsNodeStructureTool.cs:line 408
   at MigrationTools.Tools.TfsNodeStructureTool.ProcessorExecutionBegin(TfsProcessor processor) in D:\a\azure-devops-migration-tools\azure-devops-migration-tools\src\MigrationTools.Clients.TfsObjectModel\Tools\TfsNodeStructureTool.cs:line 279
   at MigrationTools.Processors.TfsWorkItemMigrationProcessor.InternalExecute() in D:\a\azure-devops-migration-tools\azure-devops-migration-tools\src\MigrationTools.Clients.TfsObjectModel\Processors\TfsWorkItemMigrationProcessor.cs:line 119
   at MigrationTools.Processors.Infrastructure.Processor.Execute() in D:\a\azure-devops-migration-tools\azure-devops-migration-tools\src\MigrationTools\Processors\Infrastructure\Processor.cs:line 99
[22:38:32 INF] [16.2.9] TfsWorkItemMigrationProcessor completed in 00:00:00
[22:38:32 ERR] [16.2.9] TfsWorkItemMigrationProcessor The Processor MigrationEngine entered the failed state...stopping run
[22:38:32 INF] [16.2.9] Command ExecuteMigrationCommand completed in 00:00:05.4447657
[22:38:32 INF] [16.2.9] Check the logs for errors: C:\Users\PSammeta\AppData\Local\Microsoft\WinGet\Packages\nkdAgility.AzureDevOpsMigrationTools_Microsoft.Winget.Source_8wekyb3d8bbwe\logs\20250717223826

[RithwikaSuresh16]

I have installed version 16.2.11. I am getting the following errors for Feedback Request, Feedback Response, Shared Steps and Shared Parameter - "Does not contain reflected work ID field 'Custom.ReflectedWorkItemID'". I don't have these work item types in my source project. Since these WITs are hidden, I am unable to add reflected work ID field on them. I have already excluded these WITs in my config.json file in the WIQL query. Please suggest a workaround.

[YuriVanZieks]

If you are trying to migrate Work Items, I managed to go around that issue with this

        "Enabled": true,
        "FixedTargetFields": {
          "User Story": []
        },
        "IncludeWorkItemtypes": [
          "Bug",
          "Task",
          "User Story",
          "Feature",
          "Epic",
          "Test Case",
          "Test Plan",
          "Test Suite",
          "Shared Steps",
          "Issue"
        ]
      }

I stopped trying to use the Exclude Option and went for the Include instead, it will disregard the Items that are not in the include option (but will also not migrate them)

Hope this helps

[YuriVanZieks]

Forgot to specify it goes in the CommonTools section

[rpollick]

This is exactly what I did. Removed the Exclude and only used the IncludeWorkItemTypes. Working on just migrating the Task work item due to a field issue on the Source and Target. Ironically the field names are the same, but the Type on the source is Text (One line) and the target is Integer. I am hoping that this will correct the issue.

"FieldMappingTool": {
"Enabled": true,
"FieldMaps": [
{
"FieldMapType": "RegexFieldMap",
"ApplyTo": ["Task"],
"SourceField": "Custom.RFCNumber",
"TargetField": "Custom.RFC Number",
"pattern": "(\d+)",
"replacement": "$1"
},
]
},

[rpollick]

I just correct the TargetField. There shouldn't be a space between RFC and Number. This is what it was corrected to.

"FieldMappingTool": {
"Enabled": true,
"FieldMaps": [
{
"FieldMapType": "RegexFieldMap",
"ApplyTo": ["Task"],
"SourceField": "Custom.RFCNumber",
"TargetField": "Custom.RFCNumber",
"pattern": "(\d+)",
"replacement": "$1"
},
]
},