"Live" doesn't mean "no planning," and it doesn't mean "everything moves." This is a repository migration with strict prerequisites, a few hard limits and a hybrid option for Boards and Pipelines. Here is what you need to know before you start.
Who can use it (and who can't)
The source and target boundaries are narrow:
- ELM supports migrations only from Azure DevOps Services to GitHub Enterprise Cloud with data residency. Azure DevOps Server users must first move to Azure DevOps Services.
- The target enterprise (an
<enterprise>.ghe.comaddress) must already exist. The target repository name must not already be in use. - Microsoft's preview announcement gave a simple test. A ghe.com URL means data residency, which ELM supports. A github.com URL means standard Enterprise Cloud, which ELM did not support at preview.
- Microsoft's launch-day Azure DevOps blog says GitHub Enterprise Importer remains the supported path for standard GitHub Enterprise Cloud.
If you are on github.com or GitHub Enterprise Server, ELM is not your tool today.
How the migration works
ELM runs a staged workflow. The Microsoft documentation describes these stages:
- Validation. Pre-migration checks confirm the repository is ready.
- Initial and incremental sync. ELM syncs changes using incremental sync and delta tracking, so teams can keep working in Azure DevOps until cutover.
- Cutover. The documentation says to plan for a brief read-only window, typically under 30 minutes for most repositories. That is a typical figure, not a guarantee.
During the initial sync, Azure DevOps stays fully writable. GitHub is not yet the system of record, and the target repository is automatically set to private.
What moves and what stays behind
Migrates:
- Git source with full commit history
- Branches and tags
- Pull request metadata, including titles, descriptions, source and target branches, and comments
- Pull request user history
- Branch policies, converted to GitHub branch rulesets
Microsoft's documentation lists Git LFS objects as migrated. An earlier revision marked LFS as a future item, so check the current page for your own setup.
Does not migrate:
- Work items
- Pipeline definitions
- Releases
- Wikis
- Test plans and results
- Azure Artifacts
There is a pull request catch too. ELM migrates active and merged pull requests, plus those with available branch history. Abandoned pull requests with deleted branches aren't migrated.
The hybrid option: Boards and Pipelines
GitHub's announcement says ELM can create the Azure Boards connection and rewire Azure Pipelines to the migrated repository. Work items and pipeline definitions stay in Azure DevOps. That is a wiring convenience, not a data migration.
Microsoft's setup documentation adds these details:
- Boards. The Azure Boards GitHub app must be installed on the target organization first. After the connection exists, teams can link work items from GitHub pull requests with
AB#<workItemId>. - Pipelines. Rewiring needs a pipeline service connection. You can use automatic discovery or choose pipelines manually.
- A discovery gap. The documented
az pipelines list --repositoryquery returns only pipelines whose default trigger repository is the source. Pipelines that reference the repo through a resource, template or checkout step may not appear. Add those IDs yourself. - Cutover review. In the manual flow, you can review and approve cutover from the CLI. Approval requires acknowledging pipeline verification, or accepting a stated number of unprocessed items.
Prerequisites checklist
- Agent. You need a self-hosted Linux agent, online for the whole migration. Windows and macOS agents aren't supported. Microsoft suggests running the agent as a service for long migrations or off-hours runs.
- CLI. You need the Azure DevOps CLI extension, version 1.0.11 or later.
- Permission. The operator needs the "Enterprise Live Migrations: Manage Migrations" permission on the repository.
- Token and service connection. A GitHub Enterprise admin creates the personal access token and the service connection. Microsoft's documentation is inconsistent on scopes. The overview and one prerequisites revision list
repo,workflow,read:org,read:userandadmin:enterprise. The start-migration page and the portal flow citerepo,admin:organddelete_repo. Follow the current page for the interface you use. - Network. Firewall rules must let the agent reach dev.azure.com and the GitHub endpoints.
Treat the token as a secret. Microsoft advises storing it only in the service connection, setting a short expiry and rotating it after migration. It must stay valid for the whole migration, which can run up to 21 days.
Limits that can derail a migration
Validation fails, and the migration can't start, if you hit any of these:
| Check | Threshold |
|---|---|
| Single file in history | Over 400 MB |
| Push pack size | Over 2 GB |
| Branch or tag name length | Over 255 bytes |
Two clocks also run:
- A successful validate-only run is good for 24 hours. After that you must rerun validation.
- Cutover must finish within 21 days of the initial sync starting. Otherwise you complete or cancel it, or restart.
Microsoft's manual cleanup list also mentions pull requests with 10,000 or more files. The fixes are to move large files to Git LFS, rewrite history, or rename the offending refs. None of that is quick on a legacy monorepo, so run validate-only early.
Cost, security and audit
- Cost. ELM itself is free, per Microsoft's overview. The only potential cost is Azure Pipelines parallel-job capacity beyond your included allowance. ELM queues one job at a time and usually waits 30 to 60 minutes between jobs.
- Transit. Communication between Azure DevOps, the agent and GitHub uses TLS-encrypted HTTPS.
- Retention. Microsoft says ELM keeps only operational metadata: repository IDs, status, validation results, error messages and audit events. It says it does not retain repository contents, commit data or the token after migration.
- Audit. Lifecycle events appear in the Azure DevOps audit log. Go to Organization settings > Auditing and filter for Enterprise Live Migrations.
Documentation caveats
Microsoft's pages don't fully agree on scale and interface. One revision mentions multi-repository batches. The current overview says you start and manage one migration at a time from the CLI, and uses the portal for one-time setup. The portal's "Start a new migration" flow lets you select several repositories. Don't plan around a batch size until you confirm it against the live documentation for your tenant.
Practical advice
- Run
--validate-onlyfirst on a non-critical repository. - Inventory pipelines that reference the repo indirectly, and hardcoded Azure DevOps URLs in scripts and tooling.
- After cutover, verify branches, tags, history and pull requests, adjust the migrated rulesets, and set up GitHub team access.
- Decide whether Boards and Pipelines stay in Azure DevOps for now. Microsoft explicitly supports that hybrid model.
Bottom line
ELM is a welcome step for teams that need to move repositories without freezing development. Its scope is narrow: ghe.com targets only, Services only, repositories only. If you fit that profile, the 24-hour and 21-day windows and the file-size checks are the details to plan around.
References
- Enterprise Live Migrations from Azure DevOps generally available GitHub Changelog · 2026-11-19T18:50:57+00:00
- azure-devops-docs/docs/repos/enterprise-live-migrations/overview.md at main · MicrosoftDocs/azure-devops-docs · GitHub github.com
- Prerequisites for Enterprise Live Migrations (ELM) - Azure DevOps learn.microsoft.com