One migration weekend feels decisive. It also compresses every unknown dependency, untested control and recovery decision into the same few hours. Part three of the series: how controlled waves replace the single leap, why movement patterns have to follow data behaviour, and what evidence must exist before anyone can say go.
An inventory says what exists. A migration plan must say what should happen to it and why. Why moving an unexamined estate relocates its operating debt, and why preserve, retire or redesign has to be decided - by someone named - before anything moves.
A model can be finished, evaluated and approved - and still never reach production. The seven capabilities beneath every production model, the eight failure states that compound, and a diagnostic that finds the gap before a platform decision hides it.
Machine data sits in a historian, production in the ERP, quality and maintenance elsewhere - and by the time it's pulled together the issue has already affected production. How Azure Event Hubs and Databricks turn live operational events into insight teams can act on.
Most finance teams still lose the first few days of every month to chasing files and copying numbers between spreadsheets. We break down why it happens, and the Microsoft setup that removes the manual layer for good.
Metro Bank's CEO called Power BI "a bank in his pocket." We break down how the UK's first new high street bank in over a century used data to transform its operations, and the lessons any organisation can apply.
Part four of From Legacy to Intelligent: the tenant, capacity, domain, workspace, identity and deployment boundaries that turn a migration wave into a supported production capability.
What it actually takes to move your organisation's data from scattered Excel files into a production-ready Microsoft Fabric lakehouse.