Migrations begin without locking the Azure DevOps repository, with changes continuously synchronized to GitHub while developers keep working. When ready, teams can schedule a cutover to complete the transition – with only a brief downtime window, typically under 30 minutes. This means no extended freeze periods, no multi-day outages – just a controlled, predictable transition that fits into your operations. Teams can migrate at their own pace, without coordinating complex, high-risk \u201call-at-once\u201d migrations.<\/p>\n
\ud83e\udea7 Sign up for the Preview<\/h2>\n
ELM currently supports migrations to GitHub Enterprise Cloud with data residency. A script-based migration experience is available today, with a UI-based experience coming soon to provide a more streamlined end-to-end workflow. We expect to remain in limited public preview over the next couple of months as we continue refining the experience, adding new features, and incorporating customer feedback. Your input is vital to making this experience successful.<\/p>\n
If you are interested in participating in the preview, you can sign up today<\/a>. We will follow up with all the information you need to get started.<\/p>\n ELM follows a simple, staged workflow:<\/p>\n During most of the process, Azure DevOps remains fully writable, so teams can keep working without interruption.<\/p>\n For detailed guidance, learn more here<\/a>.<\/p>\n Enterprise Live Migrations provides a practical path for organizations moving to GitHub Enterprise Cloud with data residency:<\/p>\n Learn<\/a> more and sign up<\/a> for preview.<\/p>\n","protected":false},"excerpt":{"rendered":" Over the last several years, we\u2019ve encouraged customers to move their repositories from Azure Repos to GitHub to take advantage of the latest AI-powered and agentic development experiences. For many enterprise teams, however, migrating at scale comes with real constraints. Traditional approaches can require extended downtime – sometimes days – which isn\u2019t acceptable for teams […]<\/p>\n","protected":false},"author":179849,"featured_media":72787,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[224,1],"tags":[7262,7318,7294],"class_list":["post-72788","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-azure","category-devops","tag-azure-devops","tag-azure-repos","tag-github"],"acf":[],"blog_post_summary":" Over the last several years, we\u2019ve encouraged customers to move their repositories from Azure Repos to GitHub to take advantage of the latest AI-powered and agentic development experiences. For many enterprise teams, however, migrating at scale comes with real constraints. Traditional approaches can require extended downtime – sometimes days – which isn\u2019t acceptable for teams […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/posts\/72788","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/users\/179849"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/comments?post=72788"}],"version-history":[{"count":1,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/posts\/72788\/revisions"}],"predecessor-version":[{"id":72857,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/posts\/72788\/revisions\/72857"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/media\/72787"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/media?parent=72788"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/categories?post=72788"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/tags?post=72788"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}\ud83e\udd16 How ELM works<\/h2>\n
\n
![\"Screenshot](\"https:\/\/devblogs.microsoft.com\/devops\/wp-content\/uploads\/sites\/6\/2026\/06\/Screenshot-2026-06-01-182500-1024x468.webp\")
<\/a><\/p>\n![\"Screenshot](\"https:\/\/devblogs.microsoft.com\/devops\/wp-content\/uploads\/sites\/6\/2026\/06\/Screenshot-2026-05-20-at-10.47.43-AM-1-1024x535.webp\")
<\/a><\/p>\n\ud83d\udcac Conclusion and key takeaways<\/h2>\n
\n