QlikView end of support and BusinessObjects: what really ends, and when
By Xavier Franco, CEO de Elternativa · Grupo Zemsania
· 6 min read
Written with the help of AI and reviewed by Xavier Franco

In this article
I confess: I have said it myself. “QlikView and BusinessObjects end in 2027.” It is a phrase that circulates a lot in the industry and that works to create urgency. But before writing this article I went to the vendors’ own sources, and reality is more nuanced. I believe a head of IT deserves the exact dates, not a headline. Here they are, and what I would do with them.
SAP BusinessObjects: the clock is real
With BusinessObjects there is a clear date. SAP has published that standard maintenance for SAP BI Platform 4.3 ends on 31 December 2026. After that, according to SAP’s maintenance strategy as reported by specialists such as Wiiisdom, only priority 1 support remains, until the end of 2027.
SAP has released a successor version, SAP BI 2025. In other words: if you run BusinessObjects 4.3, in a few weeks you lose standard maintenance and have to choose between upgrading to the new version or moving your reports elsewhere.
In practice: if you run BusinessObjects 4.3, this decision is no longer a 2027 one. It is a today one.
QlikView: it does not end, but every version expires
With QlikView it is different. According to Qlik’s official lifecycle page, the product keeps releasing versions: 12.110 came out on 29 September 2026 and is supported until 30 September 2028. What ends in 2027 is one specific version, 12.100, on 30 September 2027.
In practice, each QlikView version gets about two years of support. If you keep up to date, you stay supported. If you do not upgrade, your version expires.
So why do so many people talk about migrating QlikView? Because Qlik has been nudging its customers towards Qlik Sense for years, and because many organisations have QlikView with hundreds of documents that nobody fully understands any more. The clock is not so much support as the cost of keeping alive something that no longer evolves the way it used to.
In practice: check which version of QlikView you have installed. If it is older than 12.100, you are already out of support.
The real question is not the date
The dates are a good reason to sit down, but they should not decide for you. When you take stock of a QlikView or a BusinessObjects that has years behind it, you usually find:
- reports that nobody has opened for months;
- universes and models that only one person understands;
- per-user licences for people who only look things up;
- two BI tools living side by side, each with its own contract.
Migrating all that as it is means paying twice. That is why the first step is knowing what you have and what is used.
Three destinations, and you choose
When you decide to move, there are three paths:
- Another BI tool, such as Qlik Sense, Power BI or Tableau.
- Your data platform (Databricks, Snowflake or Microsoft Fabric), with metrics calculated once and read the same way from any tool.
- A custom dashboard, with no per-user licence, for those who only look things up.
It is not all or nothing, and it is not against any vendor. The point is for each report to go where it adds the most value.
In practice: do not choose the destination before the inventory. Choose after you know which reports are used and who uses them.
How to migrate without losing a number
A BusinessObjects report or a QlikView document is the number someone looks at every Monday. If it changes, trust is lost. That is why migration is done like this:
- Read-only inventory of reports, models, universes and load scripts.
- What stays, what goes and what gets switched off. What nobody opens is not migrated.
- Rebuild with orchestrated AI, validated by your team.
- Cutover with a number-by-number comparison. The new and the old report live side by side until everything adds up. The previous tool is retired when the last report matches.
The data and the indicators stay: they are the reference everything is compared against.
If you run BusinessObjects 4.3: three decisions before the year ends
If you are on BusinessObjects 4.3, the calendar is tight, so I have put it in order as three decisions:
- Upgrade or move? Going to SAP BI 2025 buys you time and keeps what you have. Moving to another tool, to your data platform or to a custom dashboard frees you from that tie. Both options are legitimate; what makes no sense is not deciding.
- Which reports deserve the trip? Whatever the destination, do not move what nobody opens. Switching it off first lowers the cost of any path.
- How will you show the numbers do not change? Whether you upgrade or migrate, you need to compare before and after, number by number.
And one piece of advice: do not take this decision from IT alone. BusinessObjects universes tend to hide business rules (how margin is calculated, what counts as an active customer) that someone from the business should validate before they are moved anywhere.
In practice: bring together IT and the two or three business owners who use BusinessObjects most, and go through the ten most-used reports together. Half of your plan will come out of that.
Where to start
- Check your versions and their real dates, in the vendor’s own sources.
- Take inventory of reports and models, with their actual use.
- Switch off what is not used.
- Choose the destination for what remains, report by report.
- Migrate a first batch with measured parity and decide with that data.
If you run BusinessObjects 4.3, start now. If you run QlikView, you have a little more room, but do not spend it waiting.
How we help you
In BI and dashboard migration we migrate reports, dashboards, models, universes and scripts 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 licence. Read-only inventory and cutover with a number-by-number comparison.
We do it with the Datagentis migration module, which connects read-only to QlikView, SAP BusinessObjects and the rest of the BI tools, detects what is not used and generates the documentation and the plan before anything is moved.
How many of your QlikView or BusinessObjects reports does anyone open?
In a demo, we show you how we take stock of your reports and models in read-only mode, and what stays, what goes and what gets switched off.


