Service · Software development

Replace Crystal Reports with a modern reporting solution.

At the press of a button, an invoice, an overview or a management report rolls out of an .rpt file that has sometimes been around for twenty years, built on a Delphi, FoxPro or older .NET system. Crystal Reports usually still runs fine, until the runtime stops being updated, the licence changes via SAP, or the one colleague who can modify the reports is no longer around. We replace that standalone reporting layer with a modern solution, without losing the knowledge that currently lives only in the old files.

▤

A reporting layer nobody dares to touch.

Crystal Reports rarely stands on its own. In almost every project we come across, it sits as a standalone reporting layer on top of a business application that has itself been around for years: a Delphi application, a FoxPro system or an older .NET or VB6 environment. The underlying application handles the business logic, while Crystal Reports delivers the invoices, overviews and management reports around it, via an SDK that was embedded decades ago and has not been touched since.

That works, until it doesn't. Crystal Reports is owned by SAP, and not every older version of the runtime has been developed further for the latest platforms; some ran for a long time only as a 32-bit component. Newer versions fall under a different licensing model than the version you originally started with. And the reports themselves, the .rpt files with their embedded queries and formulas, are designed so that you open them in the Crystal Reports designer or nowhere. That literally ties the knowledge of what a report actually does to whoever can still operate that designer, often a single person.

The result is a silent dependency: reports that management, accounting or customers see every week, but that nobody can change without first working out what was built into them. Meanwhile, the rest of the organisation keeps working with static PDF exports, while other departments are long used to dashboards they can click through themselves. This fits a broader pattern we see more often when replacing legacy software and modernising legacy software: the reporting layer is often not the first thing an organisation thinks of, but it is the first place where the pain becomes noticeable.

How we approach Crystal Reports projects.

Inventory first
We map which .rpt reports are actually being used
Rebuilding queries
The logic in the report is separated out and made readable
Modern BI layer
Built-in dashboards or a BI tool with a direct data source integration
Knowledge shared
Documentation instead of knowledge locked in a single .rpt file

Three steps to move away from Crystal Reports.

You don't replace a reporting layer by converting every .rpt file one-to-one. Most of the value comes from first looking carefully at what is actually used, then rebuilding the underlying logic, and only then choosing the new reporting format.

Step 01

Identifying which reports are really used

Almost always fewer than the reports folder suggests

In most organisations, the reports folder holds dozens of .rpt files, built up over the years for projects, audits or one-off questions that were wrapped up long ago. For each report, we establish when it was last run, by whom and for what purpose, rather than going on what is "surely still important". We do this through conversations with the people who actually use them, usually in accounting, management or customer service, supplemented by what the system itself shows about usage frequency.

The result is a compact list of reports that demonstrably serve a purpose, separate from the reports that were once built but have since become redundant or exist twice under a slightly different name. That inventory is the foundation for the rest of the project: the sharper the scope, the less we have to reconstruct and the smaller the risk that something is overlooked later on.

Usage analysisStakeholder interviewsReport auditScopingRemoving duplicates
Step 02

Rebuilding the underlying queries and data sources

Extracting the knowledge from the .rpt format

A Crystal Reports file is not a standalone report on a clean data source; it often contains the queries, formulas, groupings and calculations that determine what ends up in the report. That logic is hidden in a file format that can only be opened with the Crystal Reports designer, making it effectively invisible to everyone except whoever originally built the report. We reconstruct that logic as readable, documented queries or views on the underlying database, independent of the .rpt file.

Each rebuilt query is placed alongside the old report output and compared, row by row, until the results match. Where the report contained outdated or illogical filters, we put this to the user explicitly rather than silently carrying it over or dropping it. That way you don't end up with a copy of the old problem in a new guise, but with data logic that anyone on your technical team can read and adapt.

Query extractionData source integrationValidation against old outputDocumentationViews/data model
Step 03

Replacing with a modern reporting or BI layer

Built-in dashboard or BI tool, decided per report

Once the logic has been rebuilt, we choose the format that suits each report best. Reports that sit close to a single workflow, such as an invoice overview within the application where the invoice is created, we embed as a dashboard directly in the application itself. Reports that are used by several departments and need to be filtered, combined or sliced are a better fit for a BI tool with a direct connection to the data source, so users can filter for themselves without asking a developer.

