Background: Oracle's Journey to Fusion Cloud
Oracle's enterprise application portfolio has evolved from on-premises suites (EBS, JDE, PeopleSoft) to a unified, cloud-based solution set. Over the past decade, Oracle invested heavily in Oracle Fusion Cloud Applications — a comprehensive SaaS suite for ERP, HCM, CRM, and more. This transition was driven by customer demand for lower IT overhead, faster innovation cycles, and modern user experiences.
Importantly, Oracle continues to support its on-premises customers. Premier Support for EBS, JDE, and PeopleSoft has been extended to at least 2035, giving organisations a lengthy runway to plan their cloud strategy. Enterprises are not forced off legacy systems in the short term — Oracle delivers regulatory updates and periodic enhancements to ensure these products remain viable while customers prepare for the cloud.
However, the trend is clear: a growing number of Oracle customers are moving to Fusion Cloud to benefit from subscription-based applications running on Oracle's constantly updated, scalable cloud infrastructure. CIOs should understand Oracle's cloud vision and product roadmap to align their enterprise applications strategy accordingly.
📚 Related Reading
Oracle Licensing Basics: On-Premises vs SaaS
Perpetual Licence Model
- Large upfront licence fee per user or processor
- Annual support/maintenance fees (~20–22% of licence cost)
- Perpetual licence allows indefinite use of software version owned
- Support provides patches, upgrades, and Oracle support services
- Licences tied to specific modules or user counts with complex metrics
- All licences in a licence set must have same support status
Subscription Model
- Subscribe per-user-per-month (or per-employee) basis
- Subscription fee includes all support, maintenance, and updates
- No separate maintenance line item — one predictable fee
- Quarterly automatic updates applied to all customers
- Shifts ERP spending from CapEx to OpEx
- You lease the software for the subscription term, not own outright
Key Licensing Considerations During Transition
Migrating mission-critical systems from on-premises to SaaS requires careful planning to avoid licensing pitfalls.
| Consideration | Details | CIO Action |
|---|---|---|
| Dual Use & Transition Period | Oracle generally allows up to 100 days of concurrent on-prem and cloud use during migration for business continuity | Time migration carefully — ensure Fusion Cloud is fully operational within this window to remain compliant |
| Licence Parallelism & Compliance | During overlap, maintain compliance on both environments with support paid until cutover | Get written documentation from Oracle allowing concurrent use; engage GLAS for mapping |
| Mapping Users & Usage | On-prem metrics must translate to cloud — Fusion Cloud typically uses "Hosted Named User" metric; some modules use employee count, revenue, or other metrics | Size cloud subscriptions correctly; verify metric for each service (ERP, HCM, SCM) to avoid over- or under-licensing |
| Customisations & Add-ons | Custom modules don't carry licence cost but replicating functionality may require additional PaaS or third-party subscriptions | Factor PaaS costs into migration plan; clarify how many environments come with subscription |
| Data Access & Archival | Perpetual licence allows read-only archival access post-migration; can terminate support on old system | Plan for archival use; consider "shelving" licences rather than fully terminating them |
Converting On-Premises Licences to Oracle SaaS Credits
CIOs frequently ask: "What happens to our existing EBS/PeopleSoft/JDE licences and the money we've invested? Can we get credit when moving to Oracle Cloud?"
While you cannot directly "port" an on-prem licence to SaaS (it's a different delivery and licensing model), Oracle offers programmes to leverage your existing investments as you transition.
Key Points About Licence Conversion
Support Fee as Cloud Credit
It's the annual support fees (not sunk licence cost) that carry negotiating value. Oracle wants to keep your ongoing spend in-house rather than losing you to a third-party vendor. They'll apply it toward cloud services to deliver more value from the same spend.
Licence "Trade-In" or Swap
Oracle may allow retiring certain on-prem licences in exchange for a cloud subscription discount — usually within the same product family (e.g., EBS Financials → ERP Cloud Financials). This is a negotiated process, not an automatic entitlement. Outcomes may include reduced subscription prices, discounted migration services, or free dual-use periods.
Shelfware Opportunity
Before migration, audit your licence usage. Unused modules represent wasted support dollars. Oracle may let you terminate support on unused licences or trade them as part of the cloud deal — redirecting spend from idle shelfware to cloud services you'll actively use.
Negotiating Penalty Waivers
Oracle historically enforces penalties for partial support cancellation. However, these rules can be waived in a mutually beneficial cloud migration agreement. Negotiate which licences are being sunset and ensure Oracle agrees to let you discontinue support without penalty as you sign the cloud contract.
Your existing investments have leverage — use them. Engage Oracle early about conversion programmes and do an internal inventory of licences and support costs. This strengthens your ability to secure credits or discounts when moving to Fusion Cloud.
Oracle SaaS Subscription Pricing Model
Moving to Oracle Fusion Cloud involves a new pricing model. CIOs should familiarise themselves with how Oracle prices Cloud Applications to budget accurately.
| Pricing Dimension | Details | CIO Guidance |
|---|---|---|
| Per-User Subscription | Hosted Named User metric — per-user monthly/annual. ERP Cloud ~$625/user/month (list, enterprise). Minimum 10 users. HCM may use employee count metric. | Enterprise deals rarely pay list price — significant discounts negotiable based on volume. Verify metric for each cloud service. |
| Bundled Suite vs Modules | Modular — subscribe to full ERP suite or individual modules (Financials, Procurement, Project Management). Add-on modules at additional cost. | Map to current on-prem functionality. Exclude unnecessary modules. Start with what you need — add later. |
| All-Inclusive of Support | Subscription covers software usage, infrastructure, support, and updates. No separate maintenance line item. | Negotiate caps on renewal increases. Subscription fees can rise at renewal — lock in protections. |
| Multi-Year Contracts | Commonly 3-year or 5-year agreements. Payments often annual in advance. Longer terms = better discounts. | Be cautious about over-committing. Balance discount vs flexibility. Generally cannot scale down during term. |
| Growth & Flexibility | Additional users/modules at contracted rates. Price-hold clauses lock discount levels for incremental purchases. | Negotiate price holds for future additions now. Be conservative on initial subscription — purchase for current needs. |
| Environments & Limits | Typically 2 environments included (production + test). Additional environments may incur extra costs. | Clarify what's included. If you need dev sandbox or performance test environment, negotiate upfront. |
Strategies to Avoid Duplicate Costs During Migration
One of the biggest concerns in an Oracle cloud transition is paying for old and new systems simultaneously. Without proper planning, companies might pay on-prem support and new cloud subscriptions concurrently — essentially double-paying.
Leverage Transition Waivers
Oracle permits up to 100 days of concurrent use. Go live and decommission legacy within this window. If insufficient, engage Oracle upfront — they sometimes extend for large customers or complex migrations if negotiated in advance.
Negotiate Maintenance Suspension
Ask Oracle to suspend on-prem support fees during migration. For a defined transition period, you don't pay legacy support, freeing budget for cloud subscription. Oracle may agree since they know you're moving off the on-prem product. Get this documented in contract.
Co-term Cloud Start with Support End
Align your cloud subscription start date with expiration of on-prem support. This way, you roll what would have been the support payment into the SaaS fee — avoiding writing two cheques. Time migrations with maintenance renewal cycles.
Phased Module Migration
If moving in phases (e.g., Financials Cloud first, HR stays on PeopleSoft), negotiate reduced support costs for retired modules. Work with Oracle to adjust support fees to match the reduced on-prem footprint as modules migrate.
Optimise Project Timeline
A faster migration reduces overlap costs. While rushing an ERP project is inadvisable, tight project governance prevents delays that extend dual running costs. Use Oracle's cloud implementation accelerators and experienced partners.
Third-Party Support (Alternative Path)
Some companies switch to third-party support (~50% of Oracle's fee) for the last years of on-prem life. Caution: this can complicate relations and make Oracle less inclined to offer attractive cloud deals. Better to negotiate directly if your end-goal is Oracle Fusion Cloud.
Licensing Negotiation Tips and Contract Renewal Timing
Negotiating an Oracle SaaS agreement alongside the retirement of on-prem licences is a complex exercise. CIOs and procurement leaders should approach Oracle with a clear plan and leverage.
Shelve, Don't Surrender On-Prem Licences
Negotiate the right to "shelve" on-prem licences during cloud subscription — retaining them as insurance. If the cloud journey fails or you need to fall back, you still have the option to reinstate your on-prem systems. Ensure the contract allows resuming support later if needed.
Negotiate a Transition Period Clause
Get a formal clause for maintenance fee suspension or dual-use period. The contract should state that during migration, you won't be charged on-prem maintenance (or those fees will be credited against cloud fees). Without a written agreement, you might be stuck paying for everything.
Align Cloud Start with Go-Live
Align the billing start of subscriptions with your planned go-live date — so you're not paying for unused months. If your project slips, include a provision to adjust the start date or provide credits for lost time. Without this, it's common to waste a significant portion of the first-year subscription due to implementation delays.
Avoid Over-Commitment — Phase Your Purchase
Don't feel compelled to licence every user or module upfront. Start with what you need in Phase 1 and include contractual options to add more later at the same discount. Also clarify user definitions in the contract — misdefining "user" or "employee" could mean you inadvertently need more subscriptions later.
Negotiate Renewal Caps
Ensure the contract has a cap on price increases at renewal (e.g., no more than 3–5%). Verify the cap holds even if you renew with fewer users — Oracle's standard cap may be conditional on maintaining or increasing user count. Try to lock pricing for a range of user scenarios.
Secure Rebalancing Rights
Negotiate a rebalancing clause that lets you shift investment between cloud services (e.g., swap unused ERP users for HCM Cloud users). Oracle sometimes allows exchanging a portion of unused subscriptions for others in their portfolio. Even partial rebalancing (say 20–30%) provides valuable flexibility.
Plan for Successor Products
Add a "successor products" clause: if Oracle discontinues or replaces a service, you get the equivalent new service at no additional cost. This protects you from being forced into buying a more expensive package mid-term because Oracle changed its offerings.
Balance Long-Term vs Short-Term Contracts
Oracle will push for 5+ year terms with attractive initial discounts. Negotiate flexibility in any long-term deal — the right to reduce users at annual checkpoints, terminate specific modules, or an opt-out clause at a midpoint. Consider a 3-year term for more frequent re-evaluation, even at slightly lower discount.
Use Oracle's Fiscal Calendar for Leverage
Oracle's fiscal year ends May 31, with quarterly targets in August, November, February, and May. Plan your negotiation to coincide with quarter-end or year-end (Q4 = May) when sales reps are pressured to close deals and may offer higher discounts. Don't let their timing rush a decision you aren't ready to make — use it to your advantage when you are ready.
Consider Expert Help
If your organisation lacks experience in Oracle mega-deals, engage a third-party adviser or licensing expert. Firms experienced in Oracle contracts can benchmark your deal, identify hidden risks, and suggest additional terms (data export rights, SLAs, non-production usage, etc.). Oracle writes Oracle's contracts — you are allowed to propose amendments.
Actionable Next Steps and Recommendations
📋 Step 1: Inventory Your Licences and Contracts
Document all current Oracle application licences, modules, user counts, and support costs. Understand contractual renewal dates and restrictions (licence sets, ULAs). This is your baseline for negotiation and planning.
📊 Step 2: Build the Business Case
Develop a multi-year TCO comparison between staying on-prem and moving to Fusion Cloud. Include software costs (licence vs subscription), hardware/infrastructure, support, personnel, upgrade costs, and qualitative benefits (agility, innovation).
🤝 Step 3: Engage Oracle and Explore Programmes
Contact your Oracle account manager or Customer 2 Cloud team to discuss available migration programmes, cloud credits, or financial incentives. Also consider a third-party licensing consultant for an independent view of your options and leverage points.
📅 Step 4: Plan the Transition Phases
Identify which business processes or modules move first and the timeline. Coordinate with your licensing strategy — e.g., if Financials goes live in Cloud by Q4, plan to drop PeopleSoft Financials support by then. Account for the safe overlap period and contingencies for delays.
⏰ Step 5: Optimise Contract Timing
Time your cloud subscription purchase to coincide with support contract renewal or Oracle's quarter-end, whichever gives more advantage. If a support renewal is imminent, use the opportunity to negotiate a cloud deal instead of renewing another year of on-prem costs.
⚖️ Step 6: Negotiate Favourable Terms
Push back on initial quotes and leverage the 10 tips in this playbook. Specifically: eliminate overlapping costs (maintenance holidays, credits), include caps and flexibility, and secure pricing protections for future years. Address data residency, security, and compliance needs.
👥 Step 7: Prepare Internal Stakeholders
Moving to the cloud changes how IT operates (no custom patches, new update cadence, staff retraining). Assign someone to monitor cloud service usage and ensure compliance with user counts and terms (Software Asset Management). This prevents overage charges or true-up surprises.
🚀 Step 8: Execute and Monitor
Track the timeline so you terminate on-prem use as planned. Verify Oracle delivers agreed services (integration assistance, training under Customer 2 Cloud). Post-migration: confirm all legacy support bills have stopped and new subscription billing aligns with contract. Set reminders for renewal negotiation well before the initial term ends.
By tackling these steps methodically, CIOs can ensure a smooth transition from Oracle's on-premises suites to Fusion Cloud Applications — capturing modern capabilities while tightly managing costs and risks.
How Redress Compliance Supports Your Cloud Transition
Planning Your Oracle Fusion Cloud Transition?
The difference between a well-negotiated Oracle Fusion Cloud deal and a standard one can be millions of dollars over a multi-year contract. Our Oracle licensing specialists help enterprises inventory and value existing licences, model TCO for cloud vs on-prem scenarios, negotiate Customer 2 Cloud conversion credits and maintenance waivers, secure contract protections (renewal caps, rebalancing rights, successor clauses), and manage the entire licensing dimension of your cloud transformation. With 20+ years of Oracle insider expertise, we ensure you transition on your terms — not Oracle's.