Reducing the number of DevOps tools in use often means one or more tools must be decommissioned. This can be difficult since often, these tools are used to implement governance and compliance, as required by laws and regulations. In practice, this means that one of two things can be done:
- Old tools are not completely decommissioned but just no longer used, to maintain the change history.
- History must be migrated to the new tools as well before the old tools can be decommissioned.
When choosing to do a migration, there are four ways to go about this:
- Azure DevOps Server to Azure DevOps Services migration
- Big-bang migration
- Synchronization
- Rebuilding
Azure DevOps Server used to be called Team Foundation Server (TFS). Older versions of TFS need to be upgraded to one of the latest versions of Azure DevOps Server before they can be imported into Azure DevOps Services. The import service always supports the latest two versions of Azure DevOps Server
All three of these are detailed in the following sections.