Done? none, I wouldn't do it. Undone after it failed, one, and helped some other people in others.

You are expecting people to act rationally in a way that will succeed. That's not how a lot of places out there operate.

▲

raw_anon_1111 12 hours ago | parent [-]

I have been either part of or opted out of well over a dozen - I have a policy of never leading “lift and shifts” (and never staff augmentation).

Once you actually sit down and come up with a project plan with your PMO, a cloud migration is hardly ever worth the effort unless the destination cloud provider is backing up a shit ton of money for not only operational credits but also for internal AWS Professional Services (where I worked when I was inside AWS) or an outside partner to help (current employer).

Hell even certain departments at Amazon would never go through the effort of migrating to AWS from the legacy CDO infrastructure.

The risk of regressions, the refactoring, the retraining, the politics, etc are hardly ever worth it.

	▲	12_throw_away 5 hours ago \| parent [-]
		> Once you actually sit down and come up with a project plan with your PMO [...] The risk of regressions, the refactoring, the retraining, the politics, etc are hardly ever worth it. You are entirely correct, of course ... except that much of the management class simply does not care about any of those things. Not to mention the sizable contingent of engineers will repeatedly get suckered by the pitch of "Just migrate all of your stuff to [shiny new thing] and all of your [reliable old thing] problems will go away" (a.k.a., "engineers with management potential")