Most cloud migration content about SAP assumes the destination is one of the hyperscalers SAP certifies for HANA, and prices the move accordingly. OCI plays a different position. Oracle and SAP have maintained a certification relationship for decades, and SAP NetWeaver based applications running on Oracle Database are certified to run on OCI compute, with the database tier on OCI database services. That covers a very large installed base: ECC estates that never left Oracle Database, BW systems on Oracle, and the long tail of NetWeaver applications around them. What it does not cover is HANA, which SAP has not certified on OCI. An honest SAP on OCI article starts with that boundary, because budgets built on the wrong side of it are fiction.
This article is part of our series on what an OCI migration really costs, and it covers the SAP specific case: which configurations are actually certified, why the certified slice is economically attractive, what the move costs by scenario, and how to build the budget with the basis team rather than against them.
The certification boundary, plainly stated
SAP certifies specific combinations of application, database, operating system, and infrastructure. For OCI, the certified territory is SAP NetWeaver application server based products, ECC 6.0, BW, and their relatives, running against Oracle Database, on certified OCI compute shapes, with current support pack and kernel levels. Oracle publishes the certified shapes and configurations, SAP records them in its notes, and the combination is supported by both vendors in production. Outside that territory sits anything requiring HANA as the database, including S/4HANA, which SAP certifies on its own RISE infrastructure and selected hyperscalers but not on OCI. The practical reading for a CIO: if your SAP landscape runs on Oracle Database today, OCI belongs on your shortlist; if your committed future is S/4HANA on HANA, OCI is infrastructure for the journey's Oracle Database years, not the destination.
That journey framing matters more than it first appears. ECC on Oracle Database remains supported into the 2030s under SAP's published maintenance commitments, S/4HANA programs run years long and frequently slip, and an estate that will run ECC for another five to eight years has a real infrastructure decision to make for those years. Paying data center prices, or a hardware refresh, for a platform with a known end date is exactly the situation a move to OCI prices well against.
Why the certified slice is economically attractive
Three effects make SAP on Oracle Database on OCI a strong cost case. First, the database tier, which dominates SAP infrastructure spend, lands on the platform Oracle Database runs best on, with Exadata service options for the heaviest systems and BYOL carrying existing database licenses across rather than abandoning them. Second, SAP application servers are steady, predictable consumers that right size beautifully: years of SAPS sizing data mean the compute can be matched to measured load rather than refresh era guesswork. Third, SAP landscapes carry enormous non production footprints, and OCI's stop start economics on those environments alone frequently funds the migration. These are the same levers that drive the 40% average spend reduction we record across optimization engagements, and SAP estates tend to have them in unusually pure form.
What the move involves
Technically, an SAP move to OCI is a heterogeneous or homogeneous system copy, depending on whether the operating system changes, executed with SAP's standard tooling and the database moved with the Oracle methods the rest of this series covers. The application tier redeploys onto certified shapes; the database tier moves by Data Pump, backup and restore, or replication according to the outage window, with the decision arithmetic laid out in Oracle database migration to OCI. Around that core sit the usual SAP project disciplines: the transport landscape, the RFC and interface inventory, printer and output management, fiscal calendar driven test cycles, and a basis team whose sign off gates everything. None of it is exotic; all of it is calendar.
The cost drivers will look familiar from the other application families in this series, with two SAP specific accents. Interface density is usually higher: a mature ECC estate talks to dozens of systems through IDocs, RFCs, and middleware, and every connection wants a test slot. And the testing regime is heavier, because SAP estates run the company's books: period close simulations and payment run parallels are not optional, and they only fit where the fiscal calendar allows. Elapsed time on SAP moves is set by test windows more than by terabytes.
Scenario costs
The bands below assume Oracle Database under the SAP landscape, BYOL, a landing zone in place, and services effort excluding OCI consumption.
| Scenario | Typical scope | Elapsed timeline | Services budget band |
|---|---|---|---|
| Single system move | One NetWeaver system on Oracle DB, such as BW or a standalone ECC, modest interfaces, weekend window available | 2 to 4 months | Low six figures |
| Production landscape | ECC plus surrounding NetWeaver systems, full transport landscape, dense interface inventory, fiscal calendar constraints | 5 to 9 months | Mid six figures |
| Estate with OS change or tight windows | Endianness or OS migration in scope, near zero downtime requirement on the core, multi system cutover sequencing | 8 to 14 months | High six figures |
The honest caveats: an operating system change inside the move adds a heterogeneous copy with its own tooling and testing, which is what pushes estates into the third band, and any whisper of folding an S/4HANA conversion into the same program should be resisted in the budget, because it is a transformation wearing a migration's name tag and deserves its own business case. Where the SAP move is part of closing a facility, the estate level arithmetic in the data center exit business case applies unchanged.
A framework for the SAP on OCI budget
- Establish the certification position. Confirm every system's database, OS, kernel, and support pack levels against the published certified configurations. Anything outside the boundary gets a remediation line or leaves scope.
- State the S/4HANA horizon honestly. Write down the realistic year the estate leaves ECC. The gap between now and then is the investment window the OCI case must pay back inside, which feeds directly into the ROI timeline arithmetic.
- Size from SAPS and measured load. Use early watch reports and actual utilization, not the hardware inventory, to size target shapes. This is where the right sizing dividend gets locked in or lost.
- Inventory interfaces with the basis team. IDocs, RFCs, middleware connections, output management. Each gets an owner and a test slot, and the count sets the testing calendar.
- Price the outage window per system. The ECC core and the rest of the landscape rarely share a downtime price; let each system's number pick its own database method.
- Anchor the fiscal calendar. Period closes, payment runs, and year end set where cutover windows exist. Put them on the plan first and fit the technical schedule around them.
- Decide the non production strategy. Which systems move, which get rebuilt as fresh system copies, which retire, and which adopt stop start schedules from day one on OCI.
- Settle both licensing postures independently. Oracle Database BYOL on one side, SAP license implications of the infrastructure change on the other. Independent review beats vendor assurances on both.
Cost lines specific to SAP moves
Four budget lines show up on SAP migrations with a regularity that earns them named places on any honest quote. Archiving before the move. Mature ECC databases carry years of closed documents, and SAP's archiving framework exists precisely to offload them. A disciplined archiving pass before migration shrinks the database, every system copy taken from it, the transfer window, and the OCI storage bill, all at once. It needs functional sign off and lead time, which is why it belongs in the assessment phase, but few investments in the whole program return more per week of effort.
Middleware and the interface tail. The PI or PO layer, cloud connectors, EDI subsystems, and the queue of RFC destinations all need repointing and revalidating, and middleware environments are systems in their own right with their own move or rebuild decision. The interface tail is also where external parties enter the calendar: banks, customs systems, and trading partners test on their schedule, not yours, and the dates they offer should be booked before the technical plan assumes them.
Validation depth for regulated industries. Pharmaceutical, medical device, and similarly regulated SAP estates carry qualified system status, and an infrastructure change triggers requalification: documented installation and operational evidence, change control, and approval workflows that can add weeks of formal effort. The technical migration is identical; the paperwork is not, and quotes that ignore the difference are quoting someone else's estate.
Hypercare through the first close. The first month end close on the new platform is the real acceptance test, and the project team should still be at full strength when it runs. Two to four weeks of named hypercare on the quote beats the same effort appearing later as an emergency.
The same honesty applies to the parallel running period. SAP cutovers tend to be conservative, with source systems kept warm and restorable through the first close or two, and that caution has a monthly price that belongs in the model rather than in the postmortem, the arithmetic for which is laid out in budgeting dual running.
Rehearsal discipline deserves its own mention, because SAP estates reward it unusually well. A full dress rehearsal of the production cutover, timed end to end against a recent system copy, converts the cutover weekend from an estimate into a measurement: how long the export really takes, how long the import really takes, where the interface restart sequence stalls, and whether the runbook survives contact with a tired team at two in the morning. For the core ECC system the rehearsal should run at least twice, once to find the problems and once to prove they are fixed, and the rehearsal environments belong in the migration budget as named consumption. Estates that rehearse twice routinely beat their planned windows; estates that rehearse on paper discover their window arithmetic in front of the business. The rehearsal also produces the one artifact that makes the go or no go meeting short: a measured timeline with decision gates, which is what lets a CIO approve a cutover with confidence rather than hope.
Buying the move and the run
SAP moves to OCI price naturally as fixed project fees once the framework above has been run, because the scope ambiguities that justify time and materials pricing have been removed in advance. After go live, the estate needs the operating discipline that protects the business case, scheduled non production, patching aligned to both vendors' cycles, 24/7/365 monitoring through close periods, which is managed monthly retainer territory, and estates that arrived on OCI without the right sizing pass make strong candidates for an optimization engagement paid only on verified savings. The platform detail of running the workload well, shapes, database services, availability design, lives on our SAP on OCI page, and our team brings 20+ years of combined Oracle estate experience to the database half of the conversation, which on this workload is the half that decides the economics.
SAP on OCI rewards precision. Confirm the certification boundary, name the ECC horizon, size from measured load, and let the fiscal calendar own the schedule. Estates that do this turn an aging platform with a known end date from a liability into several years of cheap, stable, well supported infrastructure, and walk into their eventual S/4HANA decision with money still in the budget.
Part of a series
This guide is part of OCI Migration — our complete pillar guide on the topic.
Moving Oracle workloads to OCI, or already running on OCI and not sure the architecture or the spend is right? Most teams bring in a specialist before they commit to a region, a shape, or a Universal Credits number. OCISpecialists.com plans the landing zone, runs the migration, and manages the estate after go live, on a fixed project fee, a managed monthly retainer, or a cost optimization fee paid only on verified savings.