Fig. 01 · Answer
Is cloud repatriation worth it - or should we optimize first?
CTOs and CFOs whose cloud bill is growing faster than revenue.
The short answer
Optimize first, in most cases: rightsizing, commitments, and killing the named villains (egress, idle capacity) often recover meaningful spend without migration risk. Repatriation earns consideration for stable, well-understood workloads at material spend, run by teams with real infrastructure capability - and the honest model prices the ops staffing you take on.
What informs this answer
Selected results from related operator-led engagements, by industry and scale:
- 28,000-user migration with zero downtime
What to ask next
Which workloads make good repatriation candidates?
Stable, predictable, well-understood ones - steady compute and large, slow-changing storage. Volatile or fast-evolving workloads keep the cloud's elasticity premium worth paying.
What does the repatriation math need to include?
Hardware plus its refresh cycle, colocation or facilities, the operations staffing you now own, egress to get data out, and a parallel-run period. If the case only works with those lines at zero, it is not a case.
Answered by Justin Leader · Human Renaissance · Updated 2026-04-30 · Research methodology
