> Technologically it's somewhere between messy and impossible. Now you no longer have Google's build stack or monorepo. You have to rewrite everything. You can't just move some VMs to a cloud provider of choice
You could give a copy to both successors. Probably would want to excise some of the repo on both sides, but build tools for sure would be fine to have a second copy. There's no need to rewrite everything, especially if Parent and Child are barred by court decree from entering overlapping businesses.
For things that really need a single corporate owner, you could potentially spin that off as well and have both successors contract from that one or depending on the terms of separation have a joint partnership.
Hosting would be messy, yes. But somehow the tech world outside google manages to run systems without Google tools. It would be an adjustment, potentially a large adjustment and take a lot of hours.
> You need to hire all the roles that weren't part of that organization before (HR, legal, compliance, etc.)
> You need to register this new entity in all the countries it operates and/or has employees in
This costs money, people, and time, but it's straight forward. HR and legal would likely need some additional people, but likely you assign the people who work with the spinoff business to the spin off corporation and then back fill as needed.