Both routes put an end to the Crystal Reports habit of thinking in one-to-one PDF reports. Instead of a static file that you have to open and export, you get an environment that moves with the live data and in which several people can build their own insights. We always lay the choice between the two routes out for you, with the pros and cons made concrete for each report.

Embedded dashboardsBI tool with live connectionSelf-service reportingRole-based accessNo more .rpt files

What you have at the end.

Reporting that is no longer tied to a single file format and a single person, but is readable, documented and maintainable by several people.

Reports in production

As a built-in dashboard, as a BI environment, or a combination of both.

Documented queries

Readable views and data model, no longer hidden in an .rpt file.

Report overview

Which reports have been kept, merged or phased out, and why.

Self-service for users

Where possible, users can filter and drill down themselves, without a developer.

Management (optional)

Ongoing development of reports and dashboards under a maintenance contract.

When replacing Crystal Reports becomes unavoidable.

Four patterns in which postponing is no longer sensible, and in which we are usually invited to an assessment meeting first, before anything concrete is planned.

Runtime

The runtime or licence is a constraint

Older Crystal Reports runtimes have not all kept pace with newer platforms, and some ran for a long time only as a 32-bit component. Newer versions fall under the licensing model of SAP, the current owner of the product, which comes with different terms than the version you originally started with. As soon as a platform upgrade or server migration is on the horizon, the reporting layer suddenly becomes the bottleneck.

Knowledge

The only administrator has left or is leaving

The .rpt files were once built by a single developer or power user who still knows the Crystal Reports designer. That person is retiring, changing roles or has already left, and nobody else dares to modify the reports without first spending days working out what exactly is in them.

Embedding

The reports need to move to the web

The underlying application is being replaced by a web application, but Crystal Reports was designed for a desktop environment and is difficult to embed in a modern web stack. As soon as the application itself is modernised, as with a Delphi modernisation or the replacement of a Cobol system, the reporting layer has to follow, and that is the moment to move to a modern form straight away.

Forecast

Users want to filter for themselves

Management and operational departments have become used to dashboards elsewhere in which they can drill down, filter and compare for themselves. A static PDF report that they have to request from the IT department then feels like a step backwards, even if the underlying figures are correct.

Risks we address explicitly.

Reporting touches the figures your organisation steers by. Four risk categories that are named up front in every Crystal Reports project.

Report loss

A report gets overlooked

When an old reporting layer is switched off, there is a risk that a report that is only run a few times a year gets overlooked. That is why we do not base our inventory solely on daily usage, but explicitly check with finance, legal and operational departments whether there are periodic reports that do not show up in the day-to-day picture.

Figures

Deviating results after rebuilding queries

When the logic is reconstructed from an .rpt file, a small deviation in a filter or rounding can lead to a different figure. We validate every rebuilt query report by report against the old output, and present every deviation to you explicitly before the old report is switched off.

Adoption

Resistance to letting go of familiar PDFs

Users who have worked with a fixed report for years tend to find a dashboard unfamiliar at first, even when it offers more. We involve the key users from the inventory phase onwards and, where possible, keep the layout of a new dashboard recognisable from the old report.

Transition

Reliance on a single key person during the transition

If the only administrator of the old reports is still around, we schedule that knowledge transfer as a fixed part of the project, with documentation as the outcome rather than knowledge that stays in one person's head again.

How a Crystal Reports project works.

01Introduction→ 02Inventory→ 03Queries & build→ 04Rollout & safeguarding
Step 01

Introduction

Which reports exist, who uses them, and where the pain is: the runtime, the licence or the knowledge. A no-obligation conversation with IT and the main report users.

Step 02

Inventory & scope

We map actual usage per report, speak to the user groups and decide which reports are kept, merged or dropped.

Step 03

Rebuilding queries & build

The logic in the .rpt files is reconstructed as readable queries, validated against the old output, and built into dashboards or a BI integration.

Step 04

Rollout & safeguarding

