Migration fails with "Object reference not set to an instance of an object."

[valenker]

When default-iteration-path or default-area-path do not exist on the target project migration fails with uninformative error message - "Object reference not set to an instance of an object."

Instead - migrator should validate default-iteration-path or default-area-path and display meaningful errors if they don't.

[obvioussean]

I debugged this, and it appears to be a VSTS issue. The migrator is just returning the error returned from the REST call. I'll dig further to see what I can fix on the VSTS side to handle this more gracefully.

[srivatsamarichi]

I get the same error too @sferg-msft

[obvioussean]

@SrivatsaMarichi To work around the issue, either clear the default-iteration-path and default-area-path properties or set them to the project name.

[srivatsamarichi]

@sferg-msft Yep, worked thanks!

[irzum]

just remove "default-iteration-path" and "default-area-path" properties migrator will detect the iterations and will do the migration according to the iterations automatically.