SAP BusinessObjects BI End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all SAP BusinessObjects BI versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
SAP BusinessObjects BI BI 4.3 is supported, with no end-of-life or end-of-support date announced yet. The next SAP BusinessObjects BI version to reach end of life is BI 2025 (4.4), on December 31, 2028. 3 of 5 tracked SAP BusinessObjects BI versions are past end of life; the most recent to reach it, BI 4.2, did so on December 31, 2024. The full SAP BusinessObjects BI lifecycle, with every version's release and end-of-support date, is in the table below.
Running an EOL version? Get matched with support options — free ↓| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| BI 4.0 | 4.0 SP12 | — | Dec 31, 2017 | 3206 days past EOL | EOL |
| BI 4.1 | 4.1 SP12 | — | Dec 31, 2020 | 2110 days past EOL | EOL |
| BI 4.2 | 4.2 SP09 | — | Dec 31, 2024 | 649 days past EOL | EOL |
| BI 4.3 | 4.3 SP05 | — | TBD | Supported | Active |
| BI 2025 (4.4) | BI 2025 | — | Dec 31, 2028 | 812 days remaining | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/sap-businessobjects)
SAP BusinessObjects BI lifecycle status — the real story
SAP BusinessObjects Business Intelligence (BI) platform is SAP's on-premise reporting suite (Web Intelligence, Crystal Reports for Enterprise, the Central Management Console). SAP publishes its maintenance ends in the public BI Support Packages End of Life Dates PDF and in the BI maintenance strategy document: BI 4.3 mainstream maintenance ends December 2026 (SAP's knowledge base article 3763590 gives the day, 31 December 2026), after a one-year extension; BI 2025 (internally 4.4) runs in mainstream maintenance until December 2027; BI 4.2 ended mainstream maintenance in December 2022 and its Priority 1 support phase on December 31, 2024.
"End of support" here is the end of mainstream maintenance, and "end of life" is the end of the last phase in which SAP still ships fixes: the two-year Priority 1 support phase for 4.x releases, in which "Patches are delivered on demand and only for critical priority one issues", and for BI 2025 the first twelve months of Customer Specific Maintenance, during which SAP says "We will deliver security fixes during the first 12 months of CSM for VH and H security issues (CVSS >= 7.0)". Neither phase is a paid add-on. BI 4.3 will also have such a CSM window after 2026, but SAP prints no date for its end, so no end-of-life date is shown for 4.3. SAP publishes support-package and patch dates as months; dates here are the last day of SAP's month.
Future releases follow a three-year pattern in SAP's strategy document (BI 2027 to 2029, BI 2029 to 2031). CISA's Known Exploited Vulnerabilities catalog has no BusinessObjects entry (catalog 2026.10.08). The SAP Product Availability Matrix is login-gated and was not used.
SAP BusinessObjects BI release and support pattern
Of the 5 release lines tracked, 3 are past end of life and 2 are still within support. The next scheduled end of life is 2025 on December 31, 2028 — 812 days from this build.
Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.
What does SAP BusinessObjects BI end of life mean for your organization?
When a version of SAP BusinessObjects BI reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: A CVE-based scan does not show the accumulation of unpatched vulnerabilities in EOL software. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no vendor patch is coming. This is one of the most dangerous gaps in enterprise security posture.
Organizations running EOL SAP BusinessObjects BI should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Your options when SAP BusinessObjects BI reaches end of life
There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.
| Option | Best when | Watch out for |
|---|---|---|
| Move to a supported version | The system will outlive the current version's support window and you can schedule the work | Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits |
| Replace the component | The project is unmaintained, or a better-supported alternative exists | The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem |
| Buy extended support | Migration is genuinely underway but cannot finish before the deadline, or the workload is frozen by certification or a third-party application | A bridge, not a destination — every year purchased is a year the migration still has to happen |
| Document accepted risk | The system is isolated, short-lived, or scheduled for retirement | Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding |
How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.
Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.
Formalizing decisions like this across your estate? Our free EOL policy template is a ready-to-adopt policy with risk tiers, remediation SLAs, and audit mapping — no signup, free to use and share.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL SAP BusinessObjects BI versions. This is a bridge, not a permanent solution — plan your migration in parallel.
SAP BusinessObjects BI has 3 versions past end of life — security patches have stopped, but CVE disclosures haven't. Extended support past the official date exists for many products in this position — whether it exists for SAP BusinessObjects BI is exactly what we check. Tell us where to reach you and we'll reply with matched options and pricing guidance — or an honest "no vendor covers this."