PowerCenter end of support: moving on without a forced move to the cloud

Informatica PowerCenter 10.5.x reached end of support on 31 March 2026. That is stated on Informatica’s own site, together with the route Informatica offers: modernisation to IDMC, the Informatica cloud platform, with PowerCenter Cloud Edition as an intermediate step. For extended forms of support, Informatica refers to its Product Lifecycle Guide, behind a login. Check there and in your contract what applies to your version.

The direction is clear. New development goes to the cloud, and if you stay on-premises, you pay for a product that no longer grows with you. For organisations that want to keep data integration under their own control, however, the cloud is not the only way forward.

What the end of support means in practice

Your workflows keep running. The risk lies in what changes around them.

Security. Without regular support, no standard patches are released for vulnerabilities in the platform and its bundled components. For a tool with access to your ERP, CRM and data warehouse, that is the most serious risk.

Certification. New versions of databases, operating systems and Java are no longer certified against PowerCenter 10.5. The ETL tool then decides when the rest of your landscape may upgrade.

Skills. PowerCenter specialists become scarcer as the platform ages. You notice it with every vacancy and every replacement.

Audit and compliance. If you fall under NIS2, DORA or an internal IT policy, you have to explain why a business-critical integration tool runs without regular vendor support. Paid extensions solve that for a while, but you are paying to stand still.

Informatica’s own route: fast, but through the cloud

Informatica offers a short path: PowerCenter Cloud Edition. Your existing mappings are imported and run through a Secure Agent without being rebuilt. If you want to stay with Informatica and have no objection to the cloud, this is the fastest way through.

The difference lies in where control sits. Even when processing runs inside your own network through the Secure Agent, management and metadata run through IDMC, the Informatica cloud. Keeping everything under your own control is no longer an option on that route. For organisations with strict requirements on sovereignty or data residency, that is exactly the objection.

Qlik Talend: you choose the deployment model

With Qlik Talend, you choose the deployment model yourself. Qlik puts it this way on its own page for Informatica customers: “Stay on-prem, go hybrid, or head to the clouds.”

On-premises (sovereign). The client-managed edition of Qlik Talend runs fully in your own data centre or with a European cloud provider of your choice. Development, management, scheduling and metadata stay inside your network. According to the Qlik lifecycle page, Talend 8 has no announced end date and receives monthly releases with new features, bug fixes and security fixes.

Hybrid. Management and monitoring in Qlik Talend Cloud, processing on a Remote Engine inside your own network. The data itself does not leave your environment; only metadata and logs go to the cloud, where management runs as a service.

Cloud. Fully in Qlik Talend Cloud, for organisations that do not want to run the infrastructure themselves.

The practical advantage: the jobs you build in Talend Studio are the same in all three models. You can start on-premises and move to hybrid or the cloud later without rebuilding your jobs; only scheduling and deployment are set up again. The choice you make now does not lock you in for good.

What the migration is and is not

Moving from PowerCenter to Talend is a conversion, not an import. Mappings become Talend jobs, workflows and sessions become scheduled tasks. That is more work than an upgrade within the same product, and anyone who promises otherwise has not seen your repository yet.

Carries over well. Standard transformations such as expressions, lookups, filters, joiners, aggregators and routers, plus source and target connections. Conversion tooling is available in the Qlik ecosystem that analyses the repository and converts part of it automatically. How large that part is differs per repository.

Needs manual work. SQL overrides, pre- and post-SQL, stored procedures, complex mapplets and parameter files. Workflow logic and scheduling are also set up again, in Talend Administration Center (on-premises) or Talend Management Console (hybrid and cloud).

Is a chance to clean up. In a ten-year-old PowerCenter repository, some mappings no longer run, or do the same as another one. You do not need to migrate those.

A plan for the move

1. Repository inventory. How many mappings, workflows and sessions are actually active, how complex they are and what depends on what. This sets the scope for everything that follows.
2. Trial conversion on a representative set. Convert ten to twenty mappings that together cover the typical patterns, and measure which share carries over automatically and which needs manual work.
3. Choose the deployment model. On-premises, hybrid or cloud, based on your requirements for sovereignty, operations and cost. This also determines the edition and the infrastructure.
4. Migrate in waves with parallel running. Per business domain, with old and new running side by side for a period and automated validation of the results, so you only switch over once the outcomes match.
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.

One of our manufacturing cases shows that this works for a large landscape: a manufacturer with more than 350 PowerCenter pipelines migrated to Qlik Talend in 14 months, in waves per business domain and without production incidents.

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 best step in every situation.

If you have no objection to the cloud and want to change as little as possible, Informatica’s own route through PowerCenter Cloud Edition is the shortest path. If your organisation relies heavily on other Informatica products, such as MDM or data quality, the decision is wider than the ETL layer. And if you run a limited number of simple pipelines, the native tooling of your data platform may already be enough.

Qlik Talend fits where things are different: hundreds of pipelines, many different sources, a wish to keep data and operations in your own hands, and the freedom to decide later whether and when you move to the cloud.

What cimt does

cimt has delivered more than 70 Talend implementations and guides data migrations from inventory to cutover. For PowerCenter users we offer a migration scan: we analyse your repository, run a trial conversion on a representative set and advise on the deployment model, with a grounded estimate of duration and cost 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].