Skip to main content
This document provides an overview of Warp’s capabilities for migrating data from Azure DevOps Services to GitHub products. Warp does not provide a migration path for Azure DevOps Server, only Azure DevOps Services. To migrate from Azure DevOps Server, you’ll need to migrate to Azure DevOps Services first.

​
Repository Data

Warp includes built in support for data migrated by GitHub Enterprise Importer, including:
  • Repository contents and Git history,
  • Pull requests, including
    • User history,
    • Work item links, and
    • Attachments
  • Branch policies
    • User-scoped branch policies and cross-repository branch policies are not included.
For specific information about the limitations on the types and size of data that can be migrated, refer to the Limitations page in this section.

​
Azure Pipelines

Warp is capable of “rewiring” Azure Pipelines associated with repositories in your source Azure DevOps environment. Rewiring modifies the pipeline to associate it with the migrated copy of your repository in GitHub, rather than the original repository in Azure DevOps. Rewiring enables a flexible path to GitHub adoption, enabling further migration processes (for instance, re-creating your existing pipelines with GitHub Actions) to proceed incrementally. Your team can enjoy the experience of hosting their code and development process on GitHub, while retaining the flexibility to continue using their existing pipelines until they’re ready to replace them with Actions. To facilitate the pipeline rewiring process, Warp will automatically share and normalize service connections for the Azure Pipelines GitHub App.

​
Azure Boards

If you have installed and connected the Azure Boards GitHub App to your destination GitHub Organization, Warp can configure this integration for your migrated GitHub repositories with the /integrate-boards slash command. In addition to integrating Azure Boards, Warp is also capable of configuring GitHub’s Autolink References feature with the /autolink-work-items slash command. When this integration is enabled, references to Azure Boards work items in issues, pull requests, commit messages, and release descriptions will automatically become clickable hyperlinks to the work item they reference.

​
Post-Migration Tasks

Warp supports a variety of utility slash commands for Azure DevOps to automate common tasks like locking or disabling the original repository when a migration has been completed. These are listed in the Azure DevOps section of our slash command documentation. Warp additionally supports slash commands for common post-migration tasks such as adding teams in GitHub to a repository with specific permissions. Documentation for these commands can be located in our slash commands guide.