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?
- A. Installing the TFS Java SDK
- B. Using the TFS Database Import Service to perform the upgrade. Correct
- C. Upgrading PowerShell Core to the latest version.
- D. Using the TFS Integration Platform to perform the upgrade.
Explanation
The only Microsoft approach that preserves TFVC changeset dates and work item revision dates and moves all artifacts with minimal effort is the full-fidelity database import (the TFS Database Import Service, now the Azure DevOps Data Migration Tool), after first upgrading the server to one of the two most recent releases. API-based tools such as the TFS Integration Platform replay changes, so they do not keep original changeset dates and lose fidelity. The Java SDK and PowerShell Core are irrelevant to the migration.
