PowerCenter to IDMC migration cost: what an Informatica IPU costs at list, what the conversion itself consumes, and the support bill while you decide
9 min read Cost The Adapters team
Field mapping auto-plugged · tap a port to rewire
Plug a source port into
Transform on this cable
JSON in
JSON out
5 sample records ready
A PowerCenter to IDMC migration is billed in Informatica Processing Units, and Informatica publishes no price per IPU on its own site. It does publish one on AWS Marketplace: IDMC at 120 IPUs a month for $131,760 on a 12-month contract, which works out to about $91.50 per IPU-month at list. The conversion is metered against the same pool, per object processed. The rest of the budget is people: rewriting the SQL overrides no converter translates, validating the output, and paying for PowerCenter and IDMC at the same time during the parallel run.
Key takeaways
- One public IPU price exists. Informatica's AWS Marketplace listing: 120 IPUs a month, $131,760 for 12 months, about $91.50 per IPU-month.
- The migration spends your production budget. PC2CDI meters objects processed during assessment and conversion against the same IPU pool.
- Data Integration burns IPUs by compute hour. The meter is Compute Units per hour, converted through a tiered rate card in your contract.
- SQL overrides are the overrun. Informatica's converter leaves embedded SQL for you to rewrite by hand.
- Extended support has no public price. Informatica routes it to a contact address, and says Cloud Edition keeps you on standard support.
How much does it cost to migrate from PowerCenter to IDMC?
There is no fixed price, but there is now a public anchor for the biggest recurring line. IDMC is sold as a pre-paid pool of IPUs that every service draws down, and Informatica's pricing page, read on 18 September 2026, offers a quote form with a sample price range rather than a rate. The migration cost is that subscription, plus the IPUs the conversion consumes, plus the engineering time for everything the converter leaves undone, plus the months where you run both platforms.
Of those four, only the first has a published number, and only through a marketplace. The other three are driven by your repository: how many mappings carry SQL overrides, how many workflows depend on control tasks and parameter files, and how long the business insists on running in parallel before PowerCenter is switched off. That is why two estates with the same number of mappings can differ several times over in total cost.
How much does an Informatica IPU cost?
About $91.50 per IPU-month at list, on the only public price Informatica has put its name to. Its AWS Marketplace listing for Informatica Intelligent Data Management Cloud, sold by Informatica, offers a single bundle of 120 Informatica Processing Units per month at $131,760 for a 12-month contract. That is 1,440 IPU-months, and dividing one by the other is our arithmetic, not Informatica's statement.
Treat it as a ceiling rather than a quote. Enterprise contracts are negotiated, and Informatica's rate cards are tiered so the IPU cost of an hour falls with volume, which means a large commitment is unlikely to look like list. But a published list price is exactly what a finance team needs to sanity check a proposal, and until now most pages on this topic have offered none. The same IPU meter is set beside eight other billing units, from monthly active rows to flat plans, in data integration pricing compared.
What does an IPU actually pay for?
Informatica's documentation defines an IPU as a unit of credit used to pre-pay for IDMC scalars such as Compute Units and Events Processed. Each service has its own scalar, and a rate card turns scalar usage into IPUs. For a PowerCenter estate, the one that matters is Data Integration, which is measured in Compute Units per hour.
| Service | What is counted | Unit |
|---|---|---|
| Data Integration | Compute Units | Per hour |
| Advanced Data Integration | Compute | Per hour |
| Data Integration, change data capture | Rows processed | Per million rows |
| PowerCenter to CDI conversion | Objects processed | Per object assessed and converted |
Rate cards are tiered, so the IPU cost of an hour falls as usage rises. Informatica's documented example, for Application Integration, charges 1.38 IPU per hour in the first tier, 0.17 in the second and 0.043 in the third, and adds that sample rate cards might not match the rates in your organization. The practical estimate is therefore: compute hours of the converted jobs, times your tiered rate, summed per service, times what you pay per IPU. The metering detail per service is in Informatica pricing.
Does the PowerCenter conversion itself consume IPUs?
Yes. Informatica's list of IPU scalars includes Objects Processed, defined as the number of objects processed during assessment and conversion of PowerCenter assets to Cloud Data Integration assets. So PC2CDI is not a free utility bolted onto the subscription. Every assessment run and every conversion run draws from the pool you bought for production.
This changes how to run the project. An assessment repeated on the whole repository every time someone fixes a mapping spends IPUs each time. Scope assessment runs to the folders you are actually working on, and agree with Informatica up front whether migration consumption comes from a separate allocation. The free converters from the warehouse vendors, SnowConvert AI and Lakebridge, do not meter at all, which is a fair point to raise in that negotiation even if you are not leaving.
What are all the costs in a PowerCenter to IDMC migration?
Eight lines. Two are priced by Informatica, one is priced only on request, and the rest are your people or your partner. None of the sizes are printed as percentages, because any split we invented would read as research and would not be.
| Cost line | How it is priced | Unit | What drives it |
|---|---|---|---|
| IDMC subscription | Quote on informatica.com. One public list price on AWS Marketplace | IPUs, pre-paid, drawn down per service | The recurring line. Sized by how many compute hours the converted jobs burn |
| Assessment and conversion | Drawn from the same IPU pool | Objects processed | PC2CDI meters every object it assesses and converts, so reruns cost too |
| CDI-PC, if you bridge first | Drawn from the IPU pool | IPUs per unit, per the metering page | Keeps workloads running unchanged. You still run the servers |
| SQL override rewrites | Your team or a partner | Engineer days | Embedded SQL is not translated. Usually the line that overruns |
| Partner services | Quoted by the partner | Days or fixed scope | Common on large estates. Compare the quote to the assessment's manual count |
| Validation | Cloud Data Validation is in the bundle, the people are not | Engineer days | Row counts and money totals per workflow, against PowerCenter output |
| Parallel run | Both estates at once | Months | PowerCenter servers and support plus the new IPU draw, together |
| Extended support | Not published. Informatica asks you to contact it | Contract | Only if you stay on 10.5.x past 31 March 2026 without Cloud Edition |
The line teams underestimate is SQL overrides. Informatica's asset conversion documentation is explicit that embedded SQL is not translated: you write the converted query into a CONVERTED_SQL column yourself. A repository where most mappings read through a custom source qualifier query is a rewrite project wearing a conversion project's clothes, so count the overrides before you accept any schedule.
What does PowerCenter extended support cost?
Informatica does not publish it. Its download page states that PowerCenter 10.5.x reached end of support on 31 March 2026 and asks customers who need extended support to contact it. Third-party blogs quote end dates for extended and sustaining support, but we could not trace them to Informatica, so do not build a plan on them without the terms in writing.
The alternative Informatica is offering is PowerCenter Cloud Edition. Its webinar pages say that upgrading to Cloud Edition lets you maintain standard support without additional costs, which reframes the decision: the price of staying supported becomes an IPU commitment rather than a support renewal. Whether that is cheaper depends entirely on how many IPUs your workload draws, which is the number to get modeled before you sign.
Is CDI-PC cheaper than converting to Cloud Data Integration?
In the short run, usually, because it skips the conversion. CDI-PC runs existing PowerCenter sessions and workflows in a compatible mode without migrating metadata or business logic, and it is metered in IPUs. But Informatica's documentation describes it as an on-premises domain managed from IDMC, so the servers, the operating system patching and the database underneath all stay yours. You are paying IPUs and still running infrastructure.
That makes CDI-PC a bridge rather than a destination. It is a sensible way to get back onto standard support quickly and convert in stages, and an expensive place to stay. Price it for a fixed number of months, with a conversion plan attached.
Is it cheaper to leave Informatica than to move to IDMC?
The conversion tooling to leave is free. Snowflake's SnowConvert AI reads PowerCenter XML and produces dbt projects, and Databricks' Lakebridge is open source and produces PySpark and Spark SQL. But Snowflake labels its Informatica support as preview, Lakebridge carries no formal support SLA, and both leave you paying the target platform's compute for every job that used to run on a PowerCenter server you already owned. The honest comparison is IPUs against warehouse compute plus the tools around it, not IPUs against zero.
What usually tips the math is the shape of the repository. Heavy transformation mappings belong in the warehouse and convert reasonably well there. The long tail of jobs that only copy records between an application and a database do not need a converter or an IPU pool at all, and they are the cheapest part of the estate to move onto a flat-priced sync. Once the new pipelines are live, track what they cost month to month with a cloud cost management tool that reads your cloud and SaaS spend, because a consumption meter that nobody watches is how a migration saving quietly disappears in the second year. The full list of routes off PowerCenter, and what each one outputs, is on PowerCenter migration tools.
How do you estimate a PowerCenter migration budget?
Start from the assessment, not the mapping count. Run PC2CDI's repository assessment, which grades every asset as automated, partial or manual, and count the partial and manual items by type. Then list every SQL override, parameter file and workflow control task separately, because those are the pieces every converter handles worst.
Price the IPU line from compute hours, using the $91.50 per IPU-month list figure as the ceiling until you have a quote. Add the conversion IPUs, engineer days for the manual items and overrides, validation per workflow, and the parallel run in months. Then split out the workflows that only move data between applications and databases, and price those on a flat monthly plan instead, because they are the part of the estate where a metered platform is least justified.
Where this leaves you
The March 2026 support date turned PowerCenter into a pricing decision. Staying supported now means either an extended support contract Informatica prices only on request, or an IPU commitment through Cloud Edition, and there is finally a public list price to measure that commitment against. Get the assessment run, count what does not convert, and move the simple jobs somewhere they do not burn IPUs at all. For the ongoing cost of the platform you land on, what data integration really costs covers the budget after the migration ends.
Move the PowerCenter jobs that only copy data, and stop paying IPUs for them
Map the fields once, backfill, then run incrementally with retries, alerts and per-record logs. From $49 a month, flat, with nothing metered.
The live demo needs no card, and Starter is $49 a month.