Key takeaways
- Cognos, SAP BusinessObjects and MicroStrategy moves share one sequence: inventory, a warehouse semantic layer, a parallel run, then cutover.
- Each of these tools has its own modelling layer (Framework Manager packages, universes, schema objects), and that is where the business definitions live today.
- Rebuild those definitions once on the warehouse, then point the new BI tool at them, so the next tool change does not repeat the work.
- Power BI is a common destination. Tableau, Sigma, Omni and Looker are also reasonable choices, depending on who builds the reports.
- Crystal Reports belongs with SSRS in its own guide, because paginated reports raise different questions.
- 01Inventory reports and metrics
Usage, owners and logic
- 02Warehouse semantic layer
One definition per metric
- 03Parallel run and cutover
Totals and access compared
- 04Cognos, BusinessObjects, MicroStrategy
Tool-specific notes below
- 05Crystal
See the SSRS and Crystal guide
What does this guide cover?
This guide is for teams moving off one of the long-standing enterprise BI platforms: IBM Cognos Analytics, SAP BusinessObjects and MicroStrategy, which now trades as Strategy. It covers the plan that applies to all three and the specific traps in each. The BI migration checklist has the step-by-step exit checks.
What is the shared sequence?
These platforms all put a modelling layer between the database and the report. Report authors built on that layer for years, so the business logic is spread across the model and thousands of reports. A migration that copies report layouts into a new tool loses that logic.
- Pull usage logs and list every report, its owner and when it was last opened. Agree which reports to rebuild, merge or retire.
- Export the modelling layer and the calculations inside reports, and write one definition for each metric that survives.
- Build those definitions in a semantic layer on your warehouse, then rebuild the surviving reports in the destination tool on that layer.
- Run old and new in parallel, comparing totals by period and segment and testing access with real users.
- Cut over wave by wave with owner sign-off, then switch off the old server and licences.
Cognos to Power BI
In Cognos the definitions usually sit in Framework Manager packages or data modules, with more logic in report-level calculations and prompts. Export the packages, list the query subjects that reports actually use, and treat prompt logic as requirements for filters in the new tool. Microsoft’s Power BI migration series describes a staged plan that starts with a prioritised inventory, and it applies here.
SAP BusinessObjects
BusinessObjects reports sit on universes, built in the Information Design Tool or the older Universe Design Tool, and Web Intelligence documents add their own variables. The universe is the closest thing the estate has to a semantic layer, so map its objects and joins to warehouse definitions first. Teams staying with SAP usually look at SAP Analytics Cloud, and teams leaving usually pick Power BI or Tableau.
MicroStrategy to Power BI
MicroStrategy, now Strategy One, keeps its logic in schema objects such as attributes, facts and metrics, with filters and prompts layered on top. That schema is well structured, which makes it a good source for a metric map. We phrase this section as MicroStrategy to Power BI because that is the move most teams search for, and Sigma, Tableau or Omni work as destinations too.
What about Crystal Reports?
Crystal Reports estates are mostly pixel-perfect operational reports such as invoices and statements, and they often sit next to SSRS on SQL Server. The SSRS and Crystal Reports migration guide covers them, including the SQL Server 2016 support dates.
Has anyone done this with Rig?
Birdie replaced its legacy BI dashboards with Rig and moved its metric definitions and dbt models onto its own Snowflake as certified metrics. Its RevOps lead had spent about three months building the original reporting and said they rebuilt virtually all of the reports in less than a day. The Birdie case study has the detail.
Legacy BI migration checklist
Use these as the exit checks for each wave.
- Usage logs pulled and every report has an owner and a decision.
- Modelling layer exported: packages, universes or schema objects.
- Report-level calculations and prompts listed with their logic.
- One warehouse definition per surviving metric, with an owner.
- Totals match by period and segment for a full reporting cycle.
- Row-level rules and folder permissions tested with real users.
- Scheduled deliveries and bursting rebuilt or retired.
- Old server and licences have a switch-off date.
Where does Rig fit?
Rig is an AI-native data and systems integrator. An in-house team can follow the vendor tools listed below, specialist BI partners and large systems integrators staff programmes like this, and teams often use an AI-native data and systems integrator like Rig to run the inventory, mapping, parallel run and cutover, and to leave the metrics in Rig Map.
Rig Migrate scopes the work and agrees a fixed delivery price first. Gateway then gives people and AI agents governed access to the rebuilt metrics. The MicroStrategy migration page and the BI migration page describe the service.
Tools and approaches
- Microsoft Power BI migration guidance
- A staged migration series for moving from another BI platform to Power BI, from pre-migration steps to deployment and monitoring.
- IBM Cognos Analytics
- IBM’s BI platform, with Framework Manager packages and data modules as its modelling layer.
- SAP BusinessObjects BI Platform
- SAP’s BI platform, where Web Intelligence reports read universes built in the Information Design Tool.
- Strategy One (formerly MicroStrategy)
- Strategy’s BI platform, which keeps attributes, facts and metrics in a shared schema.
Common questions
How do you migrate off legacy BI?
Inventory the reports people still use, export the modelling layer and report calculations, rebuild each metric once in a warehouse semantic layer, rebuild the reports on that layer, run old and new in parallel, then cut over wave by wave.
Should we lift and shift the dashboards?
Lift only the layouts, and only for reports people still use. The definitions behind them should move to a warehouse semantic layer so the new tool and any AI agents read the same numbers.
Do we have to pick Power BI as the destination?
No. Power BI is common, and Tableau, Sigma, Omni and Looker are all reasonable destinations. Choose by who builds the reports and how they want to work, then test a representative report.
Why do you say MicroStrategy to Power BI?
MicroStrategy now trades as Strategy, and its BI product is called Strategy One. Most teams still describe this move with the old product name, so we use the phrase they search for.
Who usually runs the mapping and cutover?
An in-house team can do this with the vendor’s own tools, a systems integrator can staff the programme, or an AI-native data and systems integrator like Rig can run the mapping and cutover.
Sources
Vendor documentation checked on 20 November 2026. Confirm current features and terms with the vendor.