Node Migration Not Respecting Area/Iteration Maps

[zafar1995]

When I run the tool using execute, it automatically migrates all Area and Iteration nodes, before processing any work items — even though I have:

1. Disabled unnecessary processors

2. Defined mappings in AreaMaps and IterationMaps

But this behavior still persists and all nodes get created. In My case I have 1000+ Area Map and 1000+ Iteration present at Source .

What I've Tried
I defined this in my WorkItemMigrationConfig:

{
"Processor": "WorkItemMigrationConfig",
"Enabled": true,
"AreaMaps": {
"MyProject\Area 1": "MyTargetProject\Area A"
},
"IterationMaps": {
"MyProject\Iteration 1": "MyTargetProject\Sprint A"
}
}

I also tried disabling the node processor:

{
"Processor": "NodeStructuresMigrationConfig",
"Enabled": false
}

But the tool still processes and creates all Area/Iteration nodes during execution.

Question
How can I prevent all nodes from being migrated, and restrict migration to only the nodes I define in AreaMaps and IterationMaps?

Is there a way in v16.2.9 to disable automatic node migration completely — or filter specific nodes to migrate only?

Thanks in advance for your help!

[zafar1995]

@MrHinsh

Using v16.2.9 of the migration tool — even with NodeStructuresMigrationConfig disabled and AreaMaps/IterationMaps defined, all nodes (Area/Iteration) are still getting migrated.

Looking for help on how to restrict node migration to only the mapped ones. Appreciate your input!

[MrHinsh]

Can you provide your config?

[zafar1995]

Thank you for your message.

As requested, please find attached the configuration details.

[MrHinsh]

I don't see any configuration of the Node tools in the config that you shared. If you pass the config through devopsmigration upgrade -c configuration.json it will remove anything invalid.

[zafar1995]

Thanks for your message. I did try running the config through devopsmigration upgrade -c configuration.json, but unfortunately, it didn't resolve the issue.

I also attempted the code snippet below , but it didn’t work either.

https://devopsmigration.io/docs/reference/tools/tfs-node-structure-tool/

"TfsNodeStructureTool": {
"Areas": {
"Filters": null,
"Mappings": [
{
"Match": "^Skypoint Cloud$",
"Replacement": "MigrationTest5"
}
]
},
"Enabled": "True",
"Iterations": {
"Filters": null,
"Mappings": [
{
"Match": "^Skypoint Cloud\\Sprint 1$",
"Replacement": "MigrationTest5\Sprint 1"
}
]
},
"ReplicateAllExistingNodes": "True",
"ShouldCreateMissingRevisionPaths": "True"
}

Could you please share the correct code or let me know the exact processor name or configuration needed for setting up the Node tools?

Your help would be much appreciated.

[MrHinsh]

The TfsNodeStructureTool controls the area and iteration path creation.

What part can you not get working?

[zafar1995]

I'm currently working on migrating Azure DevOps (ADO) boards from our on-premises ADO Server to Azure DevOps Services (cloud). Our on-prem instance contains thousands of boards, teams, iterations, and area paths. However, I do not intend to migrate everything at once.

My goal is to migrate only specific boards, which I will define in a configuration file. This includes migrating related work items, iterations, and area paths tied to those selected boards — without impacting the rest of the environment.

Could you please guide me on how I can achieve this targeted migration using the Azure DevOps Migration Tools? Any best practices, sample configuration templates, or suggestions would be appreciated.

Thanks in advance for your support.