PowerCenter migration doesn’t force you onto IDMC
By Xavier Franco, CEO de Elternativa · Grupo Zemsania
· 6 min read
Written with the help of AI and reviewed by Xavier Franco

In this article
I come from the catacombs of data. We have spent our lives moving large volumes: first in batch, then the night was no longer enough for everything, then real time arrived. That is why, when a company has to decide what to do with its PowerCenter, I know what we are talking about. And the first answer it usually hears is always the same: «migrate to IDMC». It may be a good option. But it is not the only one.
What Informatica has said
I start with the dates, as the vendor published them. In March 2024, Informatica warned on its blog that general support for PowerCenter 10.4 would end on 31 March 2024. From then on, support became extended, at an additional cost.
It proposed three options: migrate to its cloud platform, IDMC, with the modernization programme and PowerCenter Cloud Edition; pay for a year of extended support; or upgrade to PowerCenter 10.5 to buy time.
In other words: the vendor is clear about the direction, which is its cloud. And it is only natural that it defends it. What I propose is that you make that decision yourself, by comparing.
In practice: check which version of PowerCenter you have and which support plan you are on today. It is the starting point of any conversation with Informatica.
Why it is so hard to move
PowerCenter is usually the invisible heart of a company: thousands of mappings, workflows and sessions that feed the data warehouse, the reports and half the business every night. And it has three ties that make it hard to move:
- The licence, per core or processor, which weighs on you every year.
- The knowledge, which lives in the team that knows the jobs, sometimes in two or three people.
- The fear of breaking something, because data that changes at the source shows up in every downstream report.
With IDMC, moreover, the model becomes consumption-based: Informatica bills it by processing units (IPU). It may work out better or worse depending on your case, but it is best to do the maths before and not after.
In practice: ask your team how many workflows you have and how many have run in the last few months. The difference does not need to be migrated.
Three destinations, and you decide
When we consider migrating PowerCenter, there are three paths, and they are not mutually exclusive:
- Another integration tool. IDMC, Qlik Talend Cloud, MuleSoft or dbt. You stay with a tool, but you choose which.
- Your data platform. Databricks, Snowflake or Microsoft Fabric, with native SQL and orchestration. The logic moves closer to where the data already is.
- Custom code. Java with Spring Batch, .NET or Python, with your own orchestrator. The tool licence disappears.
A mix is the norm. And the mix is decided job by job, not with a single contract for everything.
Escape from everything? No. Stay with whoever adds value. If IDMC is the best option for part of your load, go ahead. If it is not, do not choose it out of inertia.
We know what breaks when it moves
This is the part that matters most to me. Migrating data integration is not translating a mapping from one tool to another. It is guaranteeing that, the next day, every table holds exactly the same data as before.
That is why we do it this way:
- Read-only inventory of the repository: mappings, workflows, sessions, scripts and orchestration.
- Classification of each job: it stays, it goes or it is switched off. What has not run for months is not migrated.
- Rebuild with orchestrated AI, in the destination you choose, validated by your team.
- Cutover with measured parity. The old and the new chain run in parallel and are compared table by table, with real data. Each chain is cut over when it matches.
The source and target databases, the tables and the model stay: they are the reference everything is compared against.
In practice: before accepting any PowerCenter migration plan, ask how the result will be compared table by table. If there is no concrete answer, there is no plan.
The same goes for DataStage, SSIS or SAP BW
PowerCenter is the most visible case, but the pattern repeats. DataStage, SSIS, ODI or Talend are still supported, although each version has its date and each vendor pushes towards its cloud. And SAP BW has its own clock tied to ECC, in 2027. In every case the question is the same: what you have, what is used and where each piece adds the most value.
Use the migration to leave the night behind
Many PowerCenter installations were born to load the data warehouse at night, in batch. Over the years, the volume grew, the night was no longer enough for everything and the business started asking for fresher data. And patches were added along the way: intermediate loads, retries and ever tighter windows.
A migration is the best moment to rethink it. If you are going to rebuild the flows anyway, you can decide, chain by chain, which stay in batch and which move to incremental loads or real time. Today’s data platforms are designed for this, and the cost of doing it during the migration is much lower than doing it afterwards.
Not everything needs real time, mind you. Payroll does not need it; the stock of an online shop perhaps does. The key is to ask the business, not the tool.
And one more thing: if you already have a data platform and it pays off to move to another one, the reasoning is the same. You scan, you move and you operate with a system that speaks its language, comparing table by table.
In practice: mark in your PowerCenter inventory which chains feed same-day decisions. They are the candidates to leave batch.
Where to start
- Take inventory of your PowerCenter: jobs, dependencies and real executions.
- Switch off what does not run.
- Do the maths on the current licence, extended support, IDMC consumption and alternatives.
- Choose one bounded chain and take it to the destination that fits best.
- Compare it table by table in parallel and use that data to decide the rest.
How we help
In Integration and data platform migration we migrate jobs, mappings, transformations and orchestration from PowerCenter, DataStage, SSIS, ODI, Talend, MuleSoft or SAP BW to the destination you choose: another tool, your data platform or custom code. Parity measured table by table, on real data.
We do it with the Datagentis migration module, which connects read-only to Informatica, DataStage, SSIS, ODI, SAP BW or Talend, takes inventory of what you have, flags what is not used and generates the documentation and the plan before anything is moved.
How many of your PowerCenter workflows have run this year?
In a demo, on a sample repository, we show you the inventory, the classification of each job and the table-by-table comparison.


