A cloud move rehosts the servers. It does not reset the license. The application metrics travel with you, and the database underneath needs its own cloud math.
Moving Oracle E Business Suite to the cloud does not reduce the license. The application user and module metrics follow the workload to any host.
The real cost variable is the database underneath EBS, which still needs Enterprise Edition, options, and a cloud conversion rule.
This guide walks the application metrics, the database math, and where cloud migrations quietly overspend. Read it with the Oracle Database licensing guide.
No. A cloud move rehosts the application but does not change how it is licensed. The application metrics travel with the workload. See the Oracle E Business Suite product documentation.
What does change is the database conversion underneath, and your ability to retire what you no longer use before you pay to move it.
The cloud move does not rewrite your ordering documents. The metrics, minimums, and support terms in the contract still govern, so read them before sizing the target.
EBS is licensed per module, and most modules use an Application User or a custom application metric. Each module is priced separately on the Oracle price list.
The number that matters is authorized users, not active sessions. Estates that count active users understate the position and meet a true up when Oracle counts the authorizations.
The database is usually the larger cost. EBS production typically runs Enterprise Edition, often with options, and that license converts by vCPU on the cloud. Oracle sets the rule in its Cloud Licensing Policy.
EBS cloud targets compared
| Target | Database conversion | Notes |
|---|---|---|
| OCI | Most favorable BYOL | Native options on some shapes, lowest count |
| AWS | Two vCPU to one processor | Authorized cloud, hyperthreading rule applies |
| Azure | Two vCPU to one processor | Authorized cloud, same conversion as AWS |
| On premises | Physical cores by core factor | No conversion, full core counting |
White Paper ยท Oracle
The Oracle Buyer Side Framework
The moves we use across Oracle Database, Java and ULA estates. Read it free.
Overspend hides in what you move without checking. The migration carries forward modules, options, and support on assets the business already stopped using.
The standard system integrator pitch is to rehost Oracle E Business Suite to the cloud exactly as it runs today, for speed and low risk. We disagree. In roughly 20 of the 35 EBS migrations we advised across 2024 and 2025, a straight rehost carried forward shelfware modules and over deployed database options that the business was paying support on for no return. The buyer side move is to run a license true up and a module rationalization first, retire what is unused, then size the cloud target to the position you actually need, which is usually 15 to 30 percent smaller than the source.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
A cloud migration is the rare moment when retiring an Oracle license is easy. Spend it rationalizing the estate, not rehosting the waste.
The checklist below sequences the rationalization ahead of an EBS cloud migration.
No. A cloud move rehosts the application but does not reset the license. Application user and module metrics travel with the workload, so the count is the same unless you retire what you no longer use.
EBS is licensed per module, mostly on an Application User or custom application metric. Financials, Procurement, HR, and Supply Chain are priced and counted separately, so the position is the sum of the modules.
The database is usually the larger cost. EBS production typically runs Enterprise Edition with options, which converts by vCPU on authorized clouds at two vCPU to one processor.
Often yes. OCI uses a more favorable BYOL conversion and can bundle options on some shapes, which in our engagements ran 20 to 40 percent below the same estate on AWS.
Rehosting the estate as is. A straight lift carries forward unused modules and over deployed options, so the business pays support and cloud capacity for assets it does not use.
Yes. Diagnostic Pack, Tuning Pack, and Partitioning meter the same way in the cloud as on premises. An option enabled without a license becomes a true up at migration.
Authorized users. The contract metric is authorization, not active sessions, so counting active users understates the position and invites a true up.
Redress rationalizes the module and database estate, models the cloud targets, and runs the renewal on the result. Every engagement is led on the buyer side by a former Oracle licensing executive.
Redress runs Oracle EBS cloud advisory inside the Vendor Shield subscription, the Renewal Program, and the Benchmark Program, led on the buyer side by a former Oracle licensing executive.
Read the related Oracle services page, the Oracle knowledge hub, the benchmarking page, and the contact page.
A buyer side reference on the Oracle Unlimited License Agreement decision. Certification scope, the exit path, audit posture, support strategy, and the commercial levers that still hold at renewal.
Used across more than five hundred enterprise software engagements. Independent. Buyer side. Built for Oracle customers running the next renewal cycle.
Open the white paper in your browser. Corporate email only.
Open the Paper →
Renewal in twelve months. Audit notice in the inbox. RFP on the desk. We start where you are.
EBS module metrics, the database underneath, cloud conversion math, shelfware retirement, and migration intelligence from every Oracle engagement we run on the buyer side.
The moves we use across Oracle Database, Java and ULA estates. Read it free in your browser. No follow up sales call unless you ask for one.
Read the white paper →No PDF buried in your inbox. You read it on the next screen.
