...
- Export from TFS into Excel (https://docs.microsoft.com/en-us/azure/devops/report/excel/create-status-and-trend-excel-reports?view=azure-devops-2019)
In TFS, create a query of the items you would like exported. Here is the query we used for CORAL.
- In Visual Studio, open Team Explorer, Work Items and navigate to the query created in step 1a. Right-click and select "Open in Microsoft Excel". Save it. Done.
- Import to DevOps (https://docs.microsoft.com/en-us/azure/devops/boards/backlogs/office/bulk-add-modify-work-items-excel?view=azure-devops)
- Open a blank Excel sheet, hit the TEAM menu, then New List.
- Add the server/organization: eg. https://dev.azure.com/TCMarineSafetyOrg and click Connect.
- Enter user credentials (eg. john.sewchand@034gc.onmicrosoft.com).
- Select Input List.
- Hit the TEAM menu, Add Tree Level, select Parent-Child, then Convert. (Microsoft documentation about Tree Level and example)
- From the exported sheet, copy the values from the Work Item Type column into the new sheet.
- State and Reason automatically populate.
- Copy the Title 1 and Title 2 from the export sheet.
- Copy the remaining header values from the export sheet to the new one.
- Delete the duplicated Assigned To and Reason columns.
- Copy the data from the additional columns to the new sheet.
- Save the sheet and hit Publish.
- It may complain about Area Path, Iteration Path if they don't exist in Devops. Changethose to \.
- It may complain about Area Path, Iteration Path if they don't exist in Devops. Changethose to \.
- Open TFS and DevOps side by side, and manually move over any desired Attachements, Linked items, etc. that aren't covered by steps 1 and 2. This part is tedious!
...