Informatica PowerCenter 10.5 left standard support on March 31, 2026 [1]; Informatica itself became part of Salesforce on November 18, 2025 [2]. Estates that run hundreds of PowerCenter mappings have to decide where they go. Lima converts them in batches of ten to twenty: each mapping becomes a pipeline with the same sources and targets, each workflow a schedule, each reject file an exception record with an owner, and every cut-over is proved by a reconciliation of the old and new results.
PowerCenter keeps working after a support date. What changes is that patches, security fixes and help stop unless you pay for extended support, and the people who know the mappings move on. The risk grows one quarter at a time, which is why the conversion runs in batches you can schedule.
The conversion is a mapping, and the mapping is short. What has no equivalent is listed too.
| Today | In Lima | What to know |
|---|---|---|
| Mapping | Pipeline on the canvas | Sources, transformations and targets carry over one for one; the canvas shows the same flow. |
| Workflow and session | Schedule and run | A workflow becomes a scheduled pipeline (or a DAG of several); a session becomes a run with its own report. |
| Source and target definitions | Connections in the registry | Credentials go into the vault once and are referenced, never copied. |
| Expression, Filter, Router, Aggregator, Joiner, Lookup | Operators of the same name | Lookups become cached lookup queries; routers become conditional branches. |
| Update Strategy | Upsert load | Insert, update, delete or reject per row become the upsert load mode plus exception records. |
| Sequence Generator, Normalizer, Rank | Operators | Surrogate keys, unpivoting and ranking have direct operators. |
| Mapplet and reusable transformation | Shared pipeline fragment | Reused once, changed once. |
| Parameter file | Pipeline parameters and connection registry | Environment-specific values live with the connection or the schedule. |
| PowerExchange change capture | Lima change capture | Database log capture for PostgreSQL, MySQL, SQL Server and Oracle; application-layer capture for SAP. |
| SAP PowerConnect / ABAP-generated extraction | Released-interface extraction | Lima reads SAP through table reads via a released function module, BAPIs, CDS views and delta queues, with nothing installed in SAP; ABAP programs generated by PowerCenter are retired. |
| Reject file (bad rows) | Exception records with owners | Bad rows are kept, routed to the person who owns them with a deadline, and replayed once fixed. |
| Repository | Versioned pipeline definitions | Pipelines are versioned with a person and a date per change. |
The assessment reads your repository export (the XML you can produce from the Repository Manager) and needs no access to production data.
| What it reads | What it reports |
|---|---|
| Mappings, mapplets, workflows, sessions | Counts by pattern: copies, lookups and joins, aggregations, update strategies, scripts and stored-procedure calls, change capture. |
| Sources and targets | Systems involved, with the connector Lima uses for each and any prerequisite your administrators need to grant. |
| SAP-specific components | ABAP-generated programs and PowerConnect usage, and the released-interface method that replaces each. |
| Effort bands | Per batch of ten to twenty mappings: simple, standard or complex, with the reason. |
| What has no equivalent | Anything Lima does differently, named, with the recommended handling. |
One week. You send the repository export; we return the count by pattern, the effort bands and the flags. No charge, no obligation.
Get the assessment →Fixed priceThe first ten to twenty mappings converted, run side by side, reconciled and cut over on a fixed price. Your systems integrator can deliver it; so can Lima's team. Later batches are priced the same way.
Offers and principles →Your databases, warehouse and files stay where they are; the pipelines change, the data does not move for the sake of the migration.
Your scheduler stays if you want it to: Control-M or another enterprise scheduler triggers Lima jobs and receives their status.
PowerCenter keeps running the mappings that have not yet moved. The inventory shows what is left after every batch, and the two run side by side until the last cut-over.
No. Batches of ten to twenty mappings, each cut over when it reconciles. PowerCenter runs the rest until then.
They are retired. Lima reads SAP through released interfaces with nothing installed in SAP; the inventory lists each program and the method that replaces it.
Yes. The offer is software with a fixed scope; the delivery can be Lima's team or yours.
One week, no charge. You get the count by pattern, the exposure flags and the effort bands, whatever you decide next.
