📋 OasisPro · Crystal Reports Estate Audit · IFS Cloud 26R2
Before you cost anything.
6 essential steps to get right.
Crystal Reports estate audit is the step almost every organisation facing IFS Cloud 26R2 skips, and it is the one every later decision actually depends on. Before you can cost a rebuild, size a preservation route, or even have a sensible conversation with a partner, you need a number you trust: how many reports genuinely exist, how many are actually used, and how complex the ones that matter really are.
Most businesses estimate this instead of measuring it, and the estimate is usually wrong in a specific, predictable direction.
Here are the 6 steps that turn a guess into a number worth planning around.
Every organisation we have audited found more reports than they expected, and fewer of them in active use than they assumed. Both surprises point the same way: the estate is smaller and more manageable than it first appears, once you actually look.
The instinct is to imagine the estate as a wall of complexity. The reality, once counted properly, is usually a smaller core of genuinely used reports surrounded by a much larger dormant tail that costs nothing to retire. Finding that shape is the entire value of the audit, and it is why skipping it leads straight to over-costing the problem.
The 6 steps of a Crystal Reports estate audit
- 1. Pull the registry, not the department lists. IFS Cloud's own report registry captures everything technically registered, including reports nobody in the business currently remembers. Asking teams what they use will always undercount.
- 2. Cross-reference against real run history. A registered report and an actively used report are different things. Run frequency and last-run date turn a registry entry into an evidence-based judgement about whether it matters.
- 3. Set a dormancy threshold and apply it consistently. Twelve months not run is a reasonable default. Whatever threshold you choose, apply it the same way across the whole estate rather than making exceptions case by case.
- 4. Triage the survivors by complexity. Simple tabular extracts and multi-level layouts with subreports and embedded formulas are different jobs. This split, more than the raw count, is what drives any later cost estimate.
- 5. Get a named owner to sign off retirements. A report nobody has run in two years still needs someone from the business to confirm it can go. Technical dormancy is evidence, not permission.
- 6. Produce one number everyone works from. Total registered, retiring, surviving, and the complexity split within survivors. That single reconciled figure is what every subsequent conversation, internal or with a partner, should reference.
What the registry gives you
Every report IFS Cloud knows about, including ones built years ago for a project that finished, a customer that left, or a process that changed. This is always the largest and least trustworthy of the numbers on its own.
What run history adds
Frequency and recency turn a flat list into a picture of actual use. A report run daily and one run once at implementation and never again look identical in the registry and completely different in run history.
What triage adds last
Among the reports worth keeping, complexity determines effort far more than count does. A hundred simple extracts can cost less to address than twenty heavily customised customer-facing documents.
The predictable direction most estimates get wrong
Businesses that skip the audit almost always over-estimate the effort, because they picture the full registered count as if every report were both active and complex. A proper audit typically reveals a smaller, more manageable core, which is precisely why skipping the audit tends to make the 26R2 decision look more expensive than it actually is.
Using your Crystal Reports estate audit once it is done
The audit itself is only half the value. What you do with the number afterwards is the other half, and it matters just as much.
Feed the surviving count and complexity split directly into a rebuild cost estimate.
That way the figure you eventually take to a decision maker is built on real evidence rather than a headline registry number nobody has actually checked.
Compare that estimate against what preserving the estate costs on exactly the same numbers, so both routes are being judged fairly on the same underlying evidence rather than on different assumptions.
Keep the audit current. A number from eighteen months ago is a different number today, particularly after any period of process change or system growth.
Repeat the audit before any major decision point, not just once at the start of a 26R2 project, since the estate genuinely changes as processes and customers change around it.
The IFS Community has genuinely practical discussion threads on extracting registry and run history data cleanly, and the IFS documentation site covers the underlying report registry mechanics in more depth.
Our rebuild cost calculator takes exactly the numbers this audit produces and turns them into a cost comparison in about a minute.
The estate always looks larger from the registry than it is in practice. The audit is what closes that gap before you cost anything against the wrong number.
What a Crystal Reports estate audit typically reveals
A concentration of registered reports around two or three business functions, usually finance and despatch, with a long tail of one-off reports built for projects that finished years ago.
A smaller core of genuinely complex, business-critical reports, often under twenty even in a large estate, carrying most of the real rebuild risk if the route chosen is Report Studio.
And almost always, at least a handful of reports nobody in the current team can explain, built by someone who has since left, that the audit surfaces for the first time in years.
We run the Crystal Reports estate audit for you.
OasisPro will pull your registry, cross-reference run history, triage by complexity, and return one reconciled number your team can act on, typically within a few days. No commitment to any particular route required before you see the figures.
See all five IFS Cloud reporting routes comparedGet a number you can actually plan around.
Send us access to your report registry and run history, or let us pull it directly. We will return your true report count, your dormant share, and your complexity split, ready to feed straight into a cost decision.
How do I find out how many Crystal Reports we actually have?
Start with the IFS Cloud report registry rather than asking departments to list what they use, since the registry captures everything technically registered, including reports nobody remembers exist. Cross-reference that list with actual run history to see which entries are genuinely active rather than dormant registrations.
What counts as a dormant Crystal Report?
A report not run in the last twelve months is a reasonable working definition, though some organisations use six months for reports tied to monthly or quarterly cycles. The point is not the exact threshold but having one, applied consistently, so retirement decisions are evidence based rather than guessed.
How long does a proper Crystal Reports estate audit take?
For a mid-sized estate of one to two hundred reports, a day or two of focused work is typical: pulling the registry, cross-referencing run history, and triaging by complexity. Larger or multi-company estates take longer, mainly because run history has to be gathered per company or per site.
Should the audit happen before or after choosing rebuild versus preservation?
Before, always. The audit produces the report count, the retirement share and the complexity split that any rebuild or preservation cost estimate depends on. Costing first and auditing later means costing against a guess, which is exactly the pattern that leads to numbers nobody trusts later.
A Crystal Reports estate audit is a day well spent, not a delay
It is genuinely one of the cheapest hours you will spend on the whole 26R2 programme, and understanding Report Studio requirements early is what makes that hour worthwhile.
Every rebuild or preservation cost estimate is only as good as the numbers behind it, and those numbers come from the audit, not from the registry alone.
Count properly, triage by complexity, and get a named owner to sign off what gets retired.
Nothing about that process is complicated. It just has to actually happen.