Microsoft has announced that Enterprise Live Migrations (ELM) from Azure DevOps Services to GitHub Enterprise Cloud with data residency are now generally available. For engineers who manage source control, CI/CD pipelines, or work tracking, the change means a supported path to relocate codebases without halting development.
Feature Overview
ELM provides two entry points: a guided wizard inside the Azure DevOps portal and a scriptable option via the Azure DevOps CLI. Both approaches include pre‑migration validation and lifecycle tracking, allowing teams to surface configuration issues before the final cutover.
Migration Mechanics
During the migration window, ELM continuously synchronises commits, branches, tags, and pull‑request artifacts (titles, descriptions, comments, and user activity) from Azure DevOps to the target GitHub repository. This live sync lets developers continue to push changes to Azure DevOps while the migration proceeds. When the team decides the repository is ready, a brief cutover operation finalises the move, after which the GitHub repo becomes the source of truth.
Impact on Tooling and Policies
Branch policies defined in Azure DevOps are translated into GitHub branch rule sets, preserving protection mechanisms such as required reviews or status checks. Additionally, ELM can automatically create an Azure Boards connection and rewire existing Azure Pipelines to point at the newly migrated GitHub repository, reducing manual re‑configuration. Work items and pipeline definitions remain in Azure DevOps, so teams retain their tracking and build definitions after cutover.
Related CloudNinjas coverage: DevOps.
What This Means For Practitioners
Practitioners should treat ELM as a migration framework rather than a one‑off export tool. Evaluate the pre‑migration validation reports to confirm that branch policies, pull‑request metadata, and data residency requirements are correctly mapped. Plan the cutover window to align with low‑traffic periods, but remember that the continuous sync reduces the need for a long downtime. After migration, verify that Azure Boards connections and Azure Pipelines references have been updated and that GitHub branch rules enforce the same protection levels as before. Finally, monitor the lifecycle tracking logs for any sync anomalies during the transition period.


