Stop the Creation of Nodes (Iterations and Area Paths)?

[blakefosdick]

I ran a test migration limiting the number of items to migrate with the WIQLQueryBit setting. Nice, but every single Area Path and Iteration Path came over from source to the target. Regardless if they had anything to do with my query items or not.
So then, what seemed to happen was: 1. Created all these nodes. 2. Brought over my limited results of work items from the query, if the original node (iteration or area path) it used those, if not then it used my Regex Area/Iteration Maps config setting. (Not sure about this, but regardless it didn't always use my mapping).

My question is: Can I entirely prevent the creation of Source nodes in the Target?
Does the "ShouldCreateNodesUpFront" config setting accomplish this or will it still create those at some point in the process?

[MrHinsh]

Source noded missing in the Target will result in an inability to migrate. All expected nodes MUST exist.

If you turn ShouldCreateNodesUpFront off, which is the default, we create the nodes after we have gotten a full list of nodes from the system. If you also set ShouldCreateMissingRevisionPaths the system will output a list of all nodes from the source that do no exist on the target and then stop.

You can then use this data to create Area and Iteration maps to convert the nodes on the fly to new nodes in the target. Once mapped if you rerun the tool it will not list those new mapped nodes if valid. Continue the process until all nodes are mapped and the migration will start.

You can even create a regex that will match all nodes if you need.