SAP is not pulling the plug on BusinessObjects anytime soon. On 15 October 2026, the vendor announced it was abandoning any fixed end-of-maintenance date for its long-standing Business Intelligence platform, committing to maintaining and evolving it through at least 2029 (LeMagIT, 15 October 2026). For the hundreds of IT departments that had launched emergency BI migration projects, the question is now immediate: press on with the migration, or pause?
Background: The uncertainty that pushed CIOs into emergency mode
BusinessObjects — acquired by SAP in 2007 — has long been the de facto standard for BI reporting in large enterprises and mid-market companies running SAP. For years, SAP pushed customers toward SAP Analytics Cloud (SAC), its cloud-native successor, and had communicated an end of mainstream maintenance for BusinessObjects BI 4.3 on 31 December 2026 (SAP Product Availability Matrix).
That date triggered a wave of migration projects. Organisations committed budgets, issued integrator RFPs, and kicked off reconfiguration programmes targeting SAC, Power BI, or other BI platforms. The urgency was real: staying on a version without mainstream maintenance meant unpatched security vulnerabilities and progressive incompatibility with SAP ERP updates.
The October 2026 reversal changes this landscape significantly.
Impact for organisations: three situations to consider
If you have not yet launched your BI migration. The urgency pressure is gone. SAP published a new Statement of Direction in October 2026 confirming a structured product roadmap: BI 2025 (already available), BI 2027, and BI 2029 are all planned, with mainstream maintenance guaranteed through end-2031 for BI 2029 (SAP Statement of Direction BusinessObjects, October 2026). You now have time to build a decision grounded in functional needs, not calendar pressure.
If your migration is already underway. This is not an automatic stop signal. The question to put to your project team: “Are we migrating because BusinessObjects is dead, or because SAC/Power BI better meets our future needs?” If the answer is the latter, continue — the decision remains valid regardless of SAP’s announcement. If the answer is the former, a decision pause is legitimate.
If you are still running BI 4.3. Caution: the indefinite postponement concerns the product discontinuation, not the end of maintenance for BI 4.3 specifically. This version still loses Mainstream Maintenance on 31 December 2026. Upgrading to BI 2025 is still recommended to stay within the supported perimeter — this is a version upgrade, not a platform migration.
What to watch in the coming months
Two points deserve close attention over the next months.
First, the real depth of SAP’s commitment. A Statement of Direction is not a commercial contract. SAP has modified product roadmaps before. The genuine signal will be the delivery cadence of BI 2027 and the R&D investment announced for the on-premise platform. Strategic customers should request contractual commitments in their next maintenance renewal cycles.
Second, the integrator market for BI. Many SAP partners have built BusinessObjects-to-SAC or BusinessObjects-to-Power BI migration practices over the past two years. This reversal may create friction: signed projects could be called into question, and teams trained on migration methodology may find their pipeline shrinking. CIOs who have engaged consultants on active migration projects should revisit their contracts carefully before any renegotiation decision.
For a deeper look at managing your SAP estate, read our analysis on SAP license audits and the annual true-up: reducing your exposure and our guide on BI embedded in ERP systems: reporting, dashboards and analytics to frame the choice between dedicated and embedded BI. For the broader SAP strategic context in the DACH region, see our article on the Vinci Energies acquisition of All for One and its impact on SAP customers.
