Azure DevOps to GitHub Enterprise migration
I have migrated pipelines from Azure DevOps to GitHub Enterprise. The hard part is rarely the YAML. It's secrets, permissions, service connections, and keeping teams shipping during the move.
How the engagement runs
- Plan. Take stock of repositories, pipelines, service connections, secrets and permissions. Decide what moves as it is, what gets rewritten and what gets retired.
- Pilot. Move one or two real pipelines to GitHub Actions end to end, including secrets and deployment to Azure.
- Cutover. Move the rest in batches, with a way back. The old pipelines stay until the new ones have proven themselves.
What you get
- Pipelines running on GitHub Actions.
- A runbook your team can follow for anything left to move.
Let's talk
Planning a move to GitHub? Tell me how many pipelines you have.