Business Intelligence Migration Services: Legacy Reports Rebuilt in Power BI and Fabric
The report server is due for replacement, the person who wrote the Crystal reports left years ago, or the old platform's renewal just went up. Hundreds of reports exist, and nobody is sure which ones still matter.
Business intelligence migration services move the reporting you rely on from an older platform, such as SQL Server Reporting Services, Crystal Reports, Cognos, BusinessObjects or an Access and Excel setup, into Power BI and Microsoft Fabric. The work is less about copying reports than deciding which deserve to survive, rebuilding those properly and proving the numbers match.
Edward Pinela, MBA, runs each migration himself, remotely and inside your Microsoft tenant. If you are still weighing whether to move at all, the guide to cloud BI migration benefits covers the case for and against. This page is the service itself: what gets done, tool by tool.
Every migration is quoted at a fixed price once the inventory is done. To begin, ask for a free 30-minute strategy call through the form or by phone.
What happens in a BI migration engagement?
Five pieces of work: an inventory of every report and who opens it, a rationalization that retires the unused and merges near-duplicates, a rebuild of what remains on shared semantic models, a validation that reconciles old and new figures, and a retirement plan that switches the old platform off only once users have moved.
Rationalization is where the savings are. Report servers accumulate copies: the same sales report saved once per region, or a version someone kept before changing a column. Microsoft's SSRS guidance recommends finding and retiring unused reports as part of the move. A single report with a region slicer can take the place of a whole folder.
Which legacy BI tools can move to Power BI?
Most of them, by different routes. SSRS reports move almost as they are, because Power BI paginated reports use the same report definition format. Crystal Reports, Cognos and BusinessObjects content is rebuilt rather than converted: queries, formulas and layouts are documented, then recreated. Access and Excel reporting usually becomes a proper model with a scheduled refresh.
The table sets out each source and its usual destination. Several platforms have their own pages: Tableau to Power BI, Qlik to Power BI, Looker to Power BI, Zoho Analytics to Power BI, Excel to Power BI and Power BI Premium to Fabric.
| Source tool | Usual destination | How it moves | What to watch |
|---|---|---|---|
| SQL Server Reporting Services (SSRS) | Power BI paginated reports | Published from Report Builder, or with Microsoft's RDL Migration Tool for older versions | Shared data sources become embedded; custom code DLLs are not supported |
| Power BI Report Server | Power BI service | The same .rdl and .pbix files published to workspaces | Folder permissions re-created as workspace roles and apps |
| Crystal Reports | Paginated reports for fixed layouts; Power BI reports for analysis | Rebuilt from documented queries, formulas and layouts | Logic hidden in report formulas and subreports |
| IBM Cognos or SAP BusinessObjects | Power BI semantic models and reports | The business layer (packages or universes) rebuilt as a semantic model | Calculations defined in the metadata layer rather than the reports |
| Access databases and Excel workbooks | A Power BI semantic model, sometimes a Fabric lakehouse or warehouse | Tables and queries re-created in Power Query or Fabric | Manual steps and copy-paste that nobody wrote down |
| Power BI Premium capacity | Microsoft Fabric capacity | Workspaces reassigned to the new capacity | Covered on the Premium to Fabric migration page |
Can pixel-perfect SSRS and Crystal output survive?
Yes, through paginated reports. Microsoft describes them as designed for printing or sharing, with exact control of page layout and every row of a table printed across as many pages as it needs. Invoices, statements, regulatory forms and long operational lists belong there, not in an interactive dashboard.
Paginated reports are authored in the free Power BI Report Builder, and publishing them to a shared workspace needs a Pro or Premium Per User license, as with any Power BI report, according to Microsoft Learn. Reports built for SSRS 2016 or later are compatible with the service. A few features do not carry over, including SSRS-style shared data sources and data-driven subscriptions; Power BI offers dynamic per-recipient subscriptions instead.
For SSRS in particular, Microsoft's plan for migrating .rdl reports covers versions 2012 through 2022 and notes that the existing report server can stay in place until you are ready to retire it.
How do you prove the new reports are right?
By running old and new side by side on the same period and comparing the figures that matter: totals, counts and a sample of detail rows for each rebuilt report. Differences are explained in writing, either a bug fixed in the rebuild or a flaw in the old report, before anyone is asked to switch.
Old reports are sometimes wrong. A Crystal formula that silently excluded a status, or a Cognos filter nobody remembers adding, shows up as a mismatch; those findings are logged so finance can decide which figure is correct. Small details change too: Microsoft notes that the UserID field returns the user principal name in the Power BI service, and ExecutionTime returns UTC.
What does a migration cost, and what is guaranteed?
The price is fixed after the inventory, because the cost depends on how many reports survive rationalization and how complex they are, not on how many exist today. Microsoft's licenses are separate: Power BI Pro is listed at $14 per user per month and Premium Per User at $24, both paid yearly, on its pricing page.
Reports discovered later, or small changes after cutover, can use Power BI Flex Support, from $2,500 for 20 hours, with hours that never expire. Because the destination is Power BI, the Power BI guarantee covers the engagement: dislike working with us at any point in the first 4 hours, and what you paid comes back to you. That promise is about the working relationship; the reconciliation is what proves the figures.
Edward has 20+ years of experience and 200+ projects behind him, and Lightray carries a 4.9 rating on Google alongside an A+ from the BBB.
Further reading: Microsoft Learn: Plan to migrate .rdl reports to Power BI.
Ready to retire the old report server?
Book a free 30-minute call with Edward Pinela, MBA. You get an honest read on what to fix first — and if we are not the right fit, you will hear that on the call.
Frequently asked questions
Do we have to move everything at once?
No. Reports move in waves, usually by department or by source system, and the old platform keeps running until the last wave is reconciled. Microsoft's SSRS guidance makes the same point: nothing has to be removed until you are ready.
How long does a migration take?
The inventory sets the timeline, and the quote states it. A few dozen surviving reports on one data source is a very different job from several hundred spread across systems, so no honest estimate comes before the inventory.
Can you migrate us to Tableau or Looker instead?
No. Lightray builds in Power BI and Microsoft Fabric only. If discovery suggests another platform would suit you better, you will be told, but that build would need a different provider.
What do you need from us?
Read or admin access to the old platform so reports and their usage can be listed, access to the underlying databases, a Power BI workspace in your tenant, and an owner per department who can confirm which reports they still use.
Is the migration done remotely?
Yes, entirely. Edward works over video and screen share inside your tenant and, where data stays on your network, through an on-premises data gateway that your IT team installs or approves.
You Won’t Get Handed Off to Junior Staff.
At most consulting firms, the senior person who sold you shows up for the kickoff — then you get handed to a team of juniors learning on your dime. That’s not how we work.
When you hire Lightray Solutions, you work directly with Edward Pinela, MBA — a principal consultant with 20+ years of experience across Power BI, web development, SEO, and CRM systems. Edward architects every engagement personally, stays involved through delivery, and answers his own phone.
Read Edward’s Full Bio“Mid-market companies deserve senior-level expertise without paying enterprise-agency prices. That’s the gap Lightray fills.”
Simple. Transparent. Proven.
No black-box processes. No endless discovery phases. A straightforward three-step approach designed to deliver measurable results fast.
Discovery Call
Free 30-minute strategy session where we assess your data landscape, website, marketing — and where AI would genuinely pay off versus where it's hype.
Free · No ObligationCustom Roadmap
You receive a tailored plan with clear deliverables, realistic timelines, and expected ROI. You approve every detail before we start.
Fixed Scope · Clear PricingMeasurable Results
We execute, measure, and optimize. You get dashboards, regular check-ins, and full visibility — so you always know the impact.
Data-Driven · TransparentGet a clear plan in one free call.
Tell us what you are trying to fix. Your request goes to Edward Pinela, MBA — the principal consultant who would do the work — and you hear back within 4 business hours.
Prefer to call? +1 (714) 872-9606