The Hypervisor Tax
Post-Broadcom licensing has moved to subscription bundles and higher core minimums. Renewal cost climbs for the same workload, and the negotiating position weakens each cycle.
“EBS runs fine, but I'm boxed in on every side — a VMware bill that climbs every renewal since Broadcom took over, an Oracle licensing exposure I've never fully closed, and a platform that still can't touch AI or anything modern. I'm paying more each year to stand still.”
Get EBS off VMware/on-premise and onto OCI without re-implementing it — a lift-and-shift that retires the hypervisor tax, closes the Oracle-on-VMware licensing gap, and plugs the application into OCI's AI, integration, and analytics stack.
Each of these is a business case on its own. Together they are the reason most EBS estates on VMware are being re-platformed now rather than at the next hardware refresh.
Post-Broadcom licensing has moved to subscription bundles and higher core minimums. Renewal cost climbs for the same workload, and the negotiating position weakens each cycle.
Oracle's position on soft partitioning means clustered VMware hosts can pull far more of the estate into scope than intended. On OCI the boundary is defined by the platform, not by an audit argument.
On-premise EBS has no practical path to AI services, managed integration or modern analytics. Every initiative needs its own infrastructure project before it can start.
OptimalSols is a RackWare partner. EBS is usually the anchor application, but the same replication tooling lifts everything else sitting on that VMware estate — so you exit the hypervisor entirely instead of shrinking the footprint and keeping the bill.
Workloads are replicated to OCI while they keep running in production, with incremental syncs until cutover.
Test migrations run as often as needed against the real target, so the production window is a rehearsed step rather than a first attempt.
Databases, middleware, custom applications and supporting servers move alongside EBS in the same programme.
The application does not change. What changes is what it runs on — so the programme is an infrastructure exercise with functional validation, not a re-implementation.
★ Production stays live until the final sync. Rollback remains available through cutover.
A typical single-instance EBS estate, from kickoff to production on OCI. Larger estates run the same eight-week pattern in waves.
Estate inventory, dependency map, EBS and database version review, Oracle licensing position and OCI target sizing.
OCI tenancy, compartments, networking, identity, backup and DR topology built and hardened. RackWare replication configured.
Workloads replicated to OCI from the live estate, then kept current with incremental syncs. Production stays untouched.
Functional, integration and performance testing on the target. Cutover rehearsed end to end with a documented rollback.
Final sync in the agreed window, production switched to OCI, hypercare through the first close, then handover to managed services.
★ One cutover window. The VMware estate can be decommissioned from week 9.
Once EBS is on OCI, the modernisation backlog stops needing an infrastructure project in front of it.
Lift-and-shift first, so the cost and licensing pressure is resolved quickly. Modernisation — Fusion analytics, integration, AI services — follows on the new platform at your pace, not as a precondition of the move. Ongoing support continues under Optimal360 Managed Services.
Book a migration assessment and we will size your estate on OCI, review your Oracle licensing position, and lay out the wave plan and cutover window for the full workload.
Contact Us →