- Organisation
- Maersk
- Predecessor
- Longstanding data-centre environments and third-party-operated SAP infrastructure
- Destination
- SAP workloads on Microsoft Azure
- Workload
- Approximately 500 SAP servers, more than 1 PB of data and development, preproduction and production systems
- Stage
- Completed SAP infrastructure migration
- Retirement status
- Longstanding SAP infrastructure and technical debt were retired for the stated scope; wider enterprise infrastructure retirement is not claimed.
- Confidence
- High
- Next trigger
- A later SAP application-modernisation milestone or wider data-centre retirement statement.
Programme context
Maersk completed a controlled migration of 500 SAP servers and more than a petabyte of data to Azure in six months.
Why this matters: The record identifies a named organisation, an explicit predecessor and destination platform, and a bounded workload and lifecycle stage.
Migration timeline
| Date or stage | Milestone | What changed | Evidence status |
|---|---|---|---|
| Six-to-nine-month plan | Migration milestone | The team set a six-to-nine-month delivery window. | Source-stated plan |
| Six months | Migration milestone | The migration was delivered in six months. | Source-stated completion duration |
| Three weeks | Migration milestone | The Azure environment for 500 SAP servers was built in three weeks. | Source-stated implementation duration |
Workload migration matrix
| Workload | Predecessor | Destination | Status by 23 Jul 2026 |
|---|---|---|---|
| Approximately 500 SAP servers, more than 1 PB of data and development, preproduction and production systems | Longstanding data-centre environments and third-party-operated SAP infrastructure | SAP workloads on Microsoft Azure | Completed SAP infrastructure migration |
Implementation and architecture
- A hot standby and controlled failover moved production workloads.
- Azure Blueprints supported standardised governance.
- Development, preproduction and production systems were included in the stated scope.
Known unknowns and contradictions
- The exact final production cutover date.
- The complete list of retired third-party and data-centre components.
- Any residual SAP workloads outside the stated estate.
No missing fact is inferred to broaden the source-supported migration claim.
PlatformTrace analysis
The source supports the completed SAP infrastructure migration and retirement of longstanding systems. It does not establish that every Maersk application or data-centre workload moved to Azure.
Performance, cost, uptime and operational outcomes remain attributed source claims unless independently stated otherwise.
Evidence ledger
- Microsoft customer story, 1 April 2026
Named Maersk engineers identify the 500-server, petabyte-scale SAP scope, controlled failover, six-month delivery and current Azure operating model.
Corrections and updates
23 July 2026 — Initial Verified dossier published from the complete five-lane overnight intake and corrected central adjudication. Later milestones will be appended rather than silently replacing this state.