Which fits: Qlik Sense or Metabase for self-service exploration
If your Qlik renewal, a licensing change or a data residency requirement has put Qlik Sense under review, and business users explore data on their own, the decision turns on where your analytical logic lives. Qlik Sense fits teams that depend on associative in-memory apps and load scripts, where data is reshaped in the load script, held in memory and explored through selections that cross every field. Metabase fits teams whose data already sits in SQL databases and who want questions, dashboards and simple exploration on top of those tables, with the transformation done in the database or a modeling layer rather than inside the BI tool.
Metabase's free Open Source edition is self-hosted with unlimited users and dashboards, but the Pro plan is where SSO and row and column level permissions appear according to Metabase's pricing page. If your auditors or data owners require SSO or row-level access control from day one, price the Pro plan into your comparison from the start instead of assuming the free tier covers it. Confirm the current feature list on the Metabase pricing page before you decide, because plan contents change.
The decision therefore turns on three questions. First, how much of your estate relies on load script logic and set analysis, since that work must be rebuilt as SQL or dbt models before it can move. Second, whether SSO and row-level permissions must be available on the free tier or whether a paid plan is acceptable. Third, who maintains the stack after go-live: a team that already runs PostgreSQL, upgrades and backups will carry Metabase more easily than one with no operations capacity, and that staffing gap belongs in your quote as much as the license line.
Which option fits which scenario
This table matches common Qlik Sense estate situations to the platform that fits best, with the condition that drives each choice. Read each row against your own user mix, data platform and network constraints, since the right answer often depends on one or two of them.
| Scenario | Better fit | Condition that drives the choice |
|---|---|---|
| Analyzer-heavy dashboard consumers | Metabase | Most users view and filter published dashboards rather than building associative apps, so Metabase questions and dashboards map closely to that work. |
| Associative exploration across many sources | Qlik Sense (or a warehouse-first redesign) | Qlik's in-memory associative model lets users click through unrelated sources in one app; Metabase needs those sources joined in the database first. |
| Team with a warehouse and strong SQL skills | Metabase | Metabase queries the connected database directly, so the logic lives in SQL or modeled tables that your data team already maintains. |
| Heavy load script transformations | Qlik Sense until scripts are moved | Scripts that reshape data in memory must be rebuilt in SQL, dbt or a pipeline before Metabase can serve the same results. |
| Air-gapped or offline networks | Metabase, with a plan for offline installs and upgrades | Confirm the edition, image and upgrade files you need in advance, and check how Qlik's license activation works in your isolated network. |
| SSO and row-level security required | Metabase Pro or Enterprise, or Qlik Sense with its own security model | Row and column permissions and SAML or OIDC setups are paid Metabase features, so confirm the plan covers your identity provider before committing. |
| Need for a quick, free self-hosted start | Metabase Open Source | The free AGPL edition has unlimited users and dashboards, but lacks SSO and row-level permissions, so pilot before scaling. |
How Qlik licensing and Metabase editions differ
Qlik Sense Enterprise on Windows is the client-managed product. You install it on your own servers and activate it with a signed license key. Users are split into professional and analyzer access types, and the client-managed product ships in month-named releases such as November 2025 and May 2026. Your total cost depends on how many people build content and how many only consume it, so the access mix matters as much as the headline count.
- Access types: Professional users build and edit apps, while analyzer users consume published content and make selections. Confirm how Qlik defines each type in your contract.
- Infrastructure: The Windows servers, databases, storage and backups are yours to buy, patch and refresh on a recurring cycle.
- Release support: Each client-managed release has a support window. Plan upgrades against Qlik's published schedule and do not assume an older install stays supported.
- License activation: The signed license key depends on connectivity to Qlik's license backend. Ask Qlik whether your network needs outbound access and whether a License Enabler File is available for your environment.
- Renewal terms: Check the term, the number of each access type and the release your servers run against the vendor documentation in Qlik's introduction to Qlik Sense Enterprise.
Before comparing, confirm your current access allocation, the release you run and whether your network can reach the license backend as the contract assumes.
Qlik Cloud Analytics is the SaaS option that Qlik hosts and manages. The platform fee covers hosting, patching and vendor-run upgrades, so your recurring cost shifts from servers and staff time toward subscription capacity. Pricing is organized around capacity tiers rather than installed servers. The right tier depends on data volume, user count and usage patterns. No tier figures are listed here, so request the current definitions in writing.
- Capacity tiers: Ask what each tier includes, including data volume, usage measures and the rules for moving to a higher tier mid-term.
- Data location: Confirm the hosting region and whether your data leaves your jurisdiction, because Qlik operates the service.
- Connectivity to on-premises sources: Reaching internal databases from a SaaS platform is a separate architecture question. Ask what Qlik requires, who operates any gateway components and who pays for them.
- Exit path: Ask what content and data you can export from Qlik Cloud, in which formats and with what effort, before you sign.
- Growth assumptions: Model user and data growth over the contract term, because capacity overage and tier changes usually drive the difference from the first-year quote.
Before you compare with a self-hosted option, ask Qlik for a written quote that states the tier, the scaling rules and the renewal terms.
Metabase Open Source is free to self-host, with unlimited users and dashboards. Its code outside the enterprise directory is licensed under AGPL-3.0. Starter is the first paid plan, priced at $100 per month, or $90 per month billed yearly, with the first 5 users included. Starter adds Google sign-in and LDAP, but it does not include SSO or row and column level permissions. Check the current terms on the Metabase pricing page before you budget.
- Open Source cost: There is no license fee. You pay for the host, the application database, backups, staff time and upgrades.
- Starter fee: $100 per month, or $90 per month billed yearly, covers the first 5 users. Additional users cost $6 per month.
- Authentication: Google sign-in and LDAP are available. JWT, OIDC, SAML and SCIM require Pro or Enterprise.
- Missing controls: SSO, row and column level permissions, multi-tenant data segregation and usage analytics and auditing are not included in Open Source or Starter.
- Recurring work: Upgrades run database migrations automatically, so plan backups and a maintenance window for each release.
Before you choose Open Source or Starter, confirm with your auditors whether network controls, database permissions and your own logging can meet the access requirements in place of the paid features.
Pro adds SSO and row and column level permissions, which are the controls most governance teams need for shared data. Pro is priced at $575 per month, or $517.50 per month billed yearly, with the first 10 users included. Enterprise is quoted and starts at $20,000 per year. Metabase's commercial code sits in the enterprise directory under the Metabase Commercial License, so the paid features are not part of the AGPL code. The enterprise image is also a separate build from the open-source image.
- Pro fee: $575 per month, or $517.50 per month billed yearly, covers the first 10 users. Additional users cost $12 per month.
- Enterprise quote: The starting point is $20,000 per year. Ask what support, deployment assistance and contract terms the quote includes.
- Air-gapped deployment: Only the Enterprise plan offers it, so isolated networks need that plan or a verified offline process.
- Image selection: The metabase-enterprise image is separate from the metabase/metabase image. Confirm which image your build pipeline pulls and which license terms apply to it.
- Identity sync: Advanced LDAP group and attribute sync and SCIM provisioning need Pro or Enterprise, so confirm they match your directory design.
Before you deploy, confirm the plan limits, identity requirements and the Metabase version support window in writing.
Where your data and identities live under each option
Qlik and Metabase differ on where data is processed, where license checks go, and which identity features sit behind which plan. Each card below is a placement or identity decision to settle before a pilot, so the security and compliance teams can review them with the business owners.
Qlik client-managed data location
Qlik Sense Enterprise on Windows runs on servers you operate, so loaded data, QVF apps and the in-memory model stay inside your network and backup scope. Confirm which hosts hold the repository, the engine and the logs, and who can read the QMC export files. Those files can carry data if exported with it.
Qlik Cloud data location
Qlik Cloud is hosted and managed by Qlik, so data residency, tenant region and subprocessor terms come from Qlik's contract rather than your own racks. Ask Qlik in writing where tenant data is stored and processed, how it is backed up, and what happens to data at contract end. This is the location question to settle before any sensitive dataset is loaded.
Qlik license backend reachability
Qlik's signed license key requires that the server can reach Qlik's license backend, so network egress rules become part of the architecture. A blocked outbound path can stop activation or renewal in a segmented network. Confirm the required endpoints with Qlik and document whether a License Enabler File is available for your environment.
Metabase on your own servers
Metabase runs as a JAR or Docker container in your own infrastructure, and questions query your connected databases directly. Query results, cached data and dashboard snapshots are held where Metabase runs, so encryption, backup and retention must cover the Metabase host. Confirm where any cache and temporary export files are written and how long they persist.
Metabase application database choice
Metabase stores users, questions, dashboards and permissions in an application database. It ships with embedded H2 for demos, while PostgreSQL is the recommended production choice, and MySQL 8.4.0 or MariaDB 10.6.0 and later with utf8mb4 are also supported. Treat this database as the system of record for access and content, and move off H2 before any production use.
Identity options by Metabase plan
Open Source and Starter support Google sign-in and LDAP, while JWT, OIDC, SAML and SCIM provisioning require Pro or Enterprise. If your directory is Entra ID, Okta or Keycloak and you need SAML or OIDC, the Pro plan or higher is part of the decision, not an add-on. Confirm which identity provider you use before costing the plan.
Row-level permissions and compliance readiness
Row and column level permissions, multi-tenant segregation and usage auditing sit in Pro and Enterprise, not Open Source or Starter. If row-level access underpins your data access model, make it a plan requirement. Compliance work here is readiness only: you prepare controls and evidence, and independent auditors issue any report.
How a self-hosted Metabase stack connects to your warehouse
A self-hosted Metabase stack has two databases with separate jobs. Business users open Metabase in a browser, and each question they build or dashboard they load is turned into SQL that runs against the databases you connect, such as your warehouse or production replicas. The results come back to Metabase for display. The application database is different: it stores Metabase's own metadata, including users, groups, permissions, saved questions, dashboards and settings. Your data stays in the source systems, and Metabase's application database holds the configuration that governs who can see what.
This distinction shapes the rollout. Metabase ships with an embedded H2 database, which suits a demo or proof of concept but should not hold production metadata. The Metabase documentation recommends PostgreSQL for production, and MySQL 8.4.0 or MariaDB 10.6.0 and later with utf8mb4 are also supported. If you have already run a trial on H2, the documented load-from-h2 command moves that data to PostgreSQL or MySQL, but it must be run with the same Metabase version that last updated the H2 file. Plan that step before users start building content you want to keep.
Before you size the stack, confirm two lists with your data team: every source database or warehouse Metabase must query, and the driver each one needs. Metabase connects through its built-in drivers and community drivers, and driver support differs by database, so check the exact version against the Metabase documentation for each engine. Also confirm where the connections will run and which network paths and service accounts they use, since query load lands on those systems. An illustrative case: if finance reports come from a warehouse and operational views come from a PostgreSQL replica, you need both drivers tested and both read-only accounts provisioned before the pilot.
What each option costs to own, and what drives it
Qlik and Metabase price their software in very different ways, but the cost of running either one sits in the same places: infrastructure, database load, upgrades, backups and staff time. The cards below separate the recurring license line from the one-time and ongoing components so you can build a like-for-like comparison before asking for quotes.
Qlik license and capacity fees
Qlik Sense Enterprise on Windows is licensed through access types and the server fees attached to them, and Qlik Cloud Analytics is priced by capacity tier. Both are recurring, so a renewal or tier change moves your annual run cost directly. Ask Qlik or your reseller to itemize every access type, add-on and capacity unit in writing, and to state what happens to the license if you stop paying.
Metabase Open Source at no license cost
The Open Source edition is free to self-host, with unlimited users and dashboards, so its license line is zero. You still pay for the servers, the application database and the people who run them. Check which features you need before choosing it, because SSO and row and column level permissions are not included in this edition.
Metabase Starter and Pro plan fees
Starter is listed at $100 per month, or $90 per month billed yearly, with the first 5 users included, and Pro at $575 per month, or $517.50 per month billed yearly, with the first 10 users included. Additional users cost $6 per month on Starter and $12 per month on Pro. Pro is the plan that includes SSO and row and column level permissions, so for many Qlik replacements it is the line to price.
Metabase Enterprise by quote
The Enterprise plan is priced by quote, starting at $20,000 per year according to the Metabase pricing page, and it is the only plan that offers air-gapped deployment. If your Qlik estate is air-gapped, this line will likely decide the comparison. Ask for the quote to state the user count, support terms, deployment model and renewal uplift.
Infrastructure and database load
Both options add hosting costs that vary with user count, query volume and data size. Metabase runs as a JAR and needs an application database, and PostgreSQL is recommended for production. Qlik's in-memory apps shift load to the Qlik server, while Metabase pushes queries to your warehouse, so check warehouse compute and concurrency costs against your current Qlik load.
Upgrades, backups and staff time
Upgrades and backups are the recurring work that is easiest to underestimate. Metabase runs application database migrations automatically, so back up the application database first and plan a maintenance window for major versions. Ask any implementation partner for a fixed-scope estimate covering the initial build, the Qlik script rework, the cutover, and the ongoing upgrade and backup routine.
What moving from Qlik Sense to Metabase involves
The sequence turns a Qlik estate into a tested Metabase deployment where analysts and business users can explore the same governed data, with the Qlik release lifecycle as the deadline that sets the pace.
Inventory Qlik apps, users and data sources
Start by listing every Qlik Sense app, its owner, its load script data sources, the sheets and charts business users open, and the named and analyzer users who depend on them. Record which apps refresh on a schedule and which feed other apps or external reports. Compare this list against your licensing so you know which users and access rules must carry over. The step is done when you have one inventory sheet that a data owner has reviewed and signed off, with each app marked as migrate, retire or merge.
Export Qlik apps and document load logic
For client-managed Qlik Sense Enterprise on Windows, export the app files that your installation permits from the Qlik Management Console, and keep a copy of every load script, variable and data connection definition in version control. Qlik Cloud estates need the export path confirmed with Qlik for your tenant. Note that extensions and ODBC data connections must be recreated by hand. The step is done when each app has an archived export and a written record of its script logic.
Rebuild load script logic as SQL or warehouse models
Qlik load scripts combine extraction, joins, calculated fields and set analysis in one place. Move the extraction and transformation logic into SQL views or a warehouse modeling layer that Metabase connects to directly, so that the same definitions serve every question. Set analysis expressions usually become explicit aggregations in SQL. The step is done when each migrated app has a documented set of views, row counts agree with the Qlik output for a sample period, and the owner has confirmed the figures match.
Recreate dashboards as Metabase questions
Rebuild each Qlik sheet as Metabase questions, dashboards and filters on the modeled tables. Qlik associative selections do not carry over directly, so decide which filters a user needs and map them to dashboard filters or linked questions. Keep the question names and metric definitions in one place so that the same measure is not defined twice. The step is done when every in-scope sheet has a Metabase dashboard and a business owner has compared the numbers against the Qlik version.
Configure SSO and row-level permissions on the right plan
Confirm the Metabase plan before you design access. Google sign-in and LDAP are available on the free Open Source edition and Starter, while SSO through JWT, OIDC or SAML, and row and column level permissions, are included only in Pro and Enterprise, according to Metabase's pricing page. Map your Qlik section access rules to Metabase groups and data permissions, then test with accounts from each group. The step is done when a test user in each group sees only the rows and columns they are entitled to, and the chosen plan is recorded in your change request.
Pilot with analysts and collect feedback
Give a small group of analysts and business users access to the migrated dashboards in a non-production instance with production-like data. Ask them to rerun the questions they use most each week, compare results with Qlik, and log gaps such as missing drill paths or filter behavior. Fix the models and dashboards that fail the comparison. The step is done when the pilot group has signed off on every critical dashboard and the open issues are either closed or accepted with an owner.
Cut over and retire the Qlik apps
Schedule the cutover with the business owners, freeze changes to the Qlik apps, run a final reload and comparison, and then point users and scheduled distribution to Metabase. Keep the Qlik apps read-only for a defined period so that users can check historical figures. Plan the cutover before the client-managed Qlik release you run reaches end of support, because a forced upgrade would otherwise set the date. The step is done when all users access Metabase, the access log shows the old apps are no longer used, and the retirement record is filed.
Questions buyers ask before choosing Metabase over Qlik Sense
Does Metabase replace Qlik associative selections?
Not one for one. Qlik's associative engine keeps every field linked in memory, so a click on one value narrows all related fields at once. Metabase works differently: each question runs a SQL query or a visual query against your connected database, and dashboards pass filters between cards. Business users who explore data themselves can build questions and drill down, but they will not get the same instant, cross-filtered exploration across loosely related tables. Before committing, test your most-used Qlik sheets with the people who use them and confirm that the filter behavior they rely on can be rebuilt on the warehouse tables you already have.
What does the internal team need to run Metabase after migration?
Your team needs someone who can administer a Java application, manage a PostgreSQL or MySQL application database, and maintain database connections and permissions. Analysts who currently write load scripts will need SQL skills, because transformations that lived in the Qlik script move into queries, views or a transformation tool in the warehouse. Metabase's own documentation recommends PostgreSQL for production and notes that the embedded H2 database is meant for demos, so plan that database from the start. Ask your team to confirm which of these skills it already has and where the gaps sit.
Can an internal team migrate from Qlik to Metabase without outside help?
A capable internal team can do it, provided it has time, SQL skills and a clear inventory of Qlik apps. Many teams start with a pilot on a few high-use dashboards, then expand. Outside help is most useful for the parts that are easy to underestimate: converting set analysis and complex load script logic, designing the permission model, hardening the deployment and writing the runbooks. Whether to engage a partner depends on your staff capacity and risk tolerance. DeployOpen plans, implements and documents self-hosted platforms in your own infrastructure under a written, fixed scope, so the effort can be agreed before work starts.
What drives the effort of a Qlik to Metabase migration?
The main drivers are the number of apps and sheets in use, how much logic sits in Qlik load scripts and set analysis, and how many data sources must be reconnected. Effort rises when apps depend on QVD layers that have no warehouse equivalent yet, when many users rely on associative selections, or when row-level security must be rebuilt. It falls when most analytics already run on a warehouse with clean tables and when your usage concentrates in a small set of dashboards. Ask any proposal to split the work into inventory, data model, rebuild, permissions, cutover and training, and to state which items it assumes you will provide.
Does Metabase's free edition include SSO and row-level security?
No. The free Open Source edition is self-hosted with unlimited users and dashboards, but according to Metabase's pricing page, SSO, row and column level permissions, multi-tenant data segregation and usage analytics and auditing are included only in the Pro and Enterprise plans. Starter also excludes them. Google sign-in and LDAP are available on Open Source and Starter, while JWT, OIDC, SAML and SCIM provisioning require Pro or Enterprise. If you need SSO or row-level security from day one, budget for Pro and confirm current pricing directly with Metabase, since the pricing page is the source for plan contents.
How do Metabase upgrades work, and what should we plan for?
Metabase runs application database migrations automatically when you upgrade, so the upgrade is a change to your production system and needs a plan. Metabase recommends backing up the application database first, reducing a cluster to a single node for major upgrades because of a migration lock, and upgrading release by release if you are coming from a version older than 40. Non-LTS versions usually reach end of life after 2 months, while LTS versions are supported for 14 months. Metabase 64 is an LTS release with end of life on 1 December 2027, so choosing an LTS line can reduce how often you upgrade.
When is a move to Qlik Cloud simpler than migrating?
Moving to Qlik Cloud can be simpler when your organization has committed to Qlik skills and processes, when hosting Qlik on your own Windows servers is the main burden, and when the data and identity setup already fits Qlik's managed service. It is less attractive when the main concern is licensing, data residency or lock-in, since Qlik Cloud is hosted and managed by Qlik rather than in your infrastructure. Compare the capacity pricing you would be quoted against the cost components of self-hosting. Ask Qlik to confirm what the subscription includes, how capacity is measured, and how exports of your apps would work if you leave later.
Which Qlik licensing questions should we answer before choosing Metabase?
Start by listing what you license today: Professional and Analyzer user access on Qlik Sense Enterprise on Windows, or Qlik Cloud Analytics capacity. Then confirm your release timeline, since client-managed releases have a support window and older installs face a forced upgrade. Also confirm whether your Qlik deployment needs internet access to a license backend, which matters for isolated networks. Metabase's cost is separate: the free edition has no license fee, while paid plans are priced per month or by quote. Ask Qlik for a written statement of entitlements and renewal terms so your comparison uses the same basis.
How Metabase releases and upgrades affect running operations
Metabase LTS releases are supported for 14 months, while non-LTS releases usually reach end of life after about two months. That gap decides how often your team must upgrade. Metabase 64 is an LTS release published on 16 September 2026 with end of life on 1 December 2027, and Metabase 65 followed on 12 October 2026 as a non-LTS release. Before you commit to a version, check the current support table on the Metabase version support page, then plan which line your Qlik replacement will run on for the next two years. Confirm the end-of-life date of whatever version you deploy, because a non-LTS build on a fixed cycle means an upgrade calendar you must staff.
Every Metabase upgrade runs application database migrations automatically at startup. The application database holds dashboards, questions, users, permissions and the sync settings for your connected warehouses, so a failed migration affects every analyst at once. Make a verified backup of the application database before each upgrade, and restore-test it on a copy. If you run a cluster, the upgrading guide recommends reducing it to a single node for major upgrades because of a migration lock. Schedule that window with business users in mind, since Metabase will be unavailable to them during the change. The upgrading Metabase guide lists the full sequence.
If your instance is older than release 40, do not jump straight to the current version. The upgrade guide asks you to step through each release in order, so budget extra change windows for a legacy install. Document each step, the backup location and the rollback path, and keep the previous container image available until the new version has run through your normal reporting cycle. Also confirm whether your Metabase plan includes the features your users depend on, such as SSO and row-level permissions, because those settings survive upgrades only when the plan that enables them is still in place. Ask your implementation partner to include upgrade runbooks and a test environment in the written scope.
How DeployOpen helps evaluate and implement a Qlik to Metabase move
DeployOpen plans, implements, integrates, hardens, backs up, documents and supports self-hosted open-source platforms inside your own infrastructure, including Metabase. For a Qlik Sense vs Metabase decision, we start by testing whether your business users' work is exploration of connected databases or consumption of Qlik apps, then build only what the written scope agrees.
How we scope
- Inventory which Qlik apps, load scripts and users are in use, and which of them actually explore data.
- Map each in-scope Qlik app to the Metabase questions, dashboards and connected databases it would need.
- Agree the Metabase edition, the single sign-on and row-level permission needs, and the license backend connectivity assumptions in writing before work starts.
How we build
- Deploy Metabase in your own cloud account, data center or air-gapped network with a PostgreSQL application database.
- Rebuild in-scope dashboards against your warehouse or databases, and document where Qlik set analysis logic moves into SQL.
- Test permissions, sign-in paths and query results against the Qlik outputs they replace before any user is moved.
How we hand over
- Deliver configuration, runbooks, permission models and a record of each rebuilt Metabase question and dashboard.
- Document the Qlik export steps completed, including QVF files and any data connections that must be recreated manually.
- Train named administrators on upgrades, including taking an application database backup before each Metabase upgrade.
How we support
- Offer ongoing support, upgrades and continuous testing as a retainer after the fixed-scope engagement ends.
- Plan Metabase version upgrades against the published version support dates, so each move follows a supported release.
- Confirm with your team who owns query performance, warehouse access and user onboarding after handover.
