The Virtual SAP Cutover Playbook: A FTSE 100 HANA-on-Azure Go-Live

Jeet Poptani, Chief Transformation Officer at AumentoAI, revisits the operational playbook behind a FTSE 100 SAP HANA-on-Azure go-live delivered entirely under lockdown — and what's easier, and what isn't, doing the same thing in 2026.

In mid-2019 a UK retail giant began one of the most significant SAP transformations the sector had seen: upgrading its ERP, migrating from an Oracle-based ECC database to in-memory SAP HANA, and moving the entire SAP Business Suite to Microsoft Azure — as one single cutover, to limit business disruption. In March 2020, halfway through delivery, the programme lost the ability to run any of it face to face. This is the operational playbook that got it live anyway, and what I'd change running the same programme today.

The technical scope, and why it had to move as one step

Three transformations were bundled into a single cutover rather than sequenced: an ERP upgrade to accommodate new business features, the database migration from Oracle to in-memory SAP HANA, and the infrastructure migration of the entire SAP Business Suite to Azure. Splitting these into separate projects would have meant three rounds of business disruption instead of one — the complexity was real: seven SAP systems in scope, high data volumes from BI/BW, a live cache issue in APO, and more than fifty interfaces (EDI, banking and others) to repoint. More than 100 IT team members were working the cutover, and the commercial stakes were concrete: every hour of downtime beyond the planned window carried an average revenue impact of £1.5 million.

The strategy to achieve results

None of the standard programme playbook survived contact with a national lockdown unchanged. What replaced it, and what I'd still recommend as a generalisable framework for any large-scale, high-stakes SAP cutover:

• Build a virtual command centre before you need it. A 24/7 video hotline for reporting progress and issues turned a distributed, remote team into something that behaved like a single war room, with three clearly defined escalation paths — C-suite executive briefing, business/SME communications, and IT delivery — so the right issue reached the right decision-maker without a chain of hand-offs.

• Run a full rehearsal of the cutover, not a partial one. Simulating the exact sequence of the go-live weekend, at the scale it would actually run at, surfaced the problems that a phased or partial test would have missed — including, in our case, remote-access infrastructure that hadn't been sized for every user logging in from home simultaneously.

• Deliberately shrink governance for the cutover window. Streamlining the number of governance forums, running a lean stakeholder map, and having one clear communications and news-broadcasting team reduced the coordination overhead exactly when speed of decision-making mattered most.

The result: the entire SAP Suite went live on HANA in Azure within the timeline agreed with the business, with a 100% master data count reconciled before and after the migration.

The technical know-how this actually requires — then and now

In 2020, several of the hardest problems in this programme were solved with manual effort that 2026 tooling now handles natively. That's worth being explicit about, because it changes what “technical know-how” means for a programme like this today:

• SAP HANA architecture and migration mechanics — understanding in-memory data models and the specific migration path from an Oracle-based ECC estate, which hasn't fundamentally changed.

• Azure infrastructure sizing and remote-access scaling — in 2020, this meant renegotiating supplier capacity mid-programme after discovering the landscape couldn't handle full remote login load. In 2026, Azure Center for SAP solutions gives you a Virtual Instance for SAP with real-time system health, infrastructure monitoring and documented best-practice quality checks before you ever reach cutover weekend — the kind of visibility we had to build ourselves by hand five years ago.

• Interface and integration remediation at scale — repointing 50+ EDI, banking and other interfaces during a single cutover window still requires the same rigorous, sequenced testing discipline it always has.

• Programme command-and-control design — the virtual command centre, rota system and escalation paths are organisational technology, not software, and they remain the difference between a cutover that holds and one that doesn't, regardless of how good the underlying platform tooling gets.

Programmes facing the SAP ECC 2027 maintenance deadline are about to run cutovers of comparable complexity, on compressed timelines, across a market where delivery talent is in increasingly short supply. The tooling has improved. The discipline this playbook describes hasn't stopped being the difference between a successful go-live and an expensive one.

AumentoAI advises CIO and COO offices on cutover strategy and command-centre design for large-scale SAP HANA and S/4HANA migrations. Book a Value Advisory Session to pressure-test your go-live plan.