azure devops - Migrating TFS 2010 to Visual Studio Online

Question

I've installed the OpsHub VSO Migration Utilty and I'm trying to migrate one of our smallest projects as a test.

Having created a new matching project in VSO the migration validation fails on the template mis-match.

The existing TFS 2010 project is based on the MSF for Agile Software Development v5.0 template and the new VSO project is MSF for Agile Software Development 2013.3

As far as I'm aware, neither of these templates have been customised.

For each work item types the mismatched fields are:

• RelatedLinkCount
• AreaID
• AttachedFileCount
• HyperLinkCount
• ExternalLinkCount
• IterationID

Installed version of the utility is v1.1.0.005

Any help would be gratefully received.

Answer 1

Between TFS 2005/2008 to TFS 2010, the process templates were updated to add an additional space in the display name of each of the fields you mentioned. Since that's the case, you can take some easy steps for a workaround and then re-run the OpsHub Visual Studio Online Migration Utility.

You'll want to use the witadmin.exe tool and specifically the changefield option. Here are the steps you'll want to take to change the display names of each of the fields to include the spaces:

witadmin.exe changefield /collection:http://tfs.contoso.local:8080/tfs/DefaultCollection /n:System.RelatedLinkCount /name:"Related Link Count"
witadmin.exe changefield /collection:http://tfs.contoso.local:8080/tfs/DefaultCollection /n:System.AreaId /name:"Area ID"
witadmin.exe changefield /collection:http://tfs.contoso.local:8080/tfs/DefaultCollection /n:System.AttachedFileCount /name:"Attached File Count"
witadmin.exe changefield /collection:http://tfs.contoso.local:8080/tfs/DefaultCollection /n:System.HyperLinkCount /name:"Hyperlink Count"
witadmin.exe changefield /collection:http://tfs.contoso.local:8080/tfs/DefaultCollection /n:System.ExternalLinkCount /name:"External Link Count"
witadmin.exe changefield /collection:http://tfs.contoso.local:8080/tfs/DefaultCollection /n:System.IterationId /name:"Iteration ID"

Give those a try and I hope it works out for you as a workaround!