Jaspersoft ETL without maintenance: moving to Qlik Talend

TIBCO has ended maintenance for Jaspersoft ETL. Jaspersoft ETL is the Talend edition that Jaspersoft, and later TIBCO, sold under its own name (OEM) for years. The end-of-life process covers all editions, including versions 7.3.1 and 8.0.1, and maintenance ran until 20 December 2025, as stated in TIBCO support article KB0137765. You may keep using the version you have until the end of your current contract. No new patches will follow.

Jaspersoft itself has changed hands in the meantime. Cloud Software Group, the parent company of TIBCO, sold Jaspersoft to HCLSoftware, and the product is now part of Actian. If you run Jaspersoft ETL, maintenance is gone, and so is a clear answer to the question of who will support the environment from here.

What the end of maintenance means in practice

Your jobs do not stop. A built Talend job is Java code that keeps running as long as the server underneath it runs. The risk lies in what changes around those jobs.

Security. No patches means vulnerabilities in the tool and its bundled libraries stay open. For an ETL tool with access to your source systems and credentials stored in its connections, this is the most serious risk.

Connectors. Sources and targets keep changing. A new database version, a changed SaaS API or a new JDBC driver: without connector updates, your team absorbs every difference by hand.

Java and the platform underneath. At some point the operating system or the Java version on the server has to move up. A tool without maintenance is not tested for that, and then the old ETL tool sets your upgrade calendar.

Audit and compliance. If you fall under NIS2, DORA or an internal IT policy, you have to explain why a business-critical integration tool has no vendor support. That conversation gets harder every quarter.

Why the move to Qlik Talend is manageable

Jaspersoft ETL is built on Talend Studio. The product followed Talend’s releases. Qlik acquired Talend in 2023 and continues to develop Talend Studio as part of Qlik Talend Cloud.

That means you are not migrating to a different technology. You are moving from a frozen version of Talend Studio to the maintained one. Your developers work in the same environment, with the same components and the same way of modelling. That is a very different project from moving to another ETL platform, where every job is rebuilt.

What carries over and what needs attention

Carries over well. Jobs built from standard components, context variables, metadata connections, schemas and routines. Talend Studio can import jobs and projects from another Studio version and upgrades components automatically where needed.

Needs an upgrade step. If you run the 7.3 line, you first move to Talend 8.0. That step needs a newer Java version and a fresh installation of the runtime. Qlik provides a migration wizard that upgrades projects from an incompatible Studio version and publishes the artifacts to Talend Cloud. Projects on the 8.0 line are closer to the current version.

Needs its own solution. Custom components and community components, which have to be rebuilt or replaced. And the way jobs are scheduled and started today: through cron, a scheduler or a custom script. In Qlik Talend Cloud you schedule and monitor jobs in Talend Management Console. If you want the data processed on-premises, the jobs run on a Remote Engine inside your own network while management sits in the cloud.

Out of scope. If you also use JasperReports Server for reporting, that is separate from this move. The end of maintenance applies to Jaspersoft ETL, not to the reporting product. JasperReports Server has changed owner along with Jaspersoft, though. If you want to reconsider your reporting at the same time, Qlik Sense is a logical candidate: it runs on the same Qlik Cloud platform as Qlik Talend Cloud, so integration and analytics come from one vendor.

A plan for the move

1. Take inventory. How many jobs actually run, which components they use, and which are custom-built or from the community. In practice, some jobs turn out to be unused. You do not need to migrate those.
2. Trial migration on a representative set. Take ten to twenty jobs that together cover the typical patterns, import them into the current Talend Studio and measure what breaks. That gives a reliable estimate for the rest.
3. Choose edition and architecture. Studio jobs run in Qlik Talend Cloud from the Premium edition upwards. You also choose where processing happens: in the cloud, on a Remote Engine inside your own network, or a mix.
4. Migrate in waves and run in parallel. Move jobs per domain and let old and new run side by side for a period, so you can compare results before you switch over.
5. Settle operations and ownership. Who owns which data flow, how it is monitored and who picks up a failure. That belongs to data integration as a discipline, not only to the tool.

When Qlik Talend is not the answer

We are a Qlik Elite Partner, so read this section critically. Even so, Qlik Talend is not the logical successor in every situation.

If you run a handful of simple jobs that only copy data from A to B, a lighter solution or the native tooling of your data platform is often enough. If your whole landscape is moving to one cloud platform, the first question is what that platform already covers. And if a redesign of your data architecture is already planned, this is the moment to do that first.

Qlik Talend fits where the opposite holds: dozens or hundreds of jobs, many different sources, transformation logic you do not want to rebuild and a team that already knows Talend Studio. That is the profile of most Jaspersoft ETL environments we come across.

What cimt does

cimt has delivered more than 70 Talend implementations and guides data migrations from inventory to cutover. For Jaspersoft ETL users we offer a migration scan: we inventory your jobs, run a trial migration on a representative set and give you a grounded estimate of duration and edition choice before you buy a licence. If Qlik Talend turns out not to be the right destination, we say so.

You can request a migration scan through the form on the Qlik Talend Cloud page or directly at [email protected].