Azure DevOps to GitHub Enterprise: The Great Migration

Nobody migrates because the old tool stopped working. They migrate because the new one has something they want, and then spend six months discovering what the old one was quietly doing for them. Moving from Azure DevOps to GitHub Enterprise looks like a tooling swap right up until you open the box. Then it turns out to be a set of architecture decisions wearing a tooling swap as a disguise: where identity lives, what "a repo" means now, who owns the runners, and what you're actually willing to leave behind. This session is a field guide rather than a war story. We'll work through the migration as an engineering problem: the architectural decisions, the tooling, and what the conversion tools actually tell you before you commit. Along the way: - The real reasons teams migrate (yes, AI is one of them) - A capability-by-capability map of what migrates cleanly, what needs manual rework, and what's better left where it is - Translating pipelines to Actions when both platforms use YAML in roughly the way that Java and JavaScript both contain the word "Java" - The architectural forks you'll hit either way: org and repo topology, identity and permissions, runner strategy, and where your build history actually needs to live - Change management, so the transition produces adoption rather than a small, tool-related uprising. Uprisings are technically a form of engagement, but not the kind you want in the retro. You'll leave with a decision framework, a realistic capability map, and a much clearer sense of which parts of this you can safely defer. Also a renewed appreciation for the automation that keeps the SDLC wheels turning. Somewhere, a platform team is already evaluating the next platform.