Home/Blueprints/Oracle → EDB Postgres
Move off Oracle — without breaking what runs on it.
Move Oracle Database to EDB Postgres on OpenShift and cut licence and support 70–80% over five years — with single-digit code change, staged cutover and rollback at every gate. Prove it on your own schemas in 30 days.
The bottom line.
Most regulated firms operate Oracle databases they no longer want to operate. Leaving isn't the question — how to leave without breaking the applications, losing performance, or spending more on the move than it saves, is.
This blueprint is the standardised path off Oracle: EDB Postgres Advanced Server on Red Hat OpenShift, operated by Options as one managed service. Expect 70–80% lower licence and support over five years and single-digit application change — proven on your own schemas in a 30-day sandbox first.
Why now.
Oracle licence and support
Enterprise Edition lists at $47,500 per processor in 2026, plus 22% support escalating 8% a year. EDB subscription is typically 70–80% lower.
19c support ends
Oracle Premier Support for 19c ends April 30, 2026. After that it's a premium extension, an upgrade to 23ai, or an unsupported database.
Audit risk
Oracle licence audits routinely surface million-dollar findings on virtualised estates. Migrating to EDB removes the audit surface entirely.
AI data growth
IDC expects 80% of enterprises to modernise legacy databases by 2027 for AI. Postgres has native vector, JSON and AI extensions — no per-feature licence.
EDB tooling maturity
EDB Migration Portal with AI Copilot collapses schema and PL/SQL conversion from months to weeks, at single-digit rewrite rates.
The strategy.
Where It Applies
- Custom-built FSI applications on Oracle 11g, 12c, 18c, 19c or 21c
- OLTP, mid-volume analytics, reporting and internal line-of-business apps
- Portfolio management, trade booking, position keeping, risk and reporting
- KYC/AML data stores, document management, settlement and treasury
Honest Edge Cases
- Exadata-dependent extreme OLTP (Smart Scan, HCC) — keep it on Exadata
- Packaged FSI apps with Oracle-only support matrices (some Murex, Calypso)
- Active GoldenGate replication into Oracle-only third parties
- RAC topologies you can't redesign in scope
How it runs on OMC.
EDB Postgres runs as a containerised stateful service via the EDB operator on OpenShift, operated by Options as one managed service — database, platform and infrastructure. Pick the tier for your data residency and performance; it changes worker isolation, not the foundation.
Standard
Shared, multi-tenant platform. Fastest way onto FSI-hardened Kubernetes.
Advanced
Dedicated worker pools with tighter data-plane isolation and custom SLAs.
Dedicated
Single-tenant control plane in your jurisdiction. Full sovereignty over data and identity.
PodOps managed service
Options FSI hardening
Red Hat OpenShift
Kubernetes
Red Hat Premier Partner and EDB partner, with a direct engineering channel to both.
Validation Sandbox.
A 30-day engagement where we stand up EDB Postgres AI on OpenShift, migrate one or two of your real schemas through the Migration Portal, and hand you the evidence: a per-schema compatibility report, a benchmark on your own queries, and a five-year TCO comparison.
- ✓ No procurement, no lock-in, no obligation to continue
- ✓ Your own schemas, your own queries
- ✓ Written compatibility report and production plan
You see the real rewrite number on your own code — not a generic estimate — before any production commitment.
The migration path.
Four phases, explicit gates, tested rollback at each step, and a parallel run before cutover. A mid-sized estate of 50–200 cores runs 4–7 months end to end.
Discovery & design
4–6 wks
Inventory, application dependency mapping, a full compatibility scan, target architecture and the migration wave plan.
Build & migrate
6–12 wks
OpenShift hardened, EDB operator deployed, schemas migrated wave by wave via the Migration Portal and Factory Migration.
Parallel run & validate
4–8 wks
Continuous replication Oracle→EDB, read-only traffic validated, compliance reviews, and a tested rollback drill.
Cutover & steady state
2–4 wks + hypercare
Cutover in the change window, 30-day hypercare, Oracle licence cancelled at renewal, then PodOps operates.
Proof and business case.
On a typical 100-core estate, roughly $4–6M net saving over five years vs staying on Oracle 19c (illustrative — the sandbox produces your number).
Public Oracle-to-Postgres references (EDB): DBS Bank · USDA · FBI · a European FSI cutover
Ready to leave Oracle?.
Stacks with Public Cloud Repatriation if your Oracle estate is on AWS or Azure. Also: Highly Capable Teams · AI & PrivateMind.