Context: why BI 2025 is not just another upgrade
Unlike previous Service Packs, BI 2025 is not an incremental update. It is a re-plateforme. SAP has used this release to clean up fifteen years of legacy and refocus the suite on its most widely used components.
In practical terms, entire components are being removed. If your organisation uses UNV universes, Lumira Discovery reports, multi-source connections or Analysis OLAP, these tools will no longer be supported in BI 2025.
At the same time, SAP is modernising the technical foundations: migration to SapMachine JRE 17 (Java 17), 32-bit support dropped, new authentication methods (SAML, OIDC), and deeper integration with SAP Datasphere.
SAP's message is clear: BusinessObjects remains on the roadmap until at least 2035, but only for organisations willing to modernise. The strategy is straightforward — consolidate, simplify, and bring BO closer to the SAP cloud ecosystem.
What's new in BI 2025
BI 2025 is not just a list of removals. SAP is introducing significant improvements for the tools that remain in scope.
Web Intelligence
The biggest innovation in Webi is the introduction of SAPUI5 report elements: scrollable tables, interactive filters, containers, CSS editor, and rich text. These elements coexist with classic BI 4.3 elements (which remain supported) but provide a significantly more modern authoring experience.
The WIDX format is an interactive export anyone can open — no BI server access, no licence. A major shift for report distribution outside the organisation.
Another notable improvement: the chart data point limit increases from 50,000 to 250,000 — a 5x gain resolving a recurring pain point for large reports.
Semantic Layer and connectivity
BI 2025 certifies direct and UNX access to SAP Datasphere, SAP HANA Cloud and SAP BW/4HANA. OAuth 2.0 authentication is now supported, and publishing to Google Drive and Microsoft OneDrive is natively integrated.
SAP is not replacing BusinessObjects with Datasphere — it's integrating them. Data federation between the two platforms is becoming smoother, paving the way for progressive coexistence.
Security and authentication
SAML and OpenID Connect (OIDC) become first-class citizens. Certified identity providers include Azure Entra (formerly Azure AD), Google and SAML 2.0-compatible IdPs. Essential for hybrid cloud/on-premise deployments.
Infrastructure
BI 2025 requires SapMachine JRE 17, 64-bit only support (Windows Server 2022+ and Linux distributions modernes), et retire le support AIX, Solaris et NetWeaver Java. The compatibility matrix is now more restrictive but also more modern.
What's retiring: removed components
This is the most critical area for existing organisations. The list of retired components in BI 2025 is extensive, and several are still widely used.
| Component | Status BI 2025 | Alternative SAP | Impact |
|---|---|---|---|
| Univers UNV (Universe Design Tool) | Retired | UNX (Information Design Tool) | Critical |
| Univers multi-sources UNX | Retired | Federation via Datasphere | Critical |
| Lumira Discovery | Retired | SAP Analytics Cloud | High |
| Analysis OLAP | Retired | Analysis for Office / SAC | High |
| Live Office | Retired | Analysis for Office | Medium |
| SAP BO Mobile | Retired | BI Launchpad responsive | Medium |
| Lumira Designer | Maintained, no new features | SAP Analytics Cloud | Low (eventually) |
| WACS | Retired | Tomcat native | Low |
| SharePoint/Portal integrations | Retired | Publication OneDrive/GDrive | Low |
The critical point: UNV universes. If your organisation still uses UNV-format universes (created with the legacy Universe Design Tool), they will not work in BI 2025. Conversion to UNX is mandatory.
The full roadmap: from BI 4.2 to BI 2029
The October 2025 Statement of Direction and the July 2025 announcement (with SP5 for BI 4.3) give a clear view of the SAP BusinessObjects roadmap for the next 10 years.
Key point: SAP's new maintenance strategy provides 3 years of support per version, with patches every 6-8 weeks (traditional Service Packs are discontinued).
Your 5-step action plan
Regardless of your current version, here are the steps we recommend to our clients.
Step 1 — Inventory and audit of your estate
Start with a complete inventory of your environment: number of universes (UNV vs UNX), Webi and Crystal reports, components in use (Lumira Discovery? Analysis OLAP? Explorer?), and connected data sources.
At Decinova, our Audit pillar performs this inventory automatically. For SAP BO universes, we map every object, every join, every source, and deliver a ready-to-use report within 48 hours.
Step 2 — Identify your dependencies on retired components
This is the most urgent step. If you use UNV universes, multi-source universes, Lumira Discovery or Analysis OLAP, these must be migrated or replaced before any upgrade.
Step 3 — Convert your UNV universes to UNX
This is usually the heaviest workstream. UNV → UNX conversion is not truly automatic — SAP's conversion tool handles simple cases but fails on complex universes (multi-source, derived, cross-context).
Step 4 — Choose your migration path
Two main options are available:
Migrate to BI 2025 (or wait for BI 2027 if you have time). This is the least disruptive path if your Webi and Crystal estate is substantial and your teams are trained on the SAP stack.
Path 2: Migrate to a modern stack. You take advantage of this forced transition to migrate all or part of your estate to Power BI, Snowflake, or another cloud stack. This is the more ambitious path but offers the greatest long-term modernisation.
Decinova supports both scenarios. For option B, our proprietary SAP BO → Snowflake converter drastically accelerates the semantic layer migration.
Step 5 — Plan and execute in waves
Don't attempt a big bang. Prioritise critical components (UNV universes first), validate in batches, and maintain a parallel old/new run during the transition. This is how you avoid production disruption.
Conclusion
SAP BusinessObjects BI 2025 is good news for the SAP BO ecosystem — it confirms SAP's long-term commitment (maintenance through 2035). But it's also a strong signal: deprecated components are being removed, and organisations that fail to plan will find themselves stuck.
If you're still on BI 4.2, you're already out of support. If you're on BI 4.3, you have until end of 2027 for mainstream — but UNV → UNX conversion and retired component assessment should start now.
Need support? Decinova delivers comprehensive SAP BO estate audits, supports UNV → UNX conversions, and migrates universes to Snowflake using its automated converter. First audit free within 48 hours.