Concept card

SAP Lumira (Discovery & Designer)

As of 2026-09-27

Edited by Cédric-Olivier Mâry, sole editor and publication director — 27 years in the SAP ecosystem. How these pages are produced, and where automation is used.

What is SAP Lumira (Discovery & Designer)?

One brand covering two unrelated products: Lumira Discovery, the self-service visualisation desktop, and Lumira Designer, the renamed Design Studio. Reading them as one product is the single most common mistake in a Lumira migration.

What it is

SAP Lumira is a brand that covered two products with different origins, different users and different migration paths — and conflating them is the most reliable way to misprice a Lumira engagement.

Lumira Discovery is the self-service line: a desktop tool where an analyst acquires a dataset, prepares it, and builds visualisations without a server-side semantic model. It grew out of SAP's response to the self-service wave, and its users are analysts working on their own data, frequently outside IT governance entirely.

Lumira Designer is Design Studio under a later name: the scripted BI application designer with an extension SDK, used by developers to build governed, event-driven analytic applications on BW and HANA. Its users are developers, its artefacts are applications, and its residue is code.

The two land in different places. Discovery content maps toward SAC's story and exploration surfaces, and its migration difficulty is dominated by an ungoverned data question — where did the analyst's dataset come from, and does the target let them get it the same way. Designer content maps toward SAC Analytic Applications, and its difficulty is dominated by custom SDK components that have to be rebuilt as custom widgets. A single plan that says "migrate Lumira" without splitting these two will be wrong about both.

Why it matters

Two products under one brand, with different users, different successors and different cost drivers. A plan that does not split them is wrong about both halves.

Key points

🔴 One brand, two products: Lumira Discovery (self-service desktop) and Lumira Designer (Design Studio renamed).
Discovery users are analysts with their own datasets, frequently outside IT governance.
Designer users are developers; its artefacts are scripted applications and its residue is SDK code.
Discovery lands on SAC stories and exploration; Designer lands on SAC Analytic Applications.
Establish which Lumira, and who uses it, before any estimate — many estates run both with no shared owner.
Two decisions, not one: a governance decision for Discovery (governed path or accepted shadow estate) and a per-component rebuild decision for Designer.
The two halves differ in NATURE, not size — one is cultural and slow, the other technical and estimable; a single date hides the slow one.

Terms used on this page

Lumira Discovery: The self-service desktop line: acquire, prepare and visualise a dataset without a server-side semantic model.
Lumira Designer: SAP BusinessObjects Design Studio under a later product name — scripted BI applications with an extension SDK.
Dataset acquisition: How a Discovery analyst obtained the data. Frequently undocumented, and the real subject of a Discovery migration.
Story: The SAC artefact that plays the role Discovery visualisations played, on a governed foundation.
Shadow estate: Analyst-owned datasets and desktop content living outside any governed source. The Discovery migration's real subject, and invisible to a server-side inventory.
Brand collision: One product name covering two unrelated products. It is why previous estimates at the same customer came back inconsistent, and naming it is often the first value a consultant delivers.

Sources

Full card available to members. What the full card adds: the full decision framework · the SAP vs Snowflake / Databricks / Fabric comparison · the common pitfalls and their fix · the cheat sheet · the architecture schemas · the code blocks · the facts worth quoting.

Open in the app →