Data, Delivered

Every cloud migration business case reads like a holiday brochure. Glossy infrastructure savings, confident cost reductions, faster time-to-insight. What nobody includes is the bill that arrives once you are actually living there. The operational tax. After 25 years in data and transformation and four enterprise cloud platforms built from the ground up, I can tell you: the migration is the easy part. What comes next is where cloud ROI is actually made or lost.

Technical debt rarely arrives as a crisis. It starts small, a quick fix, a temporary workaround, a compromise no one plans to keep. Over time, those decisions accumulate and quietly become the foundation of your data platform. Like hot cross buns appearing earlier each year, what once felt unusual becomes normal, until you realise it’s everywhere.

For decades, project success has been defined by the Iron Triangle: on time, on budget, to scope. But in modern software, especially in agile and AI-driven environments, scope evolves as learning unfolds. This article revisits why the traditional model struggles in discovery-led work, and explores a more honest definition of success based on value, adaptability, and sustained delivery rather than rigid constraint compliance.

Lift and shift is not about avoiding change, it is about sequencing it. Keeping the same data schema during migration preserves contracts, enables clean reconciliation, and protects trust. Redesigning the model at the same time increases risk and ambiguity. Migrate first for behavioural parity, then modernise deliberately.

Modernising a data platform is not a clean rebuild, it is a transition carried out while the business continues to operate at full speed. The greatest risk is not downtime, but divergence in the numbers that erodes executive confidence. This piece explores how disciplined dual running, reconciliation, and capability-led migration protect trust while foundations shift.