Areas and iterations missing, cant able to migrate work items

[vijaykumars-newt]

iam trying to migrate work items from azure devops server to cloud , for some of the projects iam gettitng issue from migration tool like
2025-04-07 18:39:24,196 - INFO - [18:39:24 WRN] [16.0.5] !! There are MISSING Area or Iteration Paths

2025-04-07 18:39:24,197 - INFO - [18:39:24 WRN] [16.0.5] NOTE: It is NOT possible to migrate a work item if the Area or Iteration path does not exist on the target project. This is because the work item will be created with the same Area and Iteration path as the source work item with the project name swapped. The work item will not be created if the path does not exist. The only way to resolve this is to follow the instructions:

2025-04-07 18:39:24,197 - INFO - [18:39:24 WRN] [16.0.5] !! There are 2 Nodes (Area or Iteration) found in the history of the Source that are missing from the Target! These MUST be added or mapped before we can continue using the instructions on https://nkdagility.com/learn/azure-devops-migration-tools//Reference/v2/ProcessorEnrichers/TfsNodeStructureTool/#iteration-maps-and-area-maps

2025-04-07 18:39:24,198 - INFO - [18:39:24 WRN] [16.0.5] MISSING Area: sourcePath=ADO ON_PREM MIGRATION FOR TRACKING, targetPath=null, anchored=False, IDs=6269793,6271994,6272536,6269792,6269791,6269789,6269790,6272534,6272535,6269788

2025-04-07 18:39:24,198 - INFO - [18:39:24 WRN] [16.0.5] MISSING Iteration: sourcePath=ADO ON_PREM MIGRATION FOR TRACKING\TEC\PI06\PI6.1, targetPath=null, anchored=False, IDs=6269793,6271994,6272536,6269792,6269791,6269789,6269790,6272534,6272535,6269788

2025-04-07 18:39:24,208 - INFO - [18:39:24 ERR] [16.0.5] Missing Iterations in Target preventing progress, check log for list. To continue you MUST configure IterationMaps or AreaMaps that matches the missing paths..

.

even i dont have this araes and iteration sin source

[MrHinsh]

There are 2 Nodes (Area or Iteration) found in the history of the Source that are missing from the Target! These MUST be added or mapped before we can continue using the instructions on https://nkdagility.com/learn/azure-devops-migration-tools//Reference/v2/ProcessorEnrichers/TfsNodeStructureTool/#iteration-maps-and-area-maps

The key word here is "history".

[mikkelh-SDU]

@MrHinsh Thanks for the suggestion! I tried using the prefixToNode approach you mentioned, but unfortunately, it didn’t work in my case.

Is there anything else I could try? Maybe there’s something specific about how the history paths are handled that I’m missing?

Any additional guidance would be really appreciated!

[MrHinsh]

It looks like it may need a debug in Visual Studio to see what's going wrong for you... What you have should work.

[mikkelh-SDU]

It looks like it may need a debug in Visual Studio to see what's going wrong for you... What you have should work.

Hey @MrHinsh, just to clarify—did you mean that I should try debugging it in Visual Studio on my end, or that you might take a look at it in Visual Studio?

[mikkelh-SDU]

Hey @MrHinsh!

I noticed you released 16.2.0-preview.4 of the tool, so I gave it a try—and it worked! 🎉

I used the command you provided to upgrade my configuration.json file, and then added my Area and Iteration mappings using the new format. Here's what I ended up with:

"Areas": {
  "Filters": [],
  "Mappings": [
    {
      "Match": "^TimeEdit Integration([\\\\]?.*)$",
      "Replacement": "IntegrationsPlatform"
    }
  ]
},
"Iterations": {
  "Filters": [],
  "Mappings": [
    {
      "Match": "^TimeEdit Integration$",
      "Replacement": "IntegrationsPlatform"
    },
    {
      "Match": "^TimeEdit Integration([\\\\]?.*)$",
      "Replacement": "IntegrationsPlatform"
    }
  ]
}

Thanks again for your help and guidance—it really made a difference! 🙌

I've attached the full configuration.json file in case it's helpful for you or anyone else running into a similar issue:
configuration-upgraded copy.json

[MrHinsh]

@satano looks like you may have fixes a bug along with way :)

[oipolloi]

have you encountered when running the migration it removes the iterations and maps on team configuration?
then have NodeStructureEnricher.NodePathNotAnchoredException?

[mikkelh-SDU]

@oipolloi I'm not sure if you mean OP or not?
But in my case we had the issue as you can see in my log file

NodeStructureEnricher.NodePathNotAnchoredException(TimeEdit Integration, Area)

But I'm 99,9% sure it was because we renamed the project and a few work items had that in their revision history.
And I'm not sure what MrHinsh or Satano did in the newer versions (>16.1.0) to fix that. And we did not care it mapped over 1:1, so we just used the very simple mapping as stated above:

Hey @MrHinsh!

I noticed you released 16.2.0-preview.4 of the tool, so I gave it a try—and it worked! 🎉

I used the command you provided to upgrade my configuration.json file, and then added my Area and Iteration mappings using the new format. Here's what I ended up with:

"Areas": {
  "Filters": [],
  "Mappings": [
    {
      "Match": "^TimeEdit Integration([\\\\]?.*)$",
      "Replacement": "IntegrationsPlatform"
    }
  ]
},
"Iterations": {
  "Filters": [],
  "Mappings": [
    {
      "Match": "^TimeEdit Integration$",
      "Replacement": "IntegrationsPlatform"
    },
    {
      "Match": "^TimeEdit Integration([\\\\]?.*)$",
      "Replacement": "IntegrationsPlatform"
    }
  ]
}

Thanks again for your help and guidance—it really made a difference! 🙌

I've attached the full configuration.json file in case it's helpful for you or anyone else running into a similar issue: configuration-upgraded copy.json

[oipolloi]

``@mikkelh-SDU yes was referring to your comment :) i guess we don't have the same case

while our case we are trying to move sourceProjectA to targetProjectA

what makes me wonder is its showing errors on nodes on other projects like the sample log below
NodeStructureEnricher.NodePathNotAnchoredException(sourceProjectB, Area)
NodeStructureEnricher.NodePathNotAnchoredException(sourceProjectC, Area)
NodeStructureEnricher.NodePathNotAnchoredException(sourceProjectB\Sprint 2 - 2025, Iteration)
NodeStructureEnricher.NodePathNotAnchoredException(sourceProjectB, Iteration)
NodeStructureEnricher.NodePathNotAnchoredException(sourceProjectB\Sprint 2, Iteration)
NodeStructureEnricher.NodePathNotAnchoredException(sourceProjectB\Sprint 3, Iteration)
NodeStructureEnricher.NodePathNotAnchoredException(sourceProjectB\Sprint 1 - 2025, Iteration)
NodeStructureEnricher.NodePathNotAnchoredException(sourceProjectB\Sprint 3 - 2025, Iteration)
NodeStructureEnricher.NodePathNotAnchoredException(sourceProjectC, Iteration)
!! There are MISSING Area or Iteration Paths

!! There are 9 Nodes (Area or Iteration) found in the history of the Source that are missing from the Target!
MISSING Area: sourcePath=sourceProjectB, targetPath=null, anchored=false, IDs=21032,21262,21263,21264,21265,21714,21261
MISSING Area: sourcePath=sourceProjectC, targetPath=null, anchored=false, IDs=22564,20744,21734,21479,18434
MISSING Iteration: sourcePath=sourceProjectB\Sprint 2 - 2025, targetPath=null, anchored=false, IDs=21032,21262,21263,21264,21265,21714
MISSING Iteration: sourcePath=sourceProjectB, targetPath=null, anchored=false, IDs=21032,21262,21263,21264,21265,21714,21261
MISSING Iteration: sourcePath=sourceProjectB\Sprint 2, targetPath=null, anchored=false, IDs=21032,21262,21263,21264,21265,21714,21261
MISSING Iteration: sourcePath=sourceProjectB\Sprint 3, targetPath=null, anchored=false, IDs=21032,21262,21263,21264,21265,21714,21261
MISSING Iteration: sourcePath=sourceProjectB\Sprint 1 - 2025, targetPath=null, anchored=false, IDs=21032,21262,21263,21264,21265,21714
MISSING Iteration: sourcePath=sourceProjectB\Sprint 3 - 2025, targetPath=null, anchored=false, IDs=21032,21262,21263,21264,21265,21714
MISSING Iteration: sourcePath=sourceProjectC, targetPath=null, anchored=false, IDs=22564,20744,21734,21479,18434
Missing Iterations in Target preventing progress, check log for list. To continue you MUST configure IterationMaps or AreaMaps that matches the missing paths..

was reading your comments and created the ITERATION and MAPS on the target devops and mapping using but that did not help

"CommonTools": {
				  "TfsNodeStructureTool": {
					"Enabled": true,
					"Areas": {
					  "Filters": [],
					  "Mappings": [
						{
						  "Match": "sourceProjectB([\\\\]?.*)$",
						  "Replacement": "targetProjectA"
						},
						{
						  "Match": "sourceProjectC([\\\\]?.*)$",
						  "Replacement": "targetProjectA"
						}
					  ]
					},
					"Iterations": {
					  "Filters": [],
					  "Mappings": [
						{
						  "Match": "sourceProjectB$",
						  "Replacement": "targetProjectA\\$1"
						},
						{
						  "Match": "sourceProjectC([\\\\]?.*)$",
						  "Replacement": "targetProjectA\\$1"
						}
					  ]
					},
					"ShouldCreateMissingRevisionPaths": true,
					"ReplicateAllExistingNodes": true
				  }
			

[satano]

@oipolloi It seems that you have incorrect regexes for iterations. I am sure, at least the first one is wrong, because regex sourceProjectB$ matches any string that ends with "sourceProjectB" – I believe, this is not the case you want. I am writing this completely just from my head, but you probably need something like this:

{
  "Match": "^sourceProjectB(\\\\.*)?$",
  "Replacement": "targetProjectA$1"
}

And the same for sourceProjectC.

It would help if you provide some of the source iterations and how would you like them to have in target.