⚠️ OasisPro · Crystal Reports Estate Audit · IFS Cloud 26R2
You can't budget for what
you haven't counted.
Here's the uncomfortable part: most US IFS Cloud teams are already pricing their 26R2 migration, and almost none of them actually know how many Crystal Reports they're running. Not roughly. Not "somewhere around a hundred." Actually know. That gap is exactly where budgets blow up, timelines slip, and someone ends up explaining a surprise invoice to finance three months into the project.
A Crystal Reports estate audit closes that gap in a day or two. It's the single cheapest hour you'll spend on the entire 26R2 program, and it's the one step teams keep skipping because it feels like a delay instead of what it actually is: the thing that stops you from over-costing everything downstream.
Here's the 6-step audit, done properly, so the number you bring to your CFO is one you can actually defend.
Every team we've audited assumed their estate was bigger, messier, and more expensive to migrate than it actually was. The registry lies upward. Run history is what tells the truth.
You are not looking at a wall of reports that all need rebuilding. You're looking at a small, high-value core buried inside a much larger pile of dead weight nobody's touched in years. Find that shape first, and the rest of the 26R2 decision gets dramatically cheaper and dramatically easier.
The 6-step Crystal Reports estate audit
- 1. Pull the actual registry. Not the list your report writer keeps in a spreadsheet, and not what department heads say they use. The IFS Cloud report registry, in full, including everything nobody remembers building.
- 2. Cross-check against real run history. A report sitting in the registry and a report someone actually opens are two different things. Frequency and last-run date are what separate them.
- 3. Set one dormancy rule, and apply it without exceptions. Twelve months with no runs is a solid default. Pick a rule, apply it to everyone equally, and stop letting "but what if someone needs it" derail the count.
- 4. Triage what survives by complexity. This is the step teams skip and regret. A hundred simple extracts cost less to migrate than twenty heavily customized customer-facing documents. Count matters less than complexity.
- 5. Force a named sign-off on every retirement. "Nobody's touched it in two years" is evidence, not permission. Get a real person's name against every report you plan to kill.
- 6. Walk away with one number. Total registered. Retiring. Surviving. Complexity split within survivors. That's the number that goes to finance, and the number every partner conversation gets measured against.
What the registry gives you
Every report IFS Cloud has ever logged, including ones built for a customer who left five years ago. This is always the biggest, scariest number, and it's almost never the real one.
What run history strips out
A report that hasn't run in eighteen months isn't "in use," no matter what the registry says. Run history is what turns a scary list into an honest one.
What complexity triage adds last
Among what survives, complexity is the real cost driver, not headcount. This is the step most rushed audits skip, and it's the one that determines your actual invoice.
The mistake that inflates every single estimate
Teams that skip the audit cost the full registered count as if every report is both active and complex. It never is. Run the audit properly and the real number is almost always smaller, cheaper, and faster to migrate than the number you were about to take to finance.
What to do with the number once you have it
Running the audit is half the job. Using it correctly is the other half, and it's where a lot of teams still leave money on the table.
Feed the surviving count and complexity split straight into a rebuild cost estimate, so the number you bring to a decision-maker is built on evidence instead of a registry figure nobody actually checked.
Compare that estimate against preserving the estate, using the exact same numbers, so both routes get judged fairly instead of one being guessed and the other being measured.
Refresh the audit before every major decision point, not just once at kickoff. Estates change, and a number from eighteen months ago is not the number you have today.
Every week you delay this audit is a week you're planning your 26R2 budget against a number nobody actually checked. That's not caution. That's risk.
What a Crystal Reports estate audit almost always turns up
A concentration of registered reports around two or three business functions, usually finance and shipping, with a long tail of one-off reports built for projects that ended years ago.
A small core of genuinely complex, business-critical reports, often under twenty even in a large estate, that carries most of the real risk if you choose Report Studio.
And at least a handful of reports nobody currently on the team can explain, built by someone who's long gone, surfacing for the first time in years because someone finally counted.
We'll run this audit for you. Fast.
OasisPro pulls your registry, cross-checks run history, triages by complexity, and hands back one reconciled number your team can act on, typically within days. No commitment to rebuild or preserve required before you see the figures.
See all five IFS Cloud reporting routes comparedGet a number you can defend to your CFO before you spend another dollar.
Give us access to your report registry and run history, or let us pull it directly. We hand back your true report count, dormant share, and complexity split, ready to plug straight into a rebuild-versus-preserve decision.
How many Crystal Reports does a typical US IFS Cloud customer actually have?
Anywhere from a few dozen to several hundred, depending on company size and how long the estate has been running. The registry number is almost always higher than what any single team believes, because reports get built by contractors, consultants and employees who left years ago without documenting anything.
What actually happens if we skip the audit before 26R2?
You cost a Report Studio rebuild against the full registered count instead of the real active count, which inflates the number you take to finance, or you find out reports are broken in production after go-live, during month-end close, when there is no time left to fix them properly.
How fast can a Crystal Reports estate audit actually be done?
For a mid-sized estate, one to two focused days: pull the registry, check run history, triage by complexity. Most delays come from waiting on system access and internal coordination, not from the audit work itself.
Do we need to pick rebuild or preservation before we audit?
No. That decision comes after the audit, not before it. The audit produces the count, the dormant share and the complexity split that turn rebuild-versus-preserve into a real comparison instead of a guess dressed up as a plan.
A day of counting beats a year of guessing
This is genuinely one of the cheapest hours you'll spend on the whole 26R2 program, and it's what makes every later decision, Report Studio requirements included, actually affordable.
Every rebuild or preservation estimate is only as good as the number behind it, and that number comes from the audit, not from the registry alone.
Count properly. Triage by complexity. Get a named owner to sign off what gets retired.
None of that is complicated. It just has to actually happen, and it has to happen before you spend a dollar costing anything else.