Is Crystal Reports going away? No. SAP released Crystal Reports 2025 in March 2025, maintains it until 31 December 2027, and plans new releases in 2027 and 2029. Crystal Reports end of life happens one version at a time: Crystal Reports 2020 leaves mainstream maintenance on 31 December 2026, and SAP no longer supports its 32-bit .NET runtime.
Below: SAP's dates, how Crystal lines up with BusinessObjects BI, the .NET and 64-bit limits that cause the real trouble, and what to inventory inside your reports.
- No. SAP released Crystal Reports 2025 in March 2025, maintains it to 31 December 2027, and plans new versions for 2027 and 2029.
- Versions end. Mainstream maintenance for Crystal Reports 2020 ends on 31 December 2026, the same day as BusinessObjects BI 4.3.
- Crystal Reports for Visual Studio runs on .NET Framework only, and SAP dropped its 32-bit runtime after December 2025.
- The bigger risk is inside the reports: SQL, formulas and subreports holding business rules nobody wrote down.
Is Crystal Reports going away?
Not according to SAP. Its maintenance dates page lists Crystal Reports 2027 and 2029 as planned versions and says: "We already plan for a next release, BI 2027, which should be available in Q1 2027, followed by another one 2 years later. As we write this document, Mainstream Maintenance is guaranteed until at least end of 2031."
The rumor usually starts from one of three real changes:
- A version is ending. Crystal Reports 2020, its Viewer and Crystal Server 2020 leave mainstream maintenance on 31 December 2026.
- A different product went away. SAP's BI maintenance strategy, updated October 2026, lists Crystal Reports for Enterprise among the components no longer delivered with BI 2025.
- The 32-bit runtime is gone. SAP's notes for Service Pack 40 of Crystal Reports for Visual Studio say "32bit runtime and merge modules are no longer supported."
So the useful question is which version, runtime and bitness each of your reports depends on.
SAP Crystal Reports end of life dates
| Product | Released | End of mainstream maintenance |
|---|---|---|
| Crystal Reports 2025, Viewer 2025, Crystal Server 2025 | 12 March 2025 | 31 December 2027 |
| Crystal Reports 2020, Viewer 2020, Crystal Server 2020 | 6 June 2020 | 31 December 2026 |
| Crystal Reports 2016 | 8 March 2016 | 31 December 2022 (priority-one support ended 31 December 2024) |
| Crystal Reports, developer version for Visual Studio | 12 November 2010 | 31 December 2029 |
| Crystal Reports 2027 (planned) | Estimated Q1 2027 | 31 December 2029 |
| Crystal Reports 2029 (planned) | Estimated Q1 2029 | 31 December 2031 |
Checked 30 October 2026 against SAP's End of Mainstream Maintenance Dates page. SAP's Crystal download page still shows 31 December 2027 for Visual Studio, and SAP says its Product Availability Matrix wins where dates disagree. Check the PAM for your build.
After mainstream maintenance, SAP's page says customer-specific maintenance follows. SAP's BI maintenance strategy describes that phase as security corrections rated CVSS 7.0 or higher for the first 12 months, then support without new software deliveries. For the desktop designer, SAP's Crystal FAQ says "There is no maintenance or software assurance program." For a version already past its dates, see the risks of running end-of-life software.
How does Crystal Reports line up with BI 4.3 and BI 2025?
Version for version. SAP's FAQ pairs each Crystal release with a Crystal Server and BI platform release, and says "SAP Crystal follows the same maintenance schedule as SAP BusinessObjects."
| Crystal Reports | BI platform | What SAP says about the platform |
|---|---|---|
| 2020 (version 14.3) | BI 4.3 | Mainstream maintenance ends 31 December 2026; customer-specific maintenance from January 2027 |
| 2025 | BI 2025 | Supported beyond 2027 with customer-specific maintenance |
| 2027 (planned) | BI 2027 | Expected Q1 2027; SAP plans a release every two years, each with three years of mainstream maintenance |
Two more changes matter on the platform: from BI 4.3 SP02, Crystal Reports 2020 is supported on Windows only, and BI 2025 drops Crystal Reports for Enterprise. If MicroStrategy sits beside Crystal, it has its own end-of-support date.
Is Crystal Reports obsolete? The .NET and 64-bit limits
Not obsolete, but the runtime that embeds reports in your own .NET applications, Crystal Reports for Visual Studio, is tied to older technology.
SAP's FAQ is blunt: "SAP Crystal Reports for Visual Studio depends on a lot of .NET Framework-specific features. There are NO plans to update to Framework higher than 4.8, at this point." It places .NET 5 and later in the .NET Core line and advises: "don't use those CORE versions if you want to continue using SAP Crystal Reports." The runtime is still maintained: Service Pack 40 adds Visual Studio 2026 support.
| Constraint | What SAP or Microsoft says | What it means |
|---|---|---|
| .NET Framework only | No plans past Framework 4.8 (SAP FAQ) | An app that embeds Crystal can't move to .NET 8 or 10 without replacing its reporting |
| Framework support follows Windows | .NET Framework 4.8.1 is supported "as long as it is installed on a supported version of Windows" (Microsoft) | Each server's Windows version is the deadline; see .NET Framework 4.8 end of support |
| 64-bit only | "Recompile your applications as 64 bit applications" and install 64-bit database clients (SAP) | Old 32-bit ODBC and OLE DB connections must be found and replaced |
| Report file versions | Older reports opened in Crystal Reports 2020 or 2025 need a 64-bit connection, then save as version 14.3 (SAP FAQ) | Upgrading is a per-report job |
What to inventory in your Crystal reports
Counting report files is easy. What's inside them decides whether an upgrade is routine or a project.
| What to record | Why it matters | Where it lives |
|---|---|---|
| Data source and driver | 64-bit Crystal needs 64-bit connections; one report may read several databases | Database Expert, Set Datasource Location |
| Embedded SQL | SQL commands and SQL expressions can hold joins and filters nobody documented | Add Command; Formula Workshop |
| Formulas | Record selection formulas decide which rows count; others calculate totals and flags | Formula Workshop |
| Subreports | Each has its own data source and links to the main report | Every subreport |
| Who reads it, and how it runs | Unread reports can be retired; scheduled ones have recipients who'll notice | Server schedules, the embedding app, the people who ask for it |
SAP's Crystal Reports 2020 user guide says "A subreport is a report within a report," and describes SQL expressions as "like formulas, but they are written in Structured Query Language (SQL)." A selection formula that defines an active customer is a business rule, and business rule extraction applies to it. Old report estates belong on any honest list of legacy system examples.
Where the 30-day assessment fits before an upgrade
Knowing what your reports do decides whether you upgrade them, rebuild them elsewhere or retire half of them. The 30-day assessment is fixed in scope, at a price agreed before we start. Over 30 days we read the codebase and the architecture around it, including the applications that embed the Crystal runtime and the SQL and formulas inside the reports. We map how the pieces fit together, find the hidden architectural debt, and flag security and compliance gaps, starting with anything on an unsupported runtime or Windows version.
The report says in plain language what is broken and what it would take to fix it. Your own team can act on it, or we can do the work as a separate project with its own scope and price. The report stands on its own either way. If a narrower check, such as listing every report still on a 32-bit connection, would answer your question, we'll tell you.
Pick a time to talk, and bring a rough count of your reports and where they run.