Project Name
Migrating PowerCenter 10.5 to IDMC in 2 phases with zero data leaving the bank
The client is a retail bank. Its overnight warehouse loads, regulatory feeds and branch MIS all run on PowerCenter 10.5. Over the years, the estate has grown to several hundred mappings and workflows. The security team does not allow customer data to leave the bank’s network. The bank needed a supported platform quickly, without putting its reporting at risk.
- Platform running out of support: Standard support for PowerCenter 10.5 had ended. After March 2027, even critical fixes will stop.
- No full picture of the estate: Years of growth left unused objects behind. Hidden dependencies on shell scripts were not documented.
- A rewrite could change regulatory figures: A small difference in a converted mapping could shift a reported number without raising any error.
- Data had to stay inside the bank: The security team would not allow customer data to be processed or stored outside the bank’s network.
- Features that do not map one-to-one: Update Strategy logic, mapping variables, worklets, and pmcmd calls all behave differently in CDI.
- No appetite for a one-way cutover: Critical loads needed a tested way back at every step of the programme.
Ksolves designed a two-phase migration to Informatica IDMC. First, every workflow moves unchanged to CDI-PC, a supported release. Then the workloads with the most to gain are converted to native CDI, one wave at a time.
- Cloudify to CDI-PC first: The existing domain is upgraded in place and registered with IDMC. Workflows run unchanged, one environment at a time.
- Repository assessment: Every object is classified by complexity, and unused ones are retired. All pmcmd calls and scripts are listed before conversion starts.
- Parallel run into shadow tables: Converted jobs read the same input as PowerCenter but write to shadow tables. Counts, totals and checksums must match before cutover.
- On-premises Secure Agent group: All processing stays in the bank’s data centre. Agents connect outbound only, and IDMC holds just metadata and job status.
-
Reviewed conversion equivalents: Each PowerCenter feature gets a known CDI equivalent:
- Update Strategy moves to data-driven operations.
- Mapping variables become in-out parameters.
- Worklets become subtaskflows.
- pmcmd calls switch to RunAJob.
- Rollback at every step: Code moves both ways between 10.5.x and CDI-PC. PowerCenter originals stay disabled, not deleted, until each wave is signed off.
Technology Stack
| Category | Technology |
|---|---|
| Platform | Informatica IDMC |
| Platform | CDI-PC |
| Processing | Cloud Data Integration (CDI) |
| Infrastructure | Secure Agent group |
| Integration | RunAJob and pmcmd triggers |
| Compliance | Shadow-table reconciliation |
- 100% of workflows on a supported release (target): Every workflow reaches CDI-PC before any rewrite.
- 0 code changes in phase 1: Existing workflows run unchanged on CDI-PC.
- 0 inbound firewall ports opened: Customer data never leaves the bank’s network.
- 3 environments, each with a tested rollback: Dev, test, and production move one at a time.
- 9 acceptance tests at sign-off: Every converted job is proven against PowerCenter output.
“We reached a supported platform without rewriting a single workflow. Every job we converted after that was proven against PowerCenter before it touched production.”
– Head of Data Platforms, BFSI sector
The bank’s PowerCenter 10.5 estate was running out of support, and a full rewrite was too risky. Ksolves designed a two-phase move to Informatica IDMC. Phase one puts every workflow on a supported release with no code change. Phase two converts selected workloads to native CDI, one proven wave at a time. Customer data stays inside the bank throughout, and every step has a tested way back. The same approach works for PowerCenter estates outside banking.
Is Your Powercenter Estate Ready for March 2027? Plan a Safe Move to IDMC.
