Informatica PowerCenter End of Support: Your Options and Timeline
The short answer
The deadline has passed, so the clock is now your own
Informatica has stated that PowerCenter 10.5.x reaches end of support on 31 March 2026. That date has passed, and every month since is a month of paying to stay where you are. The date that matters now is your own: when your Informatica support contract renews, or when your extended support ends. Find it this week.
Informatica sells paid extended support beyond end of support, but this only postpones the decision. For the previous release, 10.4, extended support added one year. Salesforce completed its acquisition of Informatica on 18 November 2025. For PowerCenter customers, the question is no longer whether to move but where to, and how fast.
Realistic options are Informatica's own cloud platform, a modular stack on a cloud warehouse with dbt, or a phased mix of both. The best choice is the simplest one that meets your requirements for deployment, latency, governance, cost and skills.
How much time you have
Plan backwards from your own cut-off
Tropos migrations typically take two to six months. That is the working time, and it starts only after you have chosen a target, secured budget and found out what you run. Work backwards from your cut-off and the latest sensible start date arrives sooner than most teams expect.
Waiting also has a price. Add up what you pay each month to stay on PowerCenter: the extended-support premium, the people who keep it running and the infrastructure under it. That is the monthly cost of waiting, and no migration plan reduces it until the work starts.
How late are you?
Five questions tell you quickly.
- Do you know the date your PowerCenter support or maintenance contract ends?
- Do you know how many mappings and workflows you run, and which ones matter?
- Have you chosen a target platform, or at least written down your requirements?
- Do you have people free to run old and new side by side for a period?
- Does someone in the business own the decision, with budget?
If two or more answers are no, start with a conversation before you choose a tool. The next step is to understand what you run and what you need, not to pick a platform.
What end of support means
A business risk, not just an IT one
Without vendor support, three things get harder over time.
Security and compliance. Known vulnerabilities stop being patched, and auditors tend to flag unsupported software.
Operational stability. Pipelines that once worked can break when databases, operating systems or cloud services change around them, and nobody at the vendor will fix it. The result is downtime or wrong numbers in analytics.
Cost. Extended support carries a premium, and ageing infrastructure and the difficulty of finding PowerCenter skills can push running costs up.
PowerCenter was also designed for on-premises, batch-oriented data movement, which limits how quickly your team can respond when the business wants cloud or real-time data. Doing nothing is therefore not a neutral choice.
Support dates are also a compliance topic
For financial entities in scope of DORA, which has applied since 17 January 2025, the technical standard on ICT risk management requires records of the end dates of providers' regular, extended and custom support services for ICT assets, and, for larger entities, the information needed to assess the risk of legacy ICT systems. Organisations covered by the NIS2 Directive must apply measures for security in the maintenance of network and information systems, including vulnerability handling. Whether either applies to you depends on your sector and size, and your compliance team will know. An unsupported integration platform is the kind of asset an auditor may ask about, so it helps to have a dated plan ready.
What the Salesforce acquisition changes
What is confirmed, and what to watch
Salesforce announced the deal on 27 May 2025 at about $8 billion and completed it on 18 November 2025. Salesforce says Informatica will strengthen its Data 360 offering and that MuleSoft will be combined with Informatica's integration and governance capabilities.
What has not been announced is what happens to PowerCenter itself. A sensible planning assumption is that investment will follow the cloud platform. Watch three things: the support and roadmap position for PowerCenter, how licensing is bundled, and how well the combined portfolio fits an environment that is not built around Salesforce.
Your options
Four paths, with their trade-offs
1. Move to Informatica's cloud. Informatica offers several routes: Cloud Data Integration for PowerCenter (CDI-PC) on its Intelligent Data Management Cloud (IDMC), which runs existing workflows without rebuilding mappings, PowerCenter Cloud Edition, and a modernisation route for converting PowerCenter assets to Cloud Data Integration. This gives the most continuity. The trade-off is a SaaS model with consumption-based pricing, which suits some estates better than others.
2. Move to ELT on a cloud warehouse with dbt. Transformation logic becomes SQL in version control, with tests and modular code. This suits teams that want to avoid vendor lock-in and make their pipelines more transparent. The trade-off is that logic has to be rebuilt, and the team needs the skills to run it.
3. Re-architect into modular services. Ingestion, storage, transformation and orchestration are handled by separate tools, for example Fivetran, Snowflake Openflow or Kafka for ingest, Snowflake for storage, dbt for transformation and Airflow for orchestration. This is the most flexible option and the largest design effort.
4. Phase the migration. Whichever target you choose, avoid a single cut-over. Migrate pilot pipelines first, run old and new in parallel and compare results before you retire anything.
How to decide
Five steps, in order
- Inventory what you run. List the mappings, workflows and the systems they touch. Decide what can be retired, what needs a like-for-like replacement and what should be redesigned.
- Write down your requirements. Batch or real time, hybrid or cloud only, governance and residency rules, cost predictability, and the skills you have or plan to build.
- Shortlist against those requirements, not against a favourite tool. Compare total cost of ownership, not just licence price.
- Plan in phases with a parallel run, and set a timeline that leaves margin before any support date you depend on.
- Invest in skills and, where the estate is large, a partner. Moving to SQL-based ELT changes how the team works as much as what it runs.
Automating the dbt route
Where migrations lose time
Most of the effort in a PowerCenter-to-dbt migration goes into three stages: understanding what exists, converting it and proving the new output is right. The Tropos Data Transformation Migrator automates each of them.
- Audit. It scans your legacy pipelines and assesses how much of the migration can be automated.
- Conversion. It converts the logic into dbt projects for Snowflake.
- Validation. It compares the new system's output with the legacy output, and flags and explains differences.
Support for Informatica PowerCenter is currently in private preview. The migrator already supports other legacy sources, including IBM DataStage, SAS Data Integration Studio, Apache Hive and Cloudera Impala.
For example, Sanoma Learning, a leading European education company, engaged Tropos to streamline their data infrastructure and move to a unified dbt-based environment. Tropos first delivered a tailored roadmap for the migration, then used their in-house tool to accelerate conversion of existing code to dbt Cloud, automatically validating that the new system's outputs matched the old. During this process they uncovered and fixed hidden issues in the legacy codebase, improving data quality.
The outcome? A successful migration in a fraction of the time a manual rebuild would take. According to Sanoma's analytics team, “Tropos helped us prioritize improvements effectively and streamline our data processes with a robust dbt project architecture. Thanks to their guidance, we accelerated the migration to dbt Cloud, enhancing our operational efficiency and establishing a stronger foundation for further growth.”
The decision that matters
Treat the deadline as a design decision
A support deadline forces a decision but does not make it for you. The risk is a like-for-like move that recreates the same constraints on a different platform. The better outcome is a deliberate choice about how your data platform should be built from here.
FAQ
When did Informatica PowerCenter support end?
Informatica has stated that PowerCenter 10.5.x reaches end of support on 31 March 2026, a date that has passed. Informatica's product lifecycle guide sets the terms of any paid extended support beyond that date, so confirm your dates with Informatica before you plan around them.
Can we stay on PowerCenter?
You can, with paid extended support where Informatica offers it, but it only postpones the decision and carries a premium. Without support you lose security patches and bug fixes.
How long does a PowerCenter migration take?
Tropos migrations typically take two to six months. Work backwards from your own cut-off date, and allow time to decide and budget before the work begins.
How do we move from PowerCenter to the cloud?
Informatica offers several paths, including CDI-PC on IDMC, PowerCenter Cloud Edition and a conversion service. Other routes include a cloud warehouse with dbt, or a modular stack built from specialist tools.
Can PowerCenter be migrated to dbt automatically?
Tooling can automate the audit, the code conversion and the comparison of old and new output. Tropos supports PowerCenter in its migrator in private preview. Whatever the tooling, validate migrated pipelines by comparing their output with the legacy system before cut-over.