If you run Informatica PowerCenter on premises, support deadlines are now driving real cost and risk decisions. Many UK data managers are being asked to pay more simply to keep the lights on, while their organisations still carry the operational and security burden of an ageing platform.
This is why modernisation should be treated as a strategic programme, not a last minute upgrade.
What is happening with PowerCenter support
Informatica states that PowerCenter 10.4 support ended on March 31 2024 and that customers should migrate now. Their guidance presents three paths: modernise to IDMC, purchase Extended Support, or upgrade to PowerCenter 10.5.
The cost impact is significant. Extended Support is positioned as a premium option. Many organisations also report uplift pricing versus standard support, often quoted as significant, with the underlying message consistent: it costs more to stand still.
For PowerCenter 10.5, March 31 2026 is a major transition date for standard support, making now the right time to plan a controlled move away from on premises dependency.
When a platform moves beyond standard support, data teams often face:
- Security and patching risk
- Reduced vendor safety net when defects appear
- Harder audit conversations around unsupported or extended support estate
- Rising run costs at a time when budgets are under pressure
- Programme risk if a migration is left too late and becomes deadline driven
Teams also have constraints that are easy to underestimate: data residency, supplier assurance, operational resilience, segregation of duties, and change control. A rushed modernisation almost always creates avoidable risk.
Modernisation is more than a tool swap
A successful programme does not start with choosing a replacement product. It starts with clarity:
- Which version are we on, and what deadlines apply
- What integrations are truly business critical
- What is the right target architecture for our security model
- How do we migrate in waves without disrupting service
The goal is to modernise the operating model as well as the technology. That usually means improving observability, automating testing, enabling repeatable deployment, and designing for resilience and cost control.
A pragmatic migration approach that reduces risk
At Agile, we deliver cloud modernisation programmes that are designed to be calm, governed, and measurable. A typical approach looks like this:
- Discovery and risk triage: Map integrations, dependencies, schedules, and business criticality. Identify quick wins and high risk pipelines.
- Target architecture and roadmap: Cloud or hybrid design aligned to your governance and compliance, including data residency and resilience controls.
- Migration factory: Wave based delivery with repeatable patterns, automated testing, parallel run, and controlled cutover.
- Optimisation and handover: Performance tuning, cost management, operational runbooks, and team enablement.
This structure avoids the common trap: spending months debating tooling while the deadline gets closer.
FAQ: What is the difference between End of Support & Extended Support for MDM?