Notes from the migration floor.
Practical thinking on BI migrations, rationalization and proving the numbers still match.
The parity report should outlive the migration
A parity test compares the new BI platform to the old one, then the old one is switched off. Freeze the signed-off numbers and keep testing them.
Read it
Magic ETL never told you which duplicate it kept
Magic ETL's Remove Duplicates, Rank & Window and Group By first/last all pick one row. Domo's docs don't say how ties resolve. A SQL rebuild has to, and a parity check can pass by luck.
Read it
Choose a Power BI storage mode before you migrate
Import, DirectQuery or Direct Lake decides where data prep lives, how row-level security behaves and what you license. Settle it before a BI migration.
Read it
Qlik's {1} ignores selections, not the axis
Qlik set analysis to DAX looks like a one-to-one swap until a set sits under a chart axis. Here is where {1} and a plain modifier change meaning, and how to test it.
Read it
Your Domo renewal needs an exit price
Progress has bought Domo and has not said what changes for customers. Before your renewal, find out what leaving would cost. Here is how to get that number.
Read it
Looker to Power BI: what symmetric aggregates did
Looker detects fan-out joins and corrects the sum. Power BI doesn't, so a LookML migration has to rebuild that protection in the model. Here is where it goes.
Read it
Why counting dashboards gives you the wrong migration estimate
A dashboard count mostly measures how often the same logic was copied. Estimate migration effort from calculations, security and sources instead.
Read it
Tableau table calculations live in the view. DAX measures live in the model.
A Tableau table calculation takes its meaning from the sheet it sits on. Moving it to DAX means choosing the partition and order the view gave you free.
Read it
How to test an automated Domo to Power BI migration before you buy one
Any vendor can convert a simple chart. A proof of concept should hit Beast Modes, Magic ETL, row-level security and reconciliation. Use this checklist.
Read it
Where metric definitions should live
Most BI estates define the same metric many times, once per card. A migration is the cheapest moment to decide where definitions live, and to stop copying them.
Read it
Beast Mode FIXED to DAX: where it bites
Domo FIXED functions look like they map straight onto DAX CALCULATE. Here is where the translation changes the number, and how to catch it before cutover.
Read it
Proving parity after a BI migration
A migrated dashboard that looks right isn't finished. Here's how automated parity tests show the numbers really match before anyone cuts over.
Read it
Retire before you migrate
The cheapest dashboard to migrate is the one nobody opens. How to use evidence to shrink an estate before it moves.
Read it
Nobody should migrate twice
Hand-rebuilt migrations lock your analysis into the next platform just as tightly as the last. Open specifications break that cycle.
Read it
Prefer a feed reader? Subscribe via RSS.
Show us your estate.
A read-only metadata export is enough to start. No platform access required, mutual NDA as standard.