A Crystal Reports to Power BI migration that survives contact with your subreports

Which parts of a .rpt file really move?

Crystal is a banded report writer: you design against sections, and each report carries its own connection, query, and calculations. Power BI splits that into two layers — a semantic model holding the data and the measures, and reports that visualise it. A migration is therefore a rebuild with a known map, not a file conversion, and the map is what keeps it predictable.

The consequence worth understanding up front is that logic stops living inside individual reports. In Crystal, two reports can filter the same table differently and both look authoritative. In Power BI that definition is settled once in the model. Expect that conversation early; it is the most valuable and most political part of the project, and the reason we classify before we build.

How do Crystal Reports elements map to Power BI?

This is the working map we build the plan from. It is deliberately dull, because the point of a migration is that nothing surprising turns up in week three.

Because record selection formulas and stored procedures often carry the real business rules, that unpacking is a task in its own right. Transformation logic that belongs upstream goes into Power Query (opens in new tab); aggregation logic becomes measures on a star-schema model, which is the data modeling and DAX half of the job. Microsoft's own Power BI migration guidance (opens in new tab) follows the same sequence: assess and prioritise the estate before you rebuild any of it.

What happens to pixel-perfect print output?

This is the objection that stops most Crystal migrations, and it is a fair one. A standard Power BI report is built for interaction on a screen: a table you scroll prints only the rows that were visible. An invoice, a statement, or an audit pack has to print every row, break pages in the right places, and repeat headers and footers exactly.

That work belongs in a paginated report (opens in new tab), authored in Power BI Report Builder, which gives exact page-layout control and prints all the data in a table across as many pages as it takes. Microsoft documents export to PDF, Excel, Word, CSV, and other formats, plus email subscriptions that attach the rendered output — the closest equivalent to the scheduled Crystal export most teams are replacing. Confirm your workspace and capacity plan against Microsoft's current licensing documentation before committing to a design.

In practice an estate splits cleanly: anything a person explores becomes an interactive report on the shared model, and anything a person prints, files, or sends to a customer stays fixed-layout. We make that call during classification and record the reason, so it is auditable later.

What does the migration cost?

Work runs on prepaid Flex hours that never expire: Starter 20 hours ($2,500), Growth 40 hours ($4,600), or Power 80 hours ($8,000), with hourly work from $100/hour. Inventory and classification of a typical mid-market estate fits inside a Starter block, and it is the task we recommend buying first, because it converts an unknown number of report files into a scoped list with hours against each line.

After that, cost tracks how many reports survive classification and how much logic they carry. A parameter-driven listing with two totals is a very different job from a six-subreport statement pack with nested selection formulas. You get an estimate in hours per report, approve only what you want built, and unused hours stay banked. See Flex pricing.

How long does each report take?

Individual reports typically ship within 3–5 business days of approval, and a phased migration is a sequence of those tasks rather than one project ending in a big-bang cutover. Larger estates get a clear timeline and order once the inventory is done: highest-value and highest-risk first, the long tail last.

Running Crystal alongside Power BI for one full reporting cycle is worth the overlap. Users compare both outputs on live data, and the old designer is switched off only once the replacements have been through a real month-end.

Who this is for

Finance, operations, and IT teams carrying a Crystal estate they can no longer maintain comfortably: an ERP that ships .rpt files, a designer nobody has upgraded, reports hitting production directly, or a knowledge gap left by whoever wrote the formulas. It is a poor fit for anyone wanting a like-for-like copy with no decisions made — that buys a more expensive version of the problem you already have.