Platform migration
Qlik to Power BI, Power BI to Qlik. We take your dashboards whole to the other platform without losing history and without stopping the operation.
Talk to a specialistA dashboard is not copied. It is rebuilt.
There is no export button from one platform to the other, and anyone promising that is selling screen conversion not migration. The two tools store data differently, calculate differently and control access differently. What gets migrated is the business rule, not the file.
That is why a migration is the whole project again, with one big advantage: the destination is already defined. You do not need to work out which indicators matter or how the board wants to see them the current dashboard already answers that. The work is rebuilding that result on the other side, and checking that the number matches.
How the migration happens
Five steps. The last one decides whether the project is finished or not.
- Inventory of what exists. Which dashboards are live, which people actually open and which became dead weight. Migrating a dashboard nobody uses is pure cost that conversation comes before a single line of code.
- Source remapping. Connections are rebuilt on the target platform: ERP, CRM, database, API or file. Where the source sits on an internal server, we configure the necessary bridge.
- Model rebuild. The data model is rebuilt on the target. Qlik and Power BI resolve relationships and aggregation differently, so what was efficient on one side is not always efficient on the other the model is redesigned for the platform that will receive it.
- Measure translation. Each indicator is rewritten in the target language: set analysis becomes DAX, or the reverse. It is the most delicate step, because the same rule written two ways can produce two numbers and this is where most badly done migrations break.
- Dashboard rebuild and publishing. Visuals are rebuilt with the closest equivalent on the target, role-based access control is reinstated and the refresh is rescheduled.
It is only done when the number matches
The acceptance criterion is not the dashboard looking the same. It is the dashboard answering the same. Every migrated indicator is checked against the value the old dashboard delivers, on the same breakdown and the same period. A divergence found is a divergence investigated and sometimes the error was in the old dashboard, which is also a result.
That is why the source environment is only switched off afterwards, not during. Until the checks close, the operation keeps running on what already works.
What you are left with
- The dashboards working on the target. With the model documented and the origin of every table recorded.
- The metrics dictionary. The rule of each indicator in plain language, plus the equivalent expression on both platforms.
- The verification comparison. Indicator by indicator, the old value and the new one side by side.
- Team training. On the target platform, which is usually the one the team does not yet know.
How we run it
We start with the inventory and an assessment of the source environment that is what tells us whether the migration has one month or six ahead, and it is better to find out before signing. Then we present the scope with the list of what migrates, what is retired and what changes shape. Execution happens in blocks: one set of dashboards at a time, each checked and signed off before the next begins.
How we measure results
Success indicators are agreed at the start. In a migration the most frequent are the percentage of indicators checked and matching, the refresh time on the target compared with the source, and the licensing cost after the switch which is usually one of the reasons for migrating.
We now have a far more robust, fast and visual view of each management area’s results.
Sales director national fuel distributor
About this service
Will we lose the history of the old dashboards?
No. History lives in the data sources, not in the dashboard and the sources stay the same. What changes is the tool reading them. When history only exists inside the old environment, that shows up in the inventory and we handle it before any switch-off.
Does the operation stop during the migration?
No. The source environment stays live while the new one is built and checked. Switching off only comes up after the numbers match and that decision is yours, not ours.
Can we migrate only part of it?
You can, and it is usually the more sensible route. The inventory almost always reveals dashboards nobody has opened in months. Migrating what is dead is cost without return: the list of what migrates, what is retired and what changes shape is agreed with you before we start.
How long does it take?
It depends on how many dashboards are included and how documented the source environment is. An undocumented environment is the factor that weighs most on the timeline, because the rule behind each indicator has to be reconstructed before it can be translated. The initial assessment exists precisely to answer that with a number rather than a guess.
Why migrate at all?
The reasons we see most are licensing cost, an old environment nobody can maintain any more, and standardising with the rest of the company. If your case is none of those, the conversation is worth having first: sometimes the problem is a badly built model, and changing platform takes the problem along with it.
Let’s look at your numbers together
A 30-minute conversation is usually enough to find where money is sitting idle in your operation.
We understand processes before recommending technology. Automation, data, artificial intelligence, and custom software for companies seeking efficiency, control, and scale.