DataViz Migration - migrating from SAP BO to GCP Looker

Thu, 02 Jul 2026 00:00:00 +0000

SAP BusinessObjects estates typically hold several years’ worth of modeling: universes, Web Intelligence reports, business objects, calculations, filters, prompts, and semantic layers.

{openAudit} analyzes these components to reconstruct the dependencies between data sources, universes, reports, and observed usage.

Key point: universes and business objects are generally the primary source of information for reconstructing the target model.

SAP BusinessObjects analysis prerequisites

The analysis relies on access to the SAP BusinessObjects services, technical repositories, and the audit database.

The extractors run within the Client’s environment. The collected metadata can be anonymized before processing.

Good to know: only technical metadata is used.

Estate analysis

The analysis covers Web Intelligence reports, UNV and UNX universes, Data Providers, business objects, variables, filters, prompts, and graphical components.

Technical dependencies and observed usage are consolidated into a repository.

Rationalization

Audit logs are cross-referenced with the platform’s metadata.

Unused or broken reports, duplicated reports, unconsumed objects, obsolete universes, etc. are identified before migration.

Result: a massive reduction in the volume to migrate.

Conversion to Looker

Data Providers, business objects, and queries are converted into Looker components.

Dimensions, measures, joins, and calculations are reconstructed in the LookML models.

Dashboards, filters, prompts, tables, charts, and navigation mechanisms are reconstructed from the SAP BusinessObjects reports.

The functional organization of the universes carries over into the target platform’s folders, Explores, and business catalogs.

Key point: functional objects and reporting components are reconstructed from the SAP BusinessObjects universes and reports.

Validation

Migrations can be carried out with dual SAP BusinessObjects / Looker execution.

The indicators produced by both platforms are compared during acceptance testing phases.

SAP BusinessObjects prompts

SAP BusinessObjects prompts are converted into Looker’s native filters.

Value lists and input parameters are preserved.

Business objects and LookML models

Queries, business objects, dimensions, measures, and joins are converted into LookML components.

Functional structure

The organization of the universes is rebuilt as Explores, dimensions, and measures.

Pivots and matrix analyses

Cross-tabs and multidimensional analyses are converted into Looker’s pivot mechanisms.

Charts

Trend lines and comparative analyses are rebuilt from the indicators identified in the reports.

Bar charts

Bar charts are adapted to Looker’s visualization components.

Pie charts

Pie charts are converted into Looker’s native visualizations.

DataViz Migration - migrating from SAP BO to Power BI

Thu, 02 Jul 2026 00:00:00 +0000

SAP BusinessObjects estates typically hold several years’ worth of modeling: universes, Web Intelligence reports, business objects, calculations, filters, prompts, and semantic layers.

{openAudit} analyzes universes, reports, and usage logs to reconstruct the dependencies between data sources, business objects, and visualizations.

Key point: the migration covers universes, business objects, and business rules just as much as reports.

SAP BusinessObjects analysis prerequisites

The analysis requires access to the SAP BusinessObjects services, technical repositories, and the audit database.

The extractors run within the Client’s environment. The collected metadata can be anonymized before processing.

Good to know: only technical metadata is used.

Estate analysis

The analysis covers Web Intelligence reports, UNV and UNX universes, Data Providers, business objects, variables, filters, prompts, and graphical components.

Technical dependencies and observed usage are consolidated into a repository.

Rationalization

Audit logs are cross-referenced with the platform’s metadata.

Unused reports, duplicates, unconsumed objects, and obsolete universes are identified before migration.

Result: a reduced volume to migrate.

Conversion to Power BI

Data Providers are converted into Power BI datasets.

Queries, calculations, and variables are converted into SQL or DAX. Business objects are reconstructed as dimensions and measures.

Dependencies between universes, reports, and data sources are preserved in the target model.

Tables, charts, filters, sections, and layout elements are analyzed and then reconstructed in Power BI.

Key point: the migration covers both the business layer and the reporting layer.

Validation

Migrations can be carried out with dual SAP BusinessObjects / Power BI execution.

The indicators produced by both platforms are compared during acceptance testing phases.

Tables, filters, and slicers

Conversion of SAP BusinessObjects tables, filters, and sections into Power BI components.

Pie charts

Conversion of SAP BusinessObjects pie charts into Power BI visuals.

Charts

Conversion of SAP BusinessObjects charts into Power BI visuals.

Dashboards

Conversion of SAP BusinessObjects dashboards into Power BI.

Universe |

DataViz Migration - migrating from SAP BO to GCP Looker

SAP BusinessObjects analysis prerequisites

Estate analysis

Rationalization

Conversion to Looker

Validation

SAP BusinessObjects prompts

Business objects and LookML models

Functional structure

Pivots and matrix analyses

Charts

Bar charts

Pie charts

DataViz Migration - migrating from SAP BO to Power BI

SAP BusinessObjects analysis prerequisites

Estate analysis

Rationalization

Conversion to Power BI

Validation

Tables, filters, and slicers

Pie charts

Charts

Dashboards