Ten public modernization stories, side by side: where each started, how long it took, how much was rebuilt rather than moved, and what changed. Six patterns repeat in almost all of them, and each one applies to a company far smaller than these.
Book a free 30-minute call. You'll leave knowing what we'd do first and roughly what it costs, whether or not you hire us.
They started where the old constraint hurt most and the result was visible: Home Depot's warehouse capacity, Lowe's e-commerce, Netflix's single database. Early, visible wins funded the rest.
The core was rebuilt, not moved. Capital One rebuilt 80%; Netflix refused to lift and shift; Amazon chose a new database per workload. Rehosting was used for the long tail, never for the systems that differentiate.
The riskiest systems moved last. Netflix moved billing and customer data at the end, once the platform and team were proven.
A platform made the right way the easy way: Lowe's Carbon, Liberty Mutual's CDK patterns, Target's Unimatrix, Walmart's common layer. Adoption followed convenience, not mandates.
It was a people program. Capital One grew to about 11,000 technologists; Home Depot and Lowe's each announced plans to hire a thousand or more engineers; Amazon retrained its DBAs. None bought a transformation.
Cost was a result, not the reason. Netflix called lower cost per stream a welcome side benefit. The stated reasons were reliability, speed and capacity.
Pick the one system whose limits the business feels most, and modernize it properly first.
Retire and rehost the rest quickly so the old environment shrinks while the important work happens.
Build a small paved road (two or three templates for your common service shapes) before the second project, not after the tenth.
Move the systems that hold money and customer data last, with parallel runs.
Budget for people: training, a platform owner, and time for teams to learn the new way.
Once a month: what changed in tech that month and what it means for you, from cloud and AI to security and the tools you build with. Every item links to its source. No sales pitch, unsubscribe in one click.
Book a free 30-minute call about it. Bring your setup and your bill; you'll leave knowing what we'd do first and roughly what it costs, whether or not you hire us.
Or keep reading
How The Home Depot Modernized: Data Warehouse First, SAP to the Cloud, and $11 Billion Behind It
The Home Depot moved a 450 TB on-premises warehouse to a cloud warehouse that now holds more than 15 PB, moved its SAP estate to the cloud from 2017, and funded it as part of an $11.1 billion three-year plan. What they did, in what order, and the lessons that apply on any cloud.
Read
How Capital One Left Eight Data Centers for AWS, and What the 2019 Breach Taught Everyone
Capital One was the first US bank to announce going all in on the cloud, closing eight data centers by 2020 and rebuilding 80% of about 2,000 applications as cloud native. What changed in delivery speed and reliability, and the security lesson from 2019 that changed EC2 for every customer.
Read
As of October 25, 2026. Provided as is, for general information, and accurate to the best of our knowledge on the date shown. Not legal, compliance, tax, financial or other professional advice. Prices, limits and vendor services change; check current vendor documentation before relying on anything here. Terms of use.