Retiring Brio, IR and SQR reporting

Hyperion to Power BI Migration for Interactive Reporting (Brio) and SQR Reports

We take the .bqy documents and SQR programs your teams still run, separate the data logic from the layout, and rebuild them as a governed Power BI model with interactive and paginated reports — each one reconciled against the Hyperion original. Your consolidation and planning engines stay exactly where they are.

Scope approved before any hours are used · Hours never expire

  • Microsoft-certified
  • Prepaid hours that never expire
  • US-based senior engineers
  • Reconciled against the original
  • You own everything
Hyperion data model Sales Date Product Region Customer

Sample Hyperion reporting model. Illustrative data, not a client’s numbers

Which Hyperion this is

Report content, not the EPM engine

“Hyperion” covers two very different things, and the difference decides whether Power BI is the right destination. One is the reporting estate: Interactive Reporting documents (the product that began life as BrioQuery), SQR report programs, and the report output of Financial Reporting. The other is Oracle’s EPM suite — Hyperion Financial Management for consolidation, Planning and Essbase for budgeting and multidimensional analysis. This page is about the first. Power BI does not consolidate entities, eliminate intercompany balances, or accept budget write-back, and anyone telling you it replaces HFM or Planning is selling you a project that ends badly.

What Power BI does replace well is the report layer: the .bqy files someone refreshes every Monday, the SQR jobs that produce the month-end PDFs, and the Financial Reporting grids finance exports to Excel before anyone reads them. It is also a different job from an OBIEE to Power BI migration. Both are Oracle, but OBIEE estates are governed by one central semantic layer (the RPD); Hyperion IR and SQR estates usually are not. The logic lives inside each document and each program, so the work starts with an inventory rather than a repository read.

What the rebuild covers

  • .bqy and SQR inventory
  • Duplicate & dead-report triage
  • IR data models → star schema
  • Computed items → DAX
  • Pivots & charts → report pages
  • SQR layouts → paginated reports
  • FR grids on Essbase / EPM data
  • Reconciliation & cutover

Try us risk-free for 4 hours

Start with a block of prepaid Flex hours and, if you’re unhappy within the first 4 hours, we refund you in full — no questions asked. Inventorying one department’s .bqy documents and SQR programs makes a good first task: it shows the real size of the job before you commit a budget to it.

Start with one department, risk-free →

How we approach it

Logic first, layout second

Every Hyperion report mixes three things in one file: the query, the business rules applied to its results, and the layout. Pulling those apart is what turns a long list of documents into a short list of models and reports.

An inventory before a quote

We list each .bqy document and SQR program with its sections or procedures, the tables it reads, its owner, and how often it actually runs, then mark it rebuild, merge, or retire before any work is priced.

Many data models, one semantic model

IR documents often repeat the same joins with small differences. We consolidate them into one star-schema model per business area, so ten documents that each defined “net sales” end up sharing one measure.

Computed items made explicit

Computed items in Results sections hide business rules in JavaScript-style expressions. Each one becomes either a Power Query column or a named DAX measure, depending on whether it is calculated per row or after aggregation.

SQR split into query and page

An SQR program’s SELECT blocks become a database view or a Power Query query; its headers, footers, breaks, and totals become a paginated report that prints the way the recipient expects.

EPM stays the system of record

Where reports read HFM, Planning, or Essbase, Power BI sits on top as a reporting layer. The consolidation and planning logic is not rebuilt, so the numbers finance signs off on keep coming from the same engine.

Outputs matched, not assumed

Every rebuilt report runs beside its Hyperion original for the same period and filters. Differences are traced to a cause and written down, so sign-off is a comparison rather than a leap of faith.

What does Power BI replace, and what does it not?

Power BI replaces Hyperion’s report content — Interactive Reporting documents, SQR report programs, and the output of Financial Reporting — but not the EPM engines underneath. Consolidation, currency translation, intercompany elimination, and budget write-back stay in HFM, Planning, or Essbase. Power BI can read those engines’ data and present it, which is often exactly what finance wanted from the report layer in the first place.

Which Hyperion components move to Power BI
Hyperion component Moves to Power BI? What we do with it
Interactive Reporting (Brio) documents Yes Rebuilt as a semantic model plus report pages, after inventory and triage
SQR programs that produce reports Yes Query logic to views or Power Query; layout to paginated reports
SQR programs that update or post data No Flagged and left in the application, a stored procedure, or an ETL pipeline
Financial Reporting report output Yes, as a reporting layer Rebuilt as matrix visuals or paginated reports on Essbase or extracted EPM data
Essbase cubes as a data source Read, not replaced Queried through the Essbase connector or extracted to relational tables
HFM consolidation and eliminations No Stays in HFM; Power BI reports on consolidated results
Planning budgets, forecasts and write-back No Stays in Planning; budget-versus-actual is reported in Power BI

Not sure which Hyperion components you can retire? Tell us which department to start with and we will estimate the inventory in hours.

Book a free demo →

That split matters for budget conversations as much as for design. A team that expects to retire the whole Hyperion footprint with Power BI will be disappointed; a team that wants to stop maintaining a library of Brio documents and SQR jobs while EPM keeps closing the books is asking for something Power BI does well.

How do Interactive Reporting and SQR objects map to Power BI?

This is the working map the plan is built from. It is deliberately plain: the value of a migration map is that nothing surprising turns up halfway through, and that every line has an owner who agreed to it.

Hyperion Interactive Reporting and SQR objects and their Power BI equivalents
Hyperion IR / SQR Power BI equivalent What changes in practice
IR Query section and its SQL Power Query query, or a view in the database Repeated queries across documents collapse into one shared source
IR Data Model (tables, joins, topics) Semantic model: fact and dimension tables with relationships Joins are settled once in the model instead of per document
Connection file (.oce) Data source credentials and an on-premises data gateway Connections are managed centrally instead of shipped with each file
Results section computed item Power Query column or DAX measure Row-level versus aggregate logic becomes an explicit modelling choice
Results filters and local joins Model relationships, report filters, or a curated attribute Logic that ran on a user’s desktop moves into the governed model
Table and Pivot sections Table and matrix visuals Users pivot and drill themselves instead of requesting a new document
Chart section Power BI chart visuals Charts filter each other on the same page
Report section (banded layout) Paginated report Groups, page breaks and repeating headers are kept rather than approximated
Dashboard section with JavaScript Report page with slicers, bookmarks and buttons Scripts are not portable; the behaviour is redesigned, not translated
OLAPQuery section on Essbase Essbase connector, or extracted cube data in the model The cube stays the source; storage mode is chosen per report
SQR BEGIN-SELECT blocks and procedures Database view, stored procedure, or Power Query query Data retrieval is separated from formatting and can be tested on its own
SQR ON-BREAK logic, headings and footings Paginated report groups, headers and footers Subtotals and page layout are declared in the report, not coded
SQR output files (printer, PDF, CSV) Paginated report export formats and subscriptions Recipients get the same document; delivery is configured, not scripted
Workspace jobs and schedules Scheduled refresh and subscriptions Refresh and delivery are separate settings instead of one job
Workspace folders and access control Workspace roles, app audiences, and row-level security Who opens a report and which rows they see are handled separately

Two lines carry most of the risk: computed items and Dashboard-section JavaScript. Both hide business rules in places nobody has read for years. That is why we design the model against Microsoft’s star schema guidance (opens in new tab) rather than copying each document’s data model, and why we follow the order in Microsoft’s own Power BI migration guidance (opens in new tab): assess and prioritise the estate before rebuilding any of it. The measure work that follows is the data modeling and DAX half of the job.

How do SQR programs become paginated reports?

An SQR program is a procedural script that selects rows, applies logic, and prints them line by line onto a page. Power BI separates those steps. The data retrieval becomes a view or a query that can be tested on its own, and the layout becomes a paginated report built in Power BI Report Builder (opens in new tab), which controls page breaks, repeating headers, and prints every row across as many pages as it takes.

The first pass through an SQR library is about sorting, not rewriting. Many SQR estates — particularly those that grew up around PeopleSoft — mix true reports with batch programs that insert, update, or post data. Those batch programs are not reports and have no place in Power BI; we flag them so they are handed to whoever owns the application or the ETL, and nothing operational is switched off by accident. Include files shared across programs are read once, because a shared calculation in an include file usually wants to become one shared measure or view.

Paginated reports depend on the capacity or licence your workspace runs on, so confirm current licensing against Microsoft’s documentation before committing to that design. If you already run SQL Server Reporting Services, the SSRS to Power BI migration page covers that format, and its paginated output is the same family SQR layouts land in.

What about Financial Reporting and Essbase data?

Financial Reporting grids are usually the reports finance cares about most: income statements, balance sheets, and variance packs built on Essbase, HFM, or Planning data. Power BI can rebuild that output as a reporting layer — a matrix visual for interactive analysis, or a paginated report where the pack has to print exactly. The account and entity hierarchies come across as dimension tables, and the consolidated or planned numbers stay sourced from the engine that produced them.

There are two ways to reach the data. Power BI Desktop includes an Essbase connector that reads cubes through Essbase Provider Services, which is a reasonable route for a contained cube. For heavier reporting, we often extract the needed slices to relational tables on a schedule instead, so the Power BI model refreshes predictably and month-end reporting does not compete with the cube for resources. We recommend one or the other per business area after looking at cube size and usage, not before.

What does the first phase cost?

We scope the first phase as one business area: the Interactive Reporting documents and SQR programs one department actually runs, after duplicates and dead documents have been retired. Work runs on prepaid Flex hours that never expire — Starter ($2,500), Growth ($4,600), or Power ($8,000), with hourly work from $100/hour. A small, single-source area may fit a Starter block; an area with several data models, heavy computed items, or Financial Reporting packs on Essbase usually needs Growth or Power.

Cost tracks the logic, not the document count. Thirty .bqy files that query the same three tables are a smaller job than eight that each carry their own joins, computed items, and dashboard scripts. You get an estimate in hours per deliverable, approve only what you want built, and unused hours stay banked. See Flex pricing.

How long does it take?

Individual reports typically ship within 3–5 business days of approval once the model is standing, and a phased migration is a sequence of those tasks rather than one big-bang cutover. The model is the front-loaded piece: it is worth building and reconciling first, because every report after it gets cheaper.

Running Hyperion alongside Power BI for one full reporting cycle is worth the overlap. Users compare both outputs on live data, differences get explained rather than argued about, and a business area’s documents are switched off only once their replacements have been through a real month-end.

Who this is for

Finance, operations, and IT teams still running Brio-era Interactive Reporting documents or SQR programs: reports only one or two people know how to refresh, a desktop client that is getting harder to keep on supported machines, or a support decision on the Hyperion stack that has stopped looking like value. Check where your release sits in Oracle’s lifetime support policy before you set a deadline. It is a poor fit if what you really need is a new consolidation or planning system — that is an EPM project, and Power BI is the reporting layer on top of it, not the replacement for it.

Find out which .bqy documents and SQR programs your teams still run before you size the move.

Scope my Hyperion migration →

What you get

  • An inventory of .bqy documents and SQR programs
  • Rebuild, merge, or retire calls for each one
  • A star-schema semantic model with named DAX measures
  • Interactive reports and paginated reports
  • SQR batch jobs flagged, not silently dropped
  • Reconciliation against the Hyperion originals
  • Handover docs and a user walkthrough
1

business area per phase

3–5

business days per report, typical

You

own everything

Start with one department, not the whole library. Comparing routes off different legacy platforms? The migration to Power BI hub covers them side by side, and the OBIEE to Power BI migration page covers the other Oracle estate.

Migration scoping

Four questions that shape your scope estimate

These are the first things we ask before quoting hours for a move to Power BI. Answer what you know; “Not sure” is a fine answer.

How many reports need to move?

The report inventory tells you the true size of the job.

How many data sources feed those reports?

Sources shape the data model we rebuild: its tables, relationships and measures.

Do some people need to see only their own rows (row-level security)?

Who sees which rows is part of the logic we rebuild, not an afterthought.

Which month does your current license renew?

If the renewal is close, it sets the timeline.

Use these answers in my request →

Scope approved before any hours are used · Hours never expire

How it works

From a document library to reporting people trust

  1. 1

    Inventory and triage

    We catalogue the .bqy documents and SQR programs for the business area you nominate — sections, queries, computed items, procedures, tables read, owners and run frequency — and separate reports from batch jobs. You approve the rebuild list and the hours behind it before work starts.

  2. 2

    Rebuild the model, then the reports

    Repeated data models become one star schema with named DAX measures. Pivots, charts and dashboards become interactive report pages, and anything that has to print becomes a paginated report. Essbase or EPM data is connected or extracted as a reporting layer.

  3. 3

    Reconcile, cut over, support

    Each rebuilt report runs beside its Hyperion original for the same period and filters, differences are explained, then we publish, set refresh, security and subscriptions, walk your users through it, and stay available on the hours you have left for the next business area.

Fair and square

Our promises, in plain English

Scope approved before any hours are used

Every request gets a scope estimate and the hours it needs before any work begins, so you approve the cost up front. Hours are deducted only for work you sign off on.

Hours never expire

Your prepaid hours are banked immediately, with no contracts and no recurring charges. Whatever you don’t use stays on your account, with no deadline to spend it by.

You own everything, in your tenant

You receive the report files, the semantic model, the DAX and the documentation, under your own Microsoft tenant and credentials. If you move the work in-house or to another partner, nothing is held hostage.

Refund in your first 4 hours

If you’re unhappy within the first 4 hours of your block, you get a full refund, no questions asked.

Straight answers. If a task is not a good fit for prepaid Flex hours, we will tell you rather than sell you something that will not serve you.

You work directly with Edward Pinela. The consultant who scopes your request is the same person who builds your data model, writes your DAX and designs your reports: a US-based, Microsoft-certified Power BI consultant with 20+ years on the Microsoft platform. No account managers in between, and nothing passed to an offshore team. About Edward

FAQ

Questions teams ask before they commit

No. HFM consolidates entities, translates currencies and eliminates intercompany balances, and Planning captures budgets and forecasts with write-back. Power BI is a reporting and analysis tool and does neither. What it can replace is the report output on top of those engines, reading Essbase or EPM data as a reporting layer while the engines keep running.

Not in any way we would trust with month-end numbers. A .bqy document bundles queries, a data model, computed items, local results and JavaScript in one file. Automated tools can extract the SQL and the section list, which is useful for the inventory, but the model, the measures and the layout still have to be rebuilt and reconciled.

They stay out of Power BI. Many SQR programs, especially in PeopleSoft estates, insert, update or post data as part of a batch process. Power BI only reads data, so those jobs belong in your application, a stored procedure or an ETL pipeline. We flag them during the inventory so nothing operational is switched off by accident.

Power BI Desktop includes an Essbase connector that reads cubes through Essbase Provider Services. It works well for a reporting layer on a contained cube. For larger or heavily used reporting, we often extract the needed slices to a relational table instead, so the Power BI model refreshes predictably and does not load the Essbase server during the day.

One business area: the Interactive Reporting documents and SQR programs one department actually runs, after duplicates and dead documents are retired. That is small enough to scope as a fixed set of tasks, big enough to prove the model and the reconciliation, and it leaves everything else on Hyperion until that department has closed a real month on Power BI.

Find out what your Hyperion library is really carrying

Tell us which department matters most and roughly how many .bqy documents and SQR programs it runs. We’ll scope the inventory and the first rebuild in hours, so you can see the real project before committing to it.

Free demo · Scope approved before any hours are used · Refund in your first 4 hours

Book a free demo

See what your Hyperion reporting would take

Tell us the task. We reply within one business day, and you get a scope estimate and the hours needed before any work begins.

Step 1 of 2: What do you need?

How can we help? Pick one

Tap to add, or type your own:

Step 2 of 2: Where should we reply?

Used only to contact you about this inquiry.

We reply within one business day. Scope approved before any hours are used. We don’t sell your information.

Tell us the task. We scope it, you approve, and a senior consultant delivers — typically in 3–5 business days. Prepaid hours that never expire.

  • Prepaid hours from $100/hour — and they never expire
  • Senior-led delivery — 20+ years on the Microsoft platform
  • Typical 3–5 business day turnaround
  • Full refund if you’re unhappy in your first 4 hours

Related work

This page covers Hyperion’s report content specifically: Interactive Reporting, SQR, and Financial Reporting output. If your Oracle estate is built on Oracle BI Enterprise Edition or Oracle Analytics Server instead, the scope is set by the RPD semantic layer rather than by individual documents, and our OBIEE to Power BI migration page covers that path. If your estate spans several tools, the broader migration to Power BI service handles the Excel and SSRS routes on the same prepaid model. A Pentaho to Power BI migration follows a similar split between report logic and scheduled data jobs, and banded, print-first SQR layouts have a close cousin in our Crystal Reports to Power BI migration work. The rebuild itself is data modeling and DAX work, and teams standing up their first workspace usually pair it with Power BI consulting for the licensing and governance decisions a rollout brings. Every task is scoped before work begins from your prepaid block of senior-led hours, and hours are deducted only for work you approve.

Book my free demo