If you’re still on Qlik Sense Enterprise SaaS user-based, your renewal isn’t a renewal. It’s a migration.
Qlik stopped selling user-based subscriptions to new customers on April 1, 2025. Existing contracts run to term, then everyone moves to capacity. The pricing reorganization is the visible part. The functional realignment underneath is where the real money sits.
Most teams assume capacity is the same product with a different unit of measurement. It isn’t.
What changed on April 1, 2025?
Qlik stopped selling user-based Qlik Cloud subscriptions to new customers. That includes Qlik Sense Business and Qlik Sense Enterprise SaaS at the per-user tier.
The replacement is a four-tier capacity model: Starter, Standard, Premium, and Enterprise. Capacity is measured in Data for Analysis, the volume of data your apps process, not the number of named users.
Existing user-based contracts continue. Renewals push toward capacity. Some legacy entitlements like basic Predict, basic Automate, and basic Reporting are grandfathered in. Most aren’t.
If your renewal is in 2026, this conversation is already on your account manager’s calendar.
Is “capacity” just the same product with different pricing?
No. The feature surface is different.
User-based Qlik Cloud Enterprise SaaS does not include data catalog or lineage. Capacity Standard and above include both. That single difference matters more than any pricing change because lineage is the foundation for compliance audits, dashboard certification, and trust in the numbers.
User-based gates user permissions behind two entitlement types. Professional users can build apps. Analyzer users can only consume them. An Analyzer user literally cannot author content. To upgrade them, you buy a different license.
Capacity removes that split entirely. Any user can be granted any capability. Permissions become role-based, not entitlement-based.
That single change reshapes how teams license. More on that below.
What you actually lose moving from user-based, and what you gain
The lose-and-gain accounting depends on which capacity tier you migrate to. Not all migrations are equal.
What you lose if you fall to Starter or Standard:
- Qlik Predict / AutoML beyond legacy basic tier (Premium and above only)
- Qlik Talend Data Integration and data movement (Premium and above only)
- Data quality and governance tools (Premium and above only)
- Data marketplace and data products (Premium and above only)
What you gain even at Standard:
- Catalog and lineage that user-based never had
- The Professional / Analyzer entitlement disappears
- Overage tolerance up to 10x your purchased capacity (user-based hard-stops at the limit)
- Consumption metrics in the management console
- A larger app size baseline (10 GB on Premium vs 5 GB on legacy user-based)
If you migrate to Premium or Enterprise, you gain everything above plus the full data integration stack and multi-tenant management.
If you migrate to Standard because the price looks attractive, you’ve removed Predict, Talend, governance, and Marketplace from your roadmap.
That’s the trap.
Why is catalog and lineage the most important difference?
Because every enterprise eventually hits the question: where did this number come from?
Without lineage, the answer is “probably the warehouse, but ask the developer who built the app.” Without a catalog, “show me every dashboard that uses the customer dimension” is a manual scavenger hunt.
User-based Qlik Cloud has neither. You can buy Qlik Catalog as a separate product, but you’ve now stacked two contracts to get one workflow.
Capacity Standard includes both at no incremental cost. They’re part of the entitlement.
For regulated industries, this is the difference between a passable compliance audit and a four-week emergency project. We’ve seen this play out at GDPR-driven implementations where lineage isn’t a nice-to-have. It’s the audit trail.
Which capacity tier actually fits enterprise use?
For anyone running a real BI deployment with finance, operations, and compliance stakeholders: Premium is the practical floor.
Standard is where companies running Tableau or Power BI for visualization-only might land. It works. It’s cheaper. But it has no Predict beyond grandfathered basic, no Talend, no data quality tooling, and no data products. The roadmap from Standard up is an upsell, not a feature flag.
Premium adds:
- Qlik Predict / AutoML at full capability
- Data movement (Talend), including SAP and mainframe sources
- Data quality and governance toolset
- Native multi-tenant management within one license
- Larger app baseline (10 GB) and an upgrade path to 50 GB
Enterprise adds:
- Multi-region tenants
- 15 GB app baseline plus a 40 GB large-app pack included by default
- Highest reload concurrency (10 simultaneous app evaluations)
For most mid-market customers running Qlik as their primary analytics platform, Premium is the right answer and Standard is the wrong one. The pricing delta looks tempting until you realize you’ve removed three product lines from your stack.
Should multi-tenant or OEM customers care?
Yes, and this is where the model change is hardest.
If your client architecture involves serving multiple customers from a single Qlik Cloud deployment, you need Premium or Enterprise. Standard does not include native multi-tenant management. User-based never did.
OEM scenarios, where you embed Qlik analytics into your own software product, fall into the same bucket. The tenant management APIs and the capacity pooling that makes OEM economics work only exist at Premium and above.
If you’ve been running an OEM workload on user-based, your renewal is going to involve a tier jump. Build that into your customer pricing now, not after the contract conversation.
For OEM deployments specifically, lineage and catalog start to matter doubly. You’re not just satisfying your own compliance, you’re satisfying every customer’s compliance.
How does the Analyzer-Professional split disappear?
This is the quiet win for most companies.
Under user-based, every employee who could build content needed a Professional license. Every consumer needed an Analyzer license. The split was rigid. The pricing was per-seat. Right-sizing meant audit-cycle fights about who actually needed Professional and who could be downgraded.
Under capacity, everyone is just a user. Build permissions are granted at the space level via roles. The license doesn’t gate the capability anymore.
For a company with 200 Analyzer users and 30 Professional users on legacy licensing, capacity migration means you stop paying the Professional premium for users who only build occasionally. The cost shifts from “how many builders do I have?” to “how much data do my apps process?”
For most teams that’s a net win. The exception is high-data-volume, low-user-count environments. Large finance shops with heavy ETL but small consumer bases might find capacity less efficient than the old user-based math.
The hidden money in the migration: if you’ve been over-licensing Professional users to allow occasional content creation, capacity recovers that spend. If you’ve been under-licensing Analyzer-bound users who actually need to build, capacity unlocks them without a license upgrade.
What does this mean for your next renewal?
Three things to do before the renewal conversation, not during it:
- Audit your Professional vs Analyzer split. Count how many Professional licenses are paid for users who build less than once a month. That number is your over-licensing exposure under user-based. It disappears under capacity.
- Map your data volume. Capacity is priced on Data for Analysis, not seats. Pull your tenant utilization metrics and figure out which capacity tier sizing matches your real usage. Standard’s data envelope is small. Premium’s is materially larger.
- Decide if you need Predict, Talend, governance, or multi-tenant. If yes, Premium minimum. If no, Standard might fit. There is no “buy Standard now and add Predict later as a flag” option. You pay the tier, you get the features.
For teams already mid-migration from QlikView or on-premise Qlik Sense Enterprise, the renewal conversation overlaps with a cutover plan. Our Qlik Cloud migration strategy guide covers the architectural side. The licensing side is usually decided in parallel, and the wrong tier choice costs more long-term than any migration mistake.
The pattern: capacity favors mature deployments and punishes thin ones
Capacity is a better model if you have a real enterprise deployment with diverse users, governance requirements, and data integration needs. The Professional / Analyzer ceiling disappears. Catalog and lineage arrive. Predict and Talend become accessible at Premium.
It’s a worse model if you’re using Qlik as a per-seat visualization tool with no governance pressure and no AI or ML aspirations. In that case, the pricing favors capacity but the feature unlock you’re paying for goes unused.
The honest take: most companies underestimated what user-based was missing. They notice it once capacity arrives and they suddenly have lineage. They wonder why it took five years.
The migration isn’t a renewal. It’s a feature unlock disguised as a pricing change.
If your renewal is six to twelve months out, this is the right time to audit. If it’s closer than that, the audit becomes a constraint, not a strategy.
Where to go next
If you want to see how the migration plays out architecturally, our Qlik Cloud migration strategy guide walks through tenant setup, cutover, and timelines.
If you’re worried about lineage and certification under the new model, the data governance framework shows what the catalog actually unlocks.
If you want to know what each tier costs in concrete numbers, the Qlik Cloud pricing 2026 breakdown covers the cost mechanics that this post deliberately avoids.