All posts · BI Reports

OBIEE to OAC Migration: What You Need to Know

Oracle OBIEE is being superseded by Oracle Analytics Cloud. Here's what changes, what stays the same, and how to plan your migration.

Anurag Jangra · February 28, 2026 · 6 min read · ... views

OBIEE to OAC: why migrate

Oracle Business Intelligence Enterprise Edition (OBIEE) is Oracle’s on-premise analytics platform. Oracle Analytics Cloud (OAC) is its cloud successor with the same core capabilities plus modern features. Oracle has announced OBIEE’s end-of-life for new features — OAC is the strategic direction.

What’s the same

  • RPD (semantic model) structure: Physical, Business Model, and Presentation layers
  • Subject areas, hierarchies, and measure calculations carry over
  • OBIEE dashboards and analyses migrate with the Content Migration utility
  • OTBI in Fusion Cloud uses the same OBIEE presentation services under the hood

What’s different in OAC

  • Workbooks replace traditional dashboards as the primary canvas
  • Modern Data Visualisation capabilities (DV) that OBIEE doesn’t have
  • ML and augmented analytics built-in
  • No server management — Oracle manages infrastructure, patching, scaling
  • Monthly OAC feature updates vs OBIEE’s infrequent patch cycles

Migration toolkit

Oracle provides the BAR (Backup and Restore) format to migrate RPDs and catalogs from OBIEE to OAC. Process:

  1. Export RPD from OBIEE Administration Tool
  2. Import into OAC Model Administration Tool
  3. Validate connection pool settings (point to new data sources)
  4. Upload OBIEE catalog via Content Migration tool
  5. Test analyses — most work without changes; some use deprecated functions

Common migration issues

  • Custom OBIEE plugins and skins don’t migrate (recreate as OAC themes)
  • OBIEE_ROWCOUNT system function unavailable (use aggregate measures instead)
  • Write-back functionality (OBIEE) works differently in OAC
  • Some complex Narrative views and Ticker views need redesign in OAC workbooks

Migration strategy

Migrate high-value dashboards first. Use the migration as an opportunity to retire unused reports. Pilot with a non-critical team to build familiarity before enterprise rollout.

Think Beyond the Implementation

Questions worth sitting with after reading this

01

Why is this architecture appropriate for this specific context — and where would it be the wrong choice?

02

What assumptions did we make that aren't stated explicitly? What happens if those assumptions are wrong?

03

What would break first if the requirements changed — volume doubled, a third system was added, or the deadline halved?

04

What alternatives did we reject, and why? Was the decision made on evidence — or habit?

AJ
Anurag Jangra
Oracle Cloud PaaS Consultant · OIC & VBCS Specialist

4.5+ years delivering enterprise Oracle Cloud integrations and VBCS applications across manufacturing, IT services, and financial sectors. OCI Certified — writes about real-world OIC, VBCS, SQL, and BI Publisher patterns from production experience.

Chat on WhatsApp