It was understanding the infrastructure we already had. There was no documentation from the team that had originally built the self-hosted runner setup, so I had to investigate the environment, ask questions and speak to engineers who still knew how it worked. That experience shaped how I think about platform migrations.
Before you can decide what to move, you need to understand what exists, who depends on it and what each workload needs to keep working. Start With Discovery, Not the Migration Plan When infrastructure has been running for years, it is easy to assume that its design and purpose are understood. But people move teams, decisions go undocumented and configurations can outlive the reason they were introduced. I had to build up an understanding of the existing runner infrastructure by exploring it and speaking to people with historical knowledge.
