OBIEE to Fabric Migration With the RPD Rebuilt as a Semantic Model, Not Just Dashboards Redrawn
An OBIEE or Oracle Analytics Server estate is more than its dashboards. The business logic lives in the RPD repository: physical, business model and presentation layers, calculations, hierarchies, variables and security. Our OBIEE to Fabric migration inventories that estate, rebuilds the model in Power BI on Microsoft Fabric, moves Answers and BI Publisher reporting across and proves parity before anyone switches.
OBIEE to Fabric Migration: Rebuilding the RPD, Not Redrawing Dashboards
In Oracle BI, the dashboards are the visible tip. Beneath them sit the RPD, where physical tables are joined, a business model defines hierarchies, measures and aggregation rules, and a presentation layer exposes subject areas. Variables, initialization blocks, application roles and data filters add behaviour on top. An OBIEE to Fabric migration has to carry that logic across, not just recreate the charts.
The target is different in kind. A Power BI semantic model replaces the business model layer, DAX measures replace calculations written in logical SQL, and Power BI reports and paginated reports replace Answers analyses, dashboards and BI Publisher output. We resolve the model first, land the Oracle data in OneLake, then rebuild reports on top. Microsoft's migration guidance recommends focusing on the business questions a report answers, not copying every object exactly.
We decide per item. Content people use is rebuilt, near-duplicates are merged, and content nobody opens is retired. Support dates differ by Oracle BI release, so we do not quote one here. Oracle publishes them for OBIEE in My Oracle Support Doc ID 1664916.1 and for Oracle Analytics Server in Doc ID 2775561.1. Confirm yours with Oracle, and we will plan around it.
Six Core Components of Every OBIEE to Fabric Migration
From inventory to parity sign-off: everything needed to move Oracle BI and Oracle Analytics Server reporting to Power BI on Microsoft Fabric.
We list every RPD and subject area, Answers analysis, dashboard, BI Publisher report, agent and prompt, then check usage and owners. Each item is marked retire, consolidate or rebuild, with a complexity rating, before any build starts.
We rebuild the business model layer as a star-schema semantic model: logical tables become fact and dimension tables, hierarchies and measures are redefined once, and the presentation layer becomes display folders and perspectives. We choose Import, DirectQuery or Direct Lake per subject area.
We translate time-series functions, level-based measures, FILTER expressions, ranking, parent-child hierarchies and variables into DAX measures and model features, then test results at the original grain. Some logic moves upstream into Fabric transformations instead.
We land the Oracle sources your RPD reads as Delta tables in OneLake. Where the source database fits Microsoft's requirements, mirroring can replicate Oracle tables with little custom work. Otherwise we use pipelines, copy jobs or Dataflows Gen2 with the Oracle connector through an on-premises data gateway where needed.
We rebuild priority analyses and dashboards as Power BI reports, mapping prompts to slicers and navigation to bookmarks and drill-through. Pixel-perfect BI Publisher output is rebuilt as paginated reports, and agents and scheduled delivery are replaced with subscriptions and alerts per report.
We map application roles and data filters to workspaces, apps, roles and row-level security, then run a parity framework with report owner sign-off before cutover and set up usage monitoring afterwards.
RPD Logic to DAX: How We Translate Oracle BI Calculations
In the RPD, measures are defined once in the business model and Oracle BI generates the SQL. In Power BI, a DAX measure responds to the filter context of the report. So the translation is about controlling filter context, and every pattern is tested against the Oracle result. Illustrative patterns only: the right DAX depends on your model.
AGO("Sales"."Revenue", "Sales"."Time"."Year", 1)CALCULATE ( [Revenue], SAMEPERIODLASTYEAR ( 'Date'[Date] ) ) and TOTALYTD for TODATE-style measuresRevenue defined with its aggregation rule set at the Region level of a dimension hierarchyCALCULATE ( [Revenue], ALLEXCEPT ( Geography, Geography[Region] ) )FILTER("Sales"."Revenue" USING ("Products"."Brand" = 'Acme'))CALCULATE ( [Revenue], Product[Brand] = "Acme" )RANK("Sales"."Revenue")RANKX ( ALLSELECTED ( Product[Product] ), [Revenue] )Parent-child hierarchy in the business model (for example an account or organisation tree)Calculated columns with PATH and PATHITEM to flatten the tree into levels, then a Power BI hierarchyVALUEOF(NQ_SESSION."REGION") inside a data filter, populated by an initialization blockA role filter such as Region[Region] = LOOKUPVALUE ( UserRegion[Region], UserRegion[Email], USERPRINCIPALNAME () )Not every Oracle BI construct has a one-line equivalent. Where logic is really data preparation, such as a calculation pushed to the database, we move it into Fabric so every report reuses it.
OBIEE to Fabric Migration: Four Phases to Cutover
A structured plan so your Oracle BI reporting moves without disruption. Oracle BI stays live while Power BI is built and validated, so users switch only when their reports are signed off.
We inventory your OBIEE or Oracle Analytics Server environment, check usage and owners, and agree what to retire, consolidate or rebuild, with a complexity rating that flags RPD-heavy subject areas, BI Publisher output and security.
Output: inventory and decisionsWe build the first governed semantic model from one subject area, translate the hardest calculations and rebuild a pilot set of reports. The pilot sets DAX, naming and design standards and proves parity before the main build.
Output: signed-off pilot and standardsWe migrate in waves ordered by business priority and shared subject areas. Each wave is checked against the Oracle original, and the report owner signs off every report before it moves on.
Output: migrated reports with sign-offWe run Oracle BI and Power BI side by side, cut over by audience, retire Oracle content when you are ready and hand over documentation, runbooks and training so your team can run the platform.
Output: retired Oracle content and handoverWhat the Timeline Depends On
We do not quote a duration before we have seen your estate. Length is driven by the number of reports still in scope after triage, the number and complexity of RPD subject areas, how much logic sits in calculations and variables, the number of Oracle data sources, BI Publisher volume and how long you want to run in parallel. We fix the plan in the proposal after discovery and work back from your Oracle support or renewal date where there is one.
Triage complete; destination model design and wave plan approved.
First semantic model live; pilot reports match Oracle BI; standards agreed.
Each wave validated and signed off by report owners.
Users moved by audience; Oracle BI content retired, ideally ahead of your support or licence renewal date.
How We Price an OBIEE Migration
You see real effort on your own data before committing to the full programme. Price is driven by report count, calculation complexity, subject area and data source volume, security requirements and parallel-run length.
We inventory your Oracle BI estate and give you a triage, a complexity profile and a recommended scope, at no cost.
No commitmentA priced pilot that builds one semantic model and rebuilds a representative set of reports, so the approach and effort are proven on your data.
Fixed scope and feeRemaining waves are quoted by complexity tier once the pilot gives real numbers, as fixed fee per wave or on a time and materials basis, whichever suits you.
Your choice of modelWhy Choose Us for OBIEE to Fabric Migration
Six reasons teams trust us to move Oracle BI reporting to Power BI without losing the numbers their business relies on.
Translating RPD logic is where migrations stall. We map each pattern to DAX, test it at the original grain and move upstream anything that is really data preparation.
Oracle BI estates often hold several subject areas with overlapping definitions. We consolidate them into shared star-schema semantic models first, so each business metric has one definition.
Long-lived Oracle BI environments carry analyses nobody opens and subject areas nothing uses. We find them first, so you rebuild and test only what the business uses.
We do not switch reporting until totals, calculated measures and filtered views match the Oracle original and the report owner signs off.
Application roles and data filters are mapped to row-level security and tested user by user, so people see the same data in Power BI that they saw in Oracle BI.
You receive architecture notes, runbooks and a team walkthrough, and we can train your Oracle BI developers in Power BI, DAX and Fabric data preparation, so your team runs the platform without us.
The starting point: an Oracle BI environment that has grown for years. Several subject areas with overlapping definitions, an RPD that only a few people dare to change, hundreds of analyses of which few are opened, and BI Publisher reports that finance relies on. The Oracle BI version is ageing and a support or renewal date is approaching.
What we do: triage the environment, retire what nobody opens, rebuild the shared subject area as one governed semantic model, translate the calculation-heavy measures to DAX, map application roles and data filters to row-level security and rebuild the priority reports in Power BI and paginated format. Each report is checked against the Oracle original and signed off by its owner.
What the client team gets: one definition per metric, fewer reports to maintain, documented DAX, and developers trained to extend the model. Oracle BI is retired in stages once parallel running confirms the numbers hold.
Other services and guides our clients use alongside OBIEE to Fabric migration.
Common Questions About OBIEE to Fabric Migration
Still deciding? These are the questions teams ask most before they plan their move off Oracle BI.
Book a Free Call →Start Your OBIEE to Fabric Migration Plan
Book a free assessment. We will inventory your RPD, analyses, dashboards and BI Publisher reports, flag the calculation-heavy content and recommend what to rebuild, consolidate or retire, at no cost.