> But for many companies, they don't want to have this problem around long-term. They do not want to long-term maintain migration tooling, they're the happiest

> But for many companies, they don't want to have this problem around long-term. They do not want to long-term maintain migration tooling, they're the happiest if the migration happens and they never need to think about anything related to it again. Treating $(subject) tool to be equivalent of day 2 ops, does the trick. What makes it viable to do it with a team of (say) 6 folks? Community driven core, adopted internally by this team. So is it mostly about mindset change, or it just really doesn’t have a place in org internal engineering team setups?