Preserving Changesets and Work Item Revisions during Migration from TFS 2013 to Azure DevOps
Question
Your company is currently making use of Team Foundation Server 2013 (TFS 2013), but intend to migrate to Azure DevOps.
You have been tasked with supplying a migration approach that allows for the preservation of Team Foundation Version Control changesets dates, as well as the changes dates of work items revisions. The approach should also allow for the migration of all TFS artifacts, while keeping migration effort to a minimum.
You have suggested upgrading TFS to the most recent RTW release.
Which of the following should also be suggested?
Answers
Explanations
Click on the arrows to vote for the correct answer
A. B. C. D.B
In Phase 3 of your migration project, you will work on upgrading your Team Foundation Server to one of the supported versions for the Database Import Service in
Azure Devops Services.
The suggested approach to upgrade TFS to the most recent RTW release is a good starting point to migrate to Azure DevOps. However, this does not ensure the preservation of Team Foundation Version Control (TFVC) changesets dates and the changes dates of work items revisions during the migration process. Therefore, a specific approach is required to ensure the preservation of these dates.
Option A, Installing the TFS Java SDK, is not relevant in this scenario as it is used to develop applications using the TFS API and integrate them into Java-based environments.
Option B, Using the TFS Database Import Service to perform the upgrade, is a valid option to migrate TFS to Azure DevOps. This approach involves taking a backup of the TFS databases and restoring them to Azure DevOps, after which the TFS Database Import Service can be used to perform the migration. This approach preserves the dates of the changesets in TFVC and the changes dates of work item revisions. However, this approach may require a significant amount of migration effort and time.
Option C, Upgrading PowerShell Core to the latest version, is not relevant to the migration process as PowerShell is not used to migrate TFS to Azure DevOps.
Option D, Using the TFS Integration Platform to perform the upgrade, is not a recommended option as the TFS Integration Platform has been deprecated and is no longer supported by Microsoft.
Therefore, option B, Using the TFS Database Import Service to perform the upgrade, is the best option to migrate TFS to Azure DevOps while preserving the dates of the changesets in TFVC and the changes dates of work item revisions, and keeping the migration effort to a minimum.
