How to continue on error?

[kaburkett]

Hi, I am hitting an error during work item migration that is causing the processor to enter a failed state and stopping the migration.

I am wondering, how can I get the migration to continue and skip items which cause an error? We have 62K items and the tool made it to only 1K, so I am likely going to run into this or a similar issue with other work items.

Thank you!

[ovebastiansen]

That is very much depedent on what type of error you are getting? And with continue you would end up with dataloss, and in most cases that is not acceptable, especially if the problem is related to a missing Area/Iteration path. The last one you can simply fix with mapping to a new existing value, or add the missing Path in the target temporary while doing the migration.

If it is a crash on save with invalid values you get a list out of the fields that you need to look at. And depending on that you can add mappings that would make the migration continue.

[kaburkett]

Hi @ovebastiansen thanks for your quick response.

In this specific case the error is due to a text field being longer than the limit.

Microsoft.TeamFoundation.WorkItemTracking.Client.VerbatimMessageException: 
TF401262: 
Value of long text field Microsoft.VSTS.TCM.Steps exceeds the maximum allowed length of 1000000. ---> 
System.Web.Services.Protocols.SoapException: 
TF401262: 
Value of long text field Microsoft.VSTS.TCM.Steps exceeds the maximum allowed length of 1000000.

[kaburkett]

Personally I don't care about data loss if there are edge cases where we have done things unsupported. It's easier to write items off as a loss than to manipulate things in an odd manner. As long as the log tells me what fails and why, which it does fine, I just would like it to continue through the whole migration first if possible then we can resolve issues if needed one by one instead of halting migration for simple things like truncate of a text field

[Yozya]

I'm also interested on it. Have the same issue. I have too much items and solve errors after the migration sounds pretty good.

[kaburkett]

I got lucky that all my errors were in test case items and I was able to talk with the team and we decided to not migrate any test cases in order to avoid the errors. This strategy worked for us beautifully. However, it would have been nice to migrate all the un-problematic test cases and drop the problem ones... but, we are working fine in DevOps without historic test cases.