This page encompasses is based on the work our ninja team 's did to migrate 2 projects we brought over from TFS to DevOps. Please feel free to make edits, suggestions and improvements. Credit goes to (Also feel free to talk to Tibo (Unlicensed)/John Sewchand (Unlicensed) for doing the research and legwork on the first one, and leaving instructions to follow for subsequent migrations) if any questions).
Please see the note below as this has significant limitations. The ideal time to migrate to DevOps is likely at the beginning of a sprint when the content within your backlog items is minimal and the state of the majority of items is "New". It is not an easy task to perform if you have the need to migrate items that have already been worked on (eg. old sprints). Also note that the process for moving your code from TFS to DevOps is documented quite nicely here.
Instructions
NOTE: With this process you lose Iteration Path, Area Path, Assigned To, State, Reason, Effort, attachments, inline pictures and some other data. This will have to be updated manually if desired. Also, for Tasks, the Description and Comments are not uploaded, and for Bugs, the Repro Steps are not uploaded.
- 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).
- Selected 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!
| Info |
|---|
| If you're not seeing your Backlog Items in your team's Devops board, it means you likely have to update the "Area Path" and "Iteration" of the items you uploaded. As an example, when we migrated the CORAL application we created an Area Path called \CORAL and gave our team access to that Area Path. We updated all of the Backlog Items for CORAL to have this Area Path (this can be done in bulk). We also created an Iteration called Ninja Turtles (named after our team). Each of the Backlog Items was given this value for Iteration (again, in bulk) and our team was given access to this Iteration. Once this was done, the items showed up in our team's backlog. |
Related articles
| Filter by label (Content by label) | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...