The pitch for Oracle Fusion SaaS is that it ends the licensing headache. No more processors to count, no more options to track, no more audit letters about the application estate. Some of that is true, and some of it simply moves the commercial risk from a compliance question to a contract one. A subscription does not get audited the way a deployment does, but it does get renewed, repriced and over committed, and the on premises estate you are leaving behind remains auditable every day until it is genuinely switched off. Treating the move as a hosting decision misses the real work, which is the licensing and contract change underneath it.
What changes when you move from EBS to Fusion SaaS?
The fundamental change is from owning to renting. On premises E Business Suite is licensed perpetually, with the cost front loaded into the license purchase and an annual support fee running at roughly 22 percent with annual escalation. Fusion SaaS replaces that with a subscription, typically priced per user per month, where the application, the infrastructure and the updates are bundled into a recurring fee. The compliance burden of counting deployments largely disappears, but it is replaced by the discipline of subscription management: sizing the user count accurately, controlling module scope, watching for overage, and negotiating renewal before the subscription auto escalates. The audit risk does not vanish so much as transform into a commercial risk you manage through the contract.
Do on premises licenses transfer to Fusion SaaS?
No, perpetual on premises application licenses do not convert into SaaS entitlements. The two are different products under different commercial models, and the value you paid for perpetual EBS licenses does not automatically carry across. What Oracle may offer is a commercial incentive to migrate, a credit, a discount, or a bundled arrangement that recognises the existing relationship, but that incentive is a negotiation, not an entitlement. Buyers frequently leave value on the table by assuming the migration is a like for like swap or by failing to price the perpetual licenses and support they are giving up against the subscription they are taking on. The existing estate is leverage, and it should be valued and traded deliberately as part of the migration deal.
| Dimension | On premises EBS | Fusion SaaS |
|---|---|---|
| License model | Perpetual, owned | Subscription, rented |
| Cost shape | Upfront license plus 22 percent support | Recurring per user fee |
| Compliance focus | Deployment, options, database | User count, module scope, renewal |
| Main risk | Audit finding | Over commitment and repricing |
Is Fusion SaaS audited like on premises software?
Fusion SaaS is governed by the subscription agreement rather than a deployment audit, so Oracle does not send a team to count processors on a cloud you do not control. What it does instead is hold you to the subscription terms: the number of users you subscribed for, the modules in scope, and the overage provisions if you exceed them. Those are contract mechanics, and they reward exactly the same buyer side rigour as an on premises audit, applied earlier. The subtler point is that the on premises estate you are migrating away from stays fully auditable until it is decommissioned, and a half finished migration that leaves EBS and its database running alongside the new SaaS subscription is exposed on both fronts at once.
What happens to the database under EBS?
This is the part migration plans most often forget. EBS runs on an Oracle Database, and that database carries its own licensing, its own options, and the restricted use boundary that limits it to supporting EBS. When EBS moves to Fusion SaaS, the underlying database does not automatically retire, especially if other systems were quietly relying on it or if the migration runs in phases. A database left running after the application it supported has moved is a database that still needs licensing and can still carry an options or processor finding. The migration plan should include the explicit decommissioning of the EBS database, evidenced and dated, so that the liability ends when the application use ends rather than lingering as an orphaned exposure.
A services group moved its core EBS modules to Fusion SaaS and assumed the licensing question was closed. A review found two open exposures: the EBS database had been left running to feed a legacy reporting system, keeping a full database license liability alive, and the SaaS subscription had been sized to the headcount at signing rather than to actual active users, locking in overage. The buyer side response was to plan the database decommissioning with dated evidence, right size the subscription at the next renewal window, and value the retired perpetual licenses as leverage in that renewal. The result reduced both the lingering audit exposure and the recurring subscription cost.
What is the buyer move?
The buyer move is to manage the migration as a licensing and contract exercise from the start, not a technical project with a licensing afterthought. Value the perpetual licenses and support you are giving up and trade them as leverage in the SaaS deal, size the subscription to genuine active users rather than headcount, and negotiate renewal and overage terms before signing. In parallel, plan and evidence the decommissioning of the on premises estate, including the EBS database underneath, so the old liability ends cleanly. Done this way, the move to Fusion SaaS delivers the simplicity it promises instead of carrying a hidden double exposure through a half finished transition.
For how the EBS database drives audit exposure, see EBS in an Oracle audit. For the support cost that rides on the estate, see application support costs and the estate. The full method sits in the Oracle license compliance guide.