Reports are rolled out in phases alongside the old version, users are trained, and the old Crystal Reports layer is only switched off once the new reports have been confirmed.

From Crystal Reports to a modern reporting stack.

In practice, Crystal Reports appears in many different environments. Besides this page, our pages on modernising Delphi applications and replacing Cobol systems may also be relevant when the reporting layer is part of a broader modernisation, as is our wider approach to replacing legacy software.

Where we start from
Crystal Reports (.rpt)SAP Crystal Reports SDKDelphiFoxProVB6Older .NET WebForms
Target stack, reporting & BI
Built-in dashboardsPower BIReact / Next.jsPostgreSQLSQL Server views
Migration & integration
Query extractionData validationDirect data source integrationAPI layerRole-based access

Frequently asked questions.

Why can't we simply keep the existing .rpt files running?
You can, as long as the runtime is still supported and you still have the knowledge to modify the reports. The problem is that both usually disappear at the same time: not all older Crystal Reports runtimes have been developed further for the latest platforms, and licences for more recent versions fall under SAP, the product's current owner. Once the runtime or licence becomes a showstopper, or the only colleague who understands the .rpt files leaves, postponing is no longer an option. We therefore advise not waiting for that moment, but replacing the reporting layer in a controlled way while there is still time to do it carefully.
What happens to reports that nobody really uses any more?
We let them lapse, and that happens more often than organisations expect beforehand. Almost every reports folder contains .rpt files that were once built for a specific project or a one-off question and were never changed or opened again. We take stock of actual usage per report, not assumed usage, and only rebuild what demonstrably still serves a purpose. That not only saves build time, it also prevents the new environment from accumulating as much ballast as the old one.
Can we switch over without losing figures or introducing errors?
Yes, provided the underlying queries are carefully rebuilt and validated. Crystal Reports files often contain query logic, formulas and groupings that live only in the .rpt file itself, not in the database. We reconstruct that logic as readable, documented queries or views, and compare the results report by report against the old output until the figures match. Only then do we replace the old report for good.
Does everything have to move to a BI tool, or can it be done within the application itself?
Both routes are possible and we choose case by case. Reports used mainly by one department and sitting close to an existing process are often embedded as a dashboard in the application itself, right next to the workflow the figures come from. Reports that several departments slice, filter or combine are a better fit for a BI tool such as Power BI with a direct connection to the data source, so users can drill down themselves without needing a developer.
What if the only person who managed the reports has already left?
That is a common reason for calling us in, not a blocker. We open the existing .rpt files, reconstruct the queries and formulas built into them, and check the results with the colleagues who read the reports every day, even if they have no technical background. That way we recover the knowledge from the file format and capture it in documentation and readable queries, rather than leaving it in a single .rpt file that only one person can open.
Does this also work if Crystal Reports runs on a Delphi or FoxPro application?
Yes, in fact that is the situation we come across most often. Crystal Reports is frequently added as a separate reporting layer to a Delphi, FoxPro or older .NET/VB6 system, with the reporting engine embedded through a standalone SDK. We can replace the reporting layer while the underlying application keeps running, or combine it with a broader project if the application itself is also due for replacement. See also our pages on modernising Delphi applications and replacing COBOL systems for that broader approach.
What determines how long a project like this takes?
The number of reports that genuinely need to be kept after the inventory, the complexity of the underlying queries and formulas, the number of data sources involved, and the choice between built-in dashboards and a BI tool. A small set of straightforward reports with a single data source is a very different project from dozens of reports that combine multiple systems. We give an honest estimate after the inventory phase, not before, because any figure given without a clear view of the actual scope is a guess.
Do we remain the owner of the new reporting environment and the underlying data?
Yes, completely. The documented queries, the data model, the dashboards or the BI integration are all put in your name, in your own environment or database. You are not tied to a specific reporting vendor, and the knowledge that used to live only in .rpt files is captured in readable documentation that several people in your organisation can understand.

Talk to us about your Crystal Reports reports.

A no-obligation introductory call of half an hour. We will listen to which reports are running, where the pain points are, and whether replacement is the right route right now, even if it turns out that your current reporting layer is still good enough for the time being.

Edit content