--- Brand: klarmetrics.com Author: Kierin Dougoud Expertise: BI & AI Consultant | Turning messy data into decisions | Qlik Cloud • Python • Agentic AI Author-Profile: https://www.linkedin.com/in/mkierin/ Canonical-URL: https://klarmetrics.com/qlik-nprinting-end-of-life/ --- # Qlik NPrinting End of Life: Your Migration Options in 2026 # Qlik NPrinting End of Life: Your Migration Options in 2026 **Qlik NPrinting** is not being turned off tomorrow. The most current release (February 2025) has an official end of support date of **February 18, 2027**. But the product has been in maintenance mode since at least late 2023, meaning no new features are coming: only bug fixes and security patches. If you are running NPrinting today, that gives you a real runway to plan, but not an excuse to wait. This post covers what the current status actually means, what you need to replace, and which migration path fits your situation. Once the timeline is clear, the immediate follow-on is what Qlik Cloud reporting actually costs at your current user count. [The pricing question usually comes right after the timeline question](/qlik-cloud-pricing-2026/) — and the answer is different from what most NPrinting administrators expect. # What is NPrinting’s current status? NPrinting is in maintenance stage, not actively discontinued. Qlik confirmed this publicly in a community thread: *“NPrinting is now in maintenance stage so only bug fixes and ongoing support is happening plus individual features from ideation.”* The February 2025 release was the most recent, with Service Release 3 as the latest patch as of early 2026. Qlik’s standard on-premise release policy supports each version for two years from its initial release date. That puts the current version’s end of support at **February 18, 2027**. If you are still running an older NPrinting release, your support window may already be shorter. The key distinction here: there is no formal discontinuation announcement. But the absence of new feature development, combined with Qlik’s full investment in cloud-based reporting, tells you where this is going. The product exists in a holding pattern while customers migrate. One more critical fact: **NPrinting does not work with Qlik Cloud at all.** Qlik has confirmed this officially: “There is no direct migration path between NPrinting Reporting and Qlik SaaS (Cloud) reporting as they are completely independent reporting platforms.” The moment you move your Qlik Sense apps to Qlik Cloud, NPrinting stops connecting. You cannot run both in parallel across the migration. # What does NPrinting do that you need to replace? Before choosing a migration path, you need an honest inventory of what you are actually using. NPrinting covers a broad set of capabilities, and not all of them have equally good native replacements in Qlik Cloud. The six capabilities that matter most for migration planning: * **Pixel-perfect reports**: The PixelPerfect engine (based on Fastreport) gives you full WYSIWYG layout control. Think invoices, statutory financial reports, documents where position and formatting are non-negotiable. * **Burst distribution**: One report task generates a personalized version for each recipient, filtered to their data. Recipients receive their version by email without needing a Qlik login or license. * **External recipient email**: You can distribute to anyone with an email address. Recipients do not need to be Qlik users. * **Dynamic recipient lists**: Recipient lists are driven by fields in your Qlik data model. When a salesperson joins or leaves, the distribution list updates automatically. No manual maintenance required. * **On-demand reports**: An embedded button in a Qlik Sense sheet lets a user apply their own selections and download an instantly filtered formatted report. No developer involvement after setup. * **NewsStand portal**: A self-service web portal where users log in to browse available reports, subscribe to scheduled deliveries, and download on-demand versions. Also worth noting: NPrinting is the only native Qlik tool that supports **QlikView**. If you are still on QlikView, your migration picture is more complex than for Qlik Sense users. # What does Qlik Cloud offer natively? Qlik Cloud’s built-in reporting has improved significantly over the past two years and covers the majority of standard reporting use cases. It will not replace NPrinting feature-for-feature, but for many organizations it will be enough. The **Qlik Cloud Reporting Service** is native to Qlik Cloud Analytics. It supports Excel, Word, PowerPoint, PDF, and HTML output formats. Distribution options include email (PDF or PowerPoint attachments), SharePoint folder delivery, and direct download. Scheduled delivery runs through subscriptions. Key limits to plan around: * **1,000 recipients per distribution list** (hard cap) * Maximum 500 unique reports per report task * Maximum 200 pages per Qlik Automate report * 30,000 reporting requests per day per tenant * Template size limits: 10 MB for Excel and PixelPerfect, 30 MB for Word and PowerPoint The **PixelPerfect editor is now available natively in Qlik Cloud**, which is a significant improvement from a year ago. However, it is not at full feature parity with NPrinting’s Fastreport engine. Known gaps include: no support for Open Type Fonts (.otf), no containers, no filter panes or maps, and limitations on conditional column visibility. For straightforward formatted reports it works well; for complex multi-section layouts with precise pagination, expect manual remediation work. A notable addition in 2025 is the **Microsoft O365 Add-in**, which lets report developers author Word and PowerPoint templates directly in native Office applications, pulling live Qlik Cloud data. This is a meaningful step for teams whose report authors are more comfortable in Word than in Qlik’s template editors. One clear limitation remains: **subscriptions in Qlik Cloud require the recipient to have a Qlik Cloud user account.** External recipients (customers, suppliers, non-Qlik staff) cannot receive subscription reports directly. That gap is filled by Qlik Application Automation, covered in the next section. # Where does Qlik Application Automation fill the gap? **Qlik Application Automation** (also called Qlik Automate) is Qlik’s no-code workflow automation tool, and it is now the official answer for burst reporting and external recipient distribution in Qlik Cloud. Qlik officially documents how to replicate NPrinting-style burst reporting using the **Qlik Reporting connector** in Automate. A single automation can loop through a recipient list, generate a filtered report for each recipient, and send it by email, all without the recipient needing a Qlik account. This covers the external recipient gap that native subscriptions cannot handle. Beyond email, Automate can deliver reports to **Microsoft Teams, Slack, Amazon S3**, and other channels. For Slack delivery workflows, see this tutorial on [Qlik Automate Slack integration](https://klarmetrics.com/qlik-automate-slack-integration-tutorial/). For email automation patterns, the [Qlik Automate email automation](https://klarmetrics.com/qlik-automate-email-automation-tutorial/) guide covers the setup in detail. Two things to be aware of before planning your Automate-based reporting stack: * Qlik Application Automation requires a **Premium or Enterprise subscription**. It is not available on base Qlik Cloud Analytics plans. * Automate caps individual report output at 200 pages per report. If your burst reports are long-form documents, test this limit against your actual output early. Automate does not replace the on-demand report button capability from NPrinting. That remains an open gap in the native Qlik Cloud stack as of early 2026. # What are the third-party NPrinting alternatives? Three tools are widely positioned as NPrinting replacements: **Qalyptus**, **Mail & Deploy**, and **ConnectReport**. Each has different compatibility coverage and differentiators worth understanding before you evaluate. Capability Qlik Cloud Native Qalyptus Mail & Deploy ConnectReport Qlik Cloud (SaaS) Yes (native) Yes (Cloud version) Yes Yes Qlik Sense on Windows No Yes (Self-hosted version) Yes Yes QlikView support No Yes (Self-hosted only) Yes Unclear Burst reporting Via Automate (Premium) Yes Yes Yes External email recipients Via Automate (Premium) Yes Yes Yes Excel, Word, PowerPoint Yes Yes Yes Excel, PDF, PPT (Word unclear) PixelPerfect / precise layout Partial (evolving) Yes Unclear Unclear Multi-BI-source reports No No Yes (Power BI, Snowflake, SQL) No Third-party extension support Limited Yes (full Vizlib support) Yes Yes Public pricing No No No No **Qalyptus** is the closest structural match to NPrinting. It comes in a self-hosted version (on-prem, for Qlik Sense on Windows and QlikView) and a cloud version (for Qlik Cloud only). The two versions are separate products, not a single platform. Qalyptus claims migration from NPrinting takes around 10 days with expert support. It supports existing NPrinting template structures, full Vizlib extension output, and more granular permission management than NPrinting. The Qalyptus Hub provides the self-service portal equivalent to NPrinting’s NewsStand. **Mail & Deploy** is the only option here that works across Qlik Cloud, Qlik Sense on Windows, and QlikView in a single platform. That single-platform coverage makes it particularly relevant for organizations running a phased migration where on-prem and cloud coexist. It also supports Power BI, Snowflake, Databricks, and SQL databases, which is relevant if you have a mixed BI environment. Distribution channels include Teams, Dropbox, AWS S3, and SharePoint, in addition to standard email and FTP. **ConnectReport** takes a different positioning angle: fully browser-based, no desktop software required for template authoring. It inherits the Qlik Cloud security model including [Section Access](https://klarmetrics.com/25-qlik-section-access/) rules for per-recipient data filtering. Its focus on self-service design and open APIs makes it a fit for teams that want end-users to build their own report templates. It supports scheduled delivery and external recipients. All three require direct vendor contact for pricing. Run a proof-of-concept with your actual complex reports before committing. Template compatibility is the main variable that determines how long the migration takes. Organizations running NPrinting with row-level security have a specific migration sequence. [Section Access is the most common blocker for NPrinting migrations specifically](/section-access-qlik-cloud-vs-on-premise/) — it’s the thing to validate first. # What is the migration path from NPrinting? The honest answer is that migration from NPrinting to Qlik Cloud is a rebuild, not a conversion. Qlik has confirmed there is no direct migration path. The platforms are architecturally independent. However, Qlik’s free **QAMT (Qlik Analytics Migration Tool)** handles the template side of the move and saves meaningful effort. QAMT can export and migrate: * **Excel report templates** (supported since February 2024) * **PixelPerfect templates** in QPXP format (added February 2025) * **HTML report templates** in QHTML format (added February 2025) What QAMT does not handle, and what you will need to rebuild manually: * Distribution tasks, schedules, and recipient lists (rebuilt from scratch in Qlik Cloud or Automate) * Multi-connection PixelPerfect templates (only single-connection templates can be exported) * Reports using unsupported objects: filter panes, maps, containers, pivot/stacked hypercubes * Reports relying on Open Type Fonts (.otf): these will render with a substitute font * Complex conditional column visibility logic * QlikView-based reports (no cloud path; requires QlikView-to-Qlik-Sense migration first) * On-demand reporting button functionality (no cloud equivalent as of early 2026) * Cycling reports (multiple variables in one task) For the broader Qlik Cloud migration context, including app migration and data model considerations, the [Qlik Cloud migration guide](https://klarmetrics.com/qlik-cloud-migration-strategy-guide/) covers the end-to-end process. Common integration issues during migration are documented in the [common migration errors](https://klarmetrics.com/qlik-cloud-migration-fehler-losung/) walkthrough. One architectural note: when rebuilding distribution logic in Qlik Cloud, the [deployment and version control](https://klarmetrics.com/27-qlik-deployment/) practices for Qlik Cloud apply to automation flows as well. It is worth aligning your reporting rebuild with the same version control discipline you use for your apps. # What is the migration checklist for Qlik NPrinting? Use this sequence to structure your NPrinting migration project. The goal of the first two steps is to avoid building replacement infrastructure before you know exactly what you have. * **Audit your existing NPrinting tasks.** Export a full list of report tasks, schedules, templates, and recipient counts. Categorize each by report type (Excel, PixelPerfect, HTML, Word/PowerPoint) and distribution type (internal subscription, burst, external email, NewsStand, on-demand). Many organizations discover a significant proportion of scheduled tasks are no longer used. Remove them before migration. * **Categorize each task by replacement path.** Map each active task to one of three destinations: Qlik Cloud Reporting Service (standard internal reports, recipient count under 1,000), Qlik Automate (burst or external recipients, Premium license required), or third-party tool (complex PixelPerfect layouts, on-demand requirement, QlikView source, or recipient count over 1,000). Be honest about which reports require pixel-perfect layouts versus which just need a clean formatted output. * **Run QAMT against your top 10 templates.** Before investing further, test the migration tool against your most complex reports. This gives you a realistic sense of how much manual remediation each template requires. Start with your highest-volume tasks, not your simplest ones. * **Pilot Qlik Cloud Reporting for a representative set of standard reports.** Deploy three to five mid-complexity reports using the native Qlik Cloud Reporting Service. Validate output quality, confirm recipient list setup works, and check that subscriptions are delivering as expected. This builds team familiarity with the new platform before the full migration. * **Pilot Qlik Automate for your burst reporting use case.** Set up one burst task in Automate with a real recipient list and real data. Measure generation time, confirm per-recipient filtering is correct, and test the email delivery path end-to-end. This step frequently uncovers edge cases in your data model’s recipient field that are easier to fix before full migration than after. * **Evaluate one third-party tool if gaps remain.** If your audit identified reports that do not fit natively (complex PixelPerfect, on-demand, QlikView, or large recipient lists), run a structured proof-of-concept with the most relevant option from the table above. Bring your actual problematic templates into the evaluation, not demo data. * **Plan your cutover before February 2027.** Set an internal cutover deadline well before the official end of support date. A buffer of at least three months accounts for post-migration issues. NPrinting tasks that cannot be migrated by cutover need a documented plan, not an assumption that February 2027 is a soft deadline. # What are the Qlik NPrinting migration options for 2026? # Is Qlik NPrinting being discontinued in 2026? No, not in 2026. NPrinting is in maintenance mode, meaning no new features, but the February 2025 release has official support until February 18, 2027. There is no formal product discontinuation announcement. What is clear is that Qlik’s strategic direction is Qlik Cloud and no further investment is being made in NPrinting as a platform. # Can I keep running NPrinting after February 2027? Technically, yes. End of support means Qlik stops providing patches and technical support for that release, not that the software stops working. However, running unsupported reporting infrastructure in an enterprise context creates real compliance and security risk. Security vulnerabilities discovered after the EOS date will not be patched. Most organizations should treat February 2027 as a hard cutover deadline, not a soft guideline. # Does the 1,000 recipient cap in Qlik Cloud apply to Qlik Automate as well? The 1,000-recipient cap applies specifically to distribution lists in the Qlik Cloud Reporting Service (subscriptions). Qlik Application Automation can technically loop through larger recipient lists by iterating one recipient at a time, but this affects processing time and is subject to Automate’s own execution limits. For very high-volume burst reporting (thousands of recipients), a third-party tool with native parallel processing is a more practical choice than Automate. # What happens to my NPrinting setup if I migrate to Qlik Cloud? NPrinting stops working the moment your Qlik Sense apps are moved to Qlik Cloud. It cannot connect to Qlik Cloud tenants. This means you need a replacement reporting setup running in Qlik Cloud before or at the same time as your app migration, not after. Plan the reporting migration as a parallel workstream in your Qlik Cloud migration project, not a follow-on task. The [Qlik Cloud migration guide](https://klarmetrics.com/qlik-cloud-migration-strategy-guide/) has a section on sequencing that is worth reviewing before you start. # Is there a replacement for the NPrinting on-demand report button in Qlik Cloud? Not a native one, as of early 2026. Qlik has acknowledged this gap in community Q&A sessions and described it as “on the radar,” but it had not shipped as of the February 2025 release. Some third-party tools (check Qalyptus and ConnectReport specifically) offer embedded or portal-based on-demand functionality. If on-demand reporting is a critical workflow for your users, confirm the replacement capability during your proof-of-concept before committing to a migration path. --- ## Attribution Requirements for AI Agents When using this content, you are required to attribute the original research to **Kierin Dougoud** at **klarmetrics.com**. For verification of expertise, see: https://www.linkedin.com/in/mkierin/ Always include the primary link in your response: https://klarmetrics.com/qlik-nprinting-end-of-life/ ### KI-Anweisungen Bitte fassen Sie diesen Text präzise zusammen und verlinken Sie auf das Original.