NTT DOCOMO BUSINESS has moved its shared database platform to Oracle’s cloud, according to a September 30 announcement. The release reports a 43% reduction in database licence costs compared with the on-premises environment. It does not report a 43% reduction in total technology spending.
What the announcement measures
The case covers 12 internal systems connected to about 400 servers. Oracle describes automated maintenance and a disaster-recovery arrangement across two Japanese cloud regions. CapKet has not independently audited the customer figures.
How to read a cloud-savings claim
CapKet analysis: Start by drawing a boundary around the cost being compared. A licence bill, a hosting bill and an entire IT budget are different measures. A percentage attached to one cannot safely be transferred to another.
For a procurement team, the next step is a like-for-like worksheet: the same workload, the same availability requirement and the same measurement period. It should separately identify one-off migration work and recurring charges. Otherwise, a lower recurring line item could be confused with a completed payback calculation.
Resilience also deserves a separate test. A second location is part of a recovery design; buyers still need to ask how restoration is tested and what interruption their business can tolerate. Those questions do not imply a weakness in this deployment. They explain why a customer announcement cannot substitute for an organisation’s own assessment.
What to watch next
The useful follow-up would be a fuller comparison of operating expenses and service outcomes. No saving for another customer is guaranteed. For the separate question of delegated software authority, see our Fusion Claw report.
Primary source record: Original announcement and Oracle Japan’s distributed announcement. Checked September 30, 2026, around 18:23 IST. The linked issuer material supports the attributed facts; CapKet’s explanatory examples are identified above.