Migration and modernization at scale

One license for every person who looks at a report

By Xavier Franco, CEO de Elternativa · Grupo Zemsania
· 7 min read

Written with the help of AI and reviewed by Xavier Franco

The stalls of an old theatre with every seat reserved and only four people watching the stage.
In this article

Any technology director has three mandates today: produce more, depend less and spend less. And when you scratch a little at the spending, the same item always shows up: the BI dashboard that half the company consults and that is paid for per head, every year.

The sum nobody does out loud

Most BI tools are licensed per user. I take the most widespread one as an example: according to Microsoft’s official page, Power BI Pro costs €12.10 per user per month and Power BI Premium per user, €20.80, billed annually and excluding VAT. To view a shared report, each person needs one of those licenses, unless the content sits in a large dedicated capacity (F64 or higher).

Do the sum with your own numbers. With 300 people who consult reports on a Pro license, that is €43,560 a year. And that figure never goes down: it grows with every new person who wants to see “their” indicator.

I am not saying it is wrong to pay it. I am saying you need to know why you pay it. Because when we run an inventory in an organization, what we usually find is:

  • many users who only look, never edit or build anything;
  • reports that nobody has opened for months, but that keep loading every night;
  • two or three BI tools living side by side, each with its own contract, its own renewal and its own team.

In practice: ask IT for the number of BI licenses you have and, next to it, how many of those people have created or modified a report in the last year. The gap between the two figures is your first conversation.

Why it was paid for without argument until now

The semantic model of BI tools was a great idea: it let you build indicators without a data engineer at your side. That had a price, the license, and we paid it gladly, because the alternative, developing custom dashboards, was expensive, slow and hard to maintain.

That has changed. Today, with orchestrated AI, the data engineer comes built into the work: building and maintaining your own dashboard no longer takes a huge team. And when building stops being unfeasible, you can choose again.

I say this carefully, because it is not against anyone. It is not all or nothing, and never against the vendors. There are BI tools that add a great deal of value and will remain the best option in many cases. What changes is that they will now have to prove that distinctive value at every renewal, rather than win it by inertia.

In practice: split your users into two groups. Those who build and explore, who probably need the tool. Those who consult a closed dashboard, who perhaps do not.

Three possible destinations, and you decide

When we plan to migrate a BI dashboard, there is no single answer. There are three paths, and each makes sense in a different case:

  1. Another BI tool. If the one you have falls short or gets more expensive, you can move to Power BI, Tableau or Qlik Sense. You still pay a license, but you choose which one.
  2. The data platform. You take the metrics to Databricks, Snowflake or Microsoft Fabric, so they are calculated the same way wherever they are read from. The logic stops living trapped inside a tool.
  3. A custom dashboard, with no per-user license. For those who only consult, your own dashboard, built on your data, whose price does not grow with every person who joins.

The usual answer is a combination: the tool for those who analyze and your own dashboard for those who only look.

In practice: do not start with the destination tool. Start with the reports: which ones are used, who uses them and what for.

Migrating without losing a single figure

This is the real fear, and I understand it. A dashboard is the figure management looks at on Monday morning. If one decimal changes, trust in the whole project is lost.

That is why how you migrate matters more than where you migrate to. This is how we do it:

  • Read-only inventory. Reports, models and metrics are scanned without touching anything.
  • What stays, what goes and what is switched off. What nobody opens is not migrated: it is switched off. It is the cheapest way to save.
  • Rebuild validated by your team. The AI builds; your team reviews and decides.
  • Cutover with a number-by-number comparison. The new dashboard and the old one coexist until all the figures match. Only then is the previous tool retired, report by report.

The data and the indicators stay: they are the reference against which everything new is compared.

In practice: before approving any BI migration, ask how it will be proven that the figures are the same. If the answer is “we will review it at the end”, it is not a plan.

You don’t pay the same for those who build as for those who look

Vendors know this, which is why almost all of them have different licenses depending on what each person does. Tableau makes it very clear on its website: on Tableau Cloud, Standard edition, the Creator license costs $75 per user per month, Explorer $42 and Viewer $15, billed annually. Even those who only look pay, every month.

And the license is not the only cost. Behind a dashboard there are more things you pay for without seeing them:

  • the servers or capacity where the reports run;
  • duplicated models, when the same metric is calculated differently in two tools and nobody knows which one is right;
  • the people who maintain each tool, with their training and their learning curve;
  • the renewals, which arrive every year with their negotiation.

When you have two or three BI tools at once, all of that multiplies. That is why, for me, the conversation does not start with “which tool is cheaper”, but with “what does each person really need to do their job”.

In practice: draw a table with three columns (builds, explores and only looks) and put every BI user in one. That table is worth more than any price comparison.

Where to start

My advice is to start with what weighs the most and carries the least risk:

  1. Pull the inventory of BI tools, licenses and renewal dates.
  2. Cross licenses with real usage: who builds, who only looks and which reports nobody opens.
  3. Switch off what is not used. It is an immediate saving and requires no migration.
  4. Choose a dashboard that is widely consulted and has few editors as a pilot.
  5. Migrate with measured parity and compare cost, timeline and quality before deciding the next step.

Your next renewal is your deadline. If you start now, you will reach it with data and not with an invoice.

How we help you

In BI dashboard migration and modernization we migrate reports, dashboards, models and programs from QlikView, BusinessObjects, Cognos, Tableau, SAS, MicroStrategy or Power BI to the destination you choose: another tool, your data platform or a custom dashboard, with no per-user license. Read-only inventory, rebuild validated by your team and cutover with a number-by-number comparison.

We do it with the Datagentis migration module, which scans your systems read-only, detects what is not used and what has license impact, and generates the documentation and the work plan before anything is moved.

Frequently asked questions

What is a BI dashboard?

It is a panel that brings together the key indicators of an area or of the whole company so they can be followed at a glance. It can be built with a BI tool or custom-made on your data.

How much does Power BI cost per user?

According to Microsoft’s official page, Power BI Pro costs €12.10 per user per month and Premium per user €20.80, billed annually and excluding VAT. Check it before deciding, because prices change.

Can you have a BI dashboard without a per-user license?

Yes. A custom dashboard built on your data platform is not licensed per person. It makes the most sense for those who only consult.

How do I make sure the figures don’t change when migrating?

By running the new dashboard and the old one in parallel and comparing them number by number. The previous tool is retired when everything matches.

Keep reading