Migrating 100 to 120 reports from Power BI and a custom CRM to Apache Superset.
- Industry
- Legal services
- Client
- Law firm, 30+ years
- Duration
- 3 months
- Scope
- 100 to 120 reports
- Role
- Data Analyst
Reporting logic spread across three languages and two platforms.
The firm's reports lived in Power BI and in a CRM its own development team built. Business logic was written in DAX, Power Query (M), and JavaScript. The goal: move everything to Apache Superset on standard SQL.
This video shows the problem. A results and comparison video is coming.
Before and after.
Sequenced by criticality
Power BI first. Then the CRM reports, ordered by how critical and urgent each one was to the business.
Business logic, absorbed from people
Most of the logic lived in people, not in code. It took regular working sessions with every department involved: supervisors, staff, the in-house dev team, and the junior developer who originally built the Power BI reports.
Data marts designed, not transcribed
Translating DAX, M, and JavaScript to SQL was never line by line. Each data mart was designed for accuracy and speed on Superset.
AI-assisted validation, human sign-off
With the client's authorization, Claude connected through MCP sped up validation. Final review was mine: random spot checks against Power BI, especially filter interactivity. Where Superset behaved differently, dashboards were adjusted to match the interaction users expected.