PowerCenter migration tools and Informatica PowerCenter alternatives after end of support
Standard support for PowerCenter 10.5.x ended on 31 March 2026. Nine ways off it, lined up by what each one reads, what it writes out and how it bills, including the one public price anyone has for an Informatica IPU and the parts of a PowerCenter repository no converter translates.
The live demo needs no card, and Starter is $49 a month.
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
Vendor documentation read 18 September 2026
Which PowerCenter migration tool should you use?
It depends where the jobs are going. Staying with Informatica means PowerCenter Cloud Edition: CDI-PC to keep workloads running unchanged, PC2CDI to convert them into Cloud Data Integration, both billed in IPUs. Moving the logic into Snowflake means SnowConvert AI, which is free and writes dbt, though its Informatica support is still preview. Moving into Databricks means Lakebridge, free and open source, writing PySpark. And the simple jobs that only copy data between applications and databases are cheaper to rebuild on a sync platform than to convert at all.
The correction worth making early: PowerCenter is not switching off. Informatica still ships 10.5.x maintenance releases, with 10.5.11 released in August 2026. What ended is standard support, which is a contract and risk problem rather than a software outage, and it means you have time to split the repository sensibly instead of converting everything in a panic. For the wider category see data migration tools, and for what the platforms you might land on actually charge, data integration pricing compared.
PowerCenter end of support: what Informatica has actually published
Most pages on this topic repeat each other's dates. These are the ones we could trace to a primary source on 18 September 2026, and the one widely quoted row we could not.
| Item | Status | Source |
|---|---|---|
| PowerCenter 10.5.x standard support | Ended 31 March 2026 | Informatica download page |
| PowerCenter 10.4 standard support | Ended 31 March 2024 | Informatica customer alert blog |
| Latest PowerCenter release | 10.5.11, released August 2026 | Informatica documentation portal |
| PowerCenter 10.6 | No documentation exists for it | Informatica documentation portal |
| Extended and sustaining support end dates | Not published by Informatica. Ask your account team | Third-party blogs only |
| PowerCenter Cloud Edition | Generally available since 19 September 2023 | Informatica press release |
| Informatica ownership | Salesforce, acquisition completed 18 November 2025 | Salesforce press release |
The extended support row matters most for planning. Dates of March 2027 for extended support and 2029 for sustaining support appear on several vendor and partner blogs, none of which cites where they came from, and Informatica's own download page simply asks customers who need extended support to get in touch. If your migration timeline assumes a date, get that date into the renewal paperwork. Informatica also states on its webinar pages that upgrading to PowerCenter Cloud Edition keeps customers on standard support without additional cost, which is the lever it is using to move the installed base.
PowerCenter migration tools compared
What each tool reads, what it produces and how it bills. The output column is the one that decides the shortlist, because it tells you which platform you are really choosing.
| Tool | Owner | What it does | Produces | Pricing | Watch out for |
|---|---|---|---|---|---|
| CDI-PC | Informatica | Runs existing PowerCenter sessions and workflows in a compatible mode, managed from IDMC. Nothing is converted | Your PowerCenter assets, unchanged | IPU consumption | The domain and data still run on your servers. It buys support time, not modernization |
| PC2CDI | Informatica | Assesses the repository, then converts mappings, mapplets, sessions and workflows to Cloud Data Integration | CDI mappings, mapping tasks and taskflows | IPUs, metered per object assessed and converted | Embedded SQL is not translated. You type the rewritten query into a CONVERTED_SQL column |
| SnowConvert AI | Snowflake | Reads PowerCenter XML exports and rebuilds the logic for Snowflake | dbt projects plus Snowflake task graphs | Free | Informatica support is preview, and each export file must hold exactly one workflow |
| Lakebridge | Databricks, open source | BladeBridge converter inside a free migration toolkit, plus an experimental LLM route | Notebooks with PySpark and Spark SQL | Free | No formal support SLA, and the public docs do not yet list Informatica as a source |
| Maia migration agent | Matillion | AI agent that reads 14 source platforms including PowerCenter | Matillion pipelines on Snowflake, Databricks or Redshift | Not published | Public preview since 26 March 2026 |
| AWS SCT | Amazon Web Services | Converts the SQL embedded in Informatica XML and redirects connections to the new database | Informatica XML again, pointed at the new target | No license charge | It keeps you on Informatica. Rebuilding on Glue is sold by partners, not AWS |
| Qlik Talend | Qlik | Informatica migration program with automated conversion tooling, delivered with partners | Qlik Talend Cloud jobs | Capacity subscription, quoted | The tool is not named or priced publicly. Ask who does the conversion |
| Microsoft, Google | Microsoft, Google Cloud | No first-party PowerCenter converter found for Data Factory, Fabric or BigQuery | Partner-built pipelines | Partner services | Fabric Migration Assistant covers SQL warehouses, not Informatica mappings |
| Adapters | Adapters | Field-level mapping between apps, databases and warehouses, scheduled with retries and per-record logs | Running syncs, rebuilt rather than converted | Flat monthly price, not metered | We do not read PowerCenter XML. Use us for the app and database syncs, not heavy transforms |
Two of these are commonly misread. AWS Schema Conversion Tool does read Informatica XML, but what it does is translate the SQL inside it for a new database and write Informatica XML back out, so you stay on Informatica. And CDI-PC is sometimes described as a migration when it is closer to a support bridge: Informatica's documentation describes an on-premises domain, with sessions and workflows still running in it, managed from the cloud. The detail on SnowConvert and the Snowflake route is on Snowflake ETL tools.
What no PowerCenter converter translates for you
Informatica does not publish a list of transformations PC2CDI cannot convert. It sends each customer an assessment report instead, grading every workflow, session, mapping, mapplet and worklet as automated, partial or manual, where manual means it might need redesign because there is no direct support. Snowflake is more specific about SnowConvert AI. Read together, the documentation points to the same hard parts.
SQL overrides
PC2CDI does not translate embedded SQL. You enter the rewritten query yourself in a CONVERTED_SQL column. AWS SCT exists largely to do this one job for a new database.
Parameter files
Converted by a separate parameter file conversion task in PC2CDI, not by the main asset conversion. Easy to miss until the first converted run picks up the wrong connection.
Workflow control tasks
SnowConvert AI lists the Command, Control, Event Wait and Timer workflow tasks as not yet supported. These carry the scheduling glue that makes a nightly run behave.
Unusual source qualifiers
XML, Application and App Multi-Group Source Qualifiers are on SnowConvert's unsupported list, along with Salesforce Lookup.
Transaction control
Transaction Control and SQL Transform are both listed as not yet supported by SnowConvert AI. Mappings that commit mid-stream need their semantics redesigned for the warehouse.
Multi-workflow exports
SnowConvert AI expects exactly one workflow per XML file. A single repository export of everything has to be split first.
The pattern is consistent. The data flow logic in a mapping converts reasonably well, and the things around it do not: SQL typed into overrides, the scheduling and control tasks between sessions, and the parameters that tell each run where to connect. Budget the migration by counting those, not by counting mappings.
Six automation numbers for the same migration
Every figure below is quoted from the vendor's own page. They are not wrong, they measure different things, and none of them is a measurement of your repository.
| Source | What it says | How to read it |
|---|---|---|
| Informatica landing page | Reuse up to 100% of PowerCenter assets | Upper bound, marketing copy |
| Informatica press release, 2023 | 95% AI-driven automation for PC2CDI | Launch claim for the converter |
| Informatica documentation | Automates more than 90% of the migration process | The figure the docs stand behind |
| Informatica customer stories | BMC 99% of assets, Marathon Oil up to 70% | Real range across two customers |
| Databricks, Lakebridge launch | Automates up to 80% of migration tasks | Upper bound across all sources, not Informatica specifically |
| Snowflake documentation | Informatica PowerCenter migration is in preview | No percentage offered at all |
The most useful row is the pair of customer stories on Informatica's own page: 99 percent of assets at one company and up to 70 percent at another, from the same converter. That spread is what repository variety does to an automation rate. Your number sits somewhere in it, and the assessment report is the only way to find out where. The same problem shows up on Oracle to PostgreSQL migration tools, where AWS rates each feature area separately rather than quoting one percentage.
The numbers that decide the plan
$91.50
Per IPU-month at list: 120 IPUs a month for $131,760 on a 12-month contract, Informatica's own AWS Marketplace listing
AWS Marketplace, read 18 Sep 2026
31 Mar 2026
End of support for PowerCenter 10.5.x, per Informatica
Informatica, read 18 Sep 2026
10.5.11
Latest PowerCenter release, August 2026. Maintenance continues after the support date
Informatica docs, read 18 Sep 2026
1
Workflows per XML export file that SnowConvert AI accepts
Snowflake docs, read 18 Sep 2026
3
Buckets the PC2CDI assessment sorts assets into: automated, partial and manual
Informatica docs, read 18 Sep 2026
$8B
Approximate equity value of the Salesforce acquisition of Informatica, completed 18 November 2025
Salesforce, read 18 Sep 2026
The first card is the one to take into a budget meeting. Informatica's own site offers only a quote form, but Informatica lists IDMC on AWS Marketplace as one bundle of 120 Informatica Processing Units a month for $131,760 on a 12-month contract. That is 1,440 IPU-months, or about $91.50 per IPU-month at list. Negotiated contracts will differ, and what one IPU buys depends on the service's rate card, but it is the only published anchor there is. The full breakdown of how IPUs are metered, and what the conversion itself consumes, is in PowerCenter to IDMC migration cost.
How to migrate off PowerCenter in six steps
-
01
Inventory what PowerCenter actually runs
Export the repository and count workflows, sessions, mappings and mapplets, then split them by what they do. In most estates a large share of the workflows are plain movement: an application table copied to a database, a nightly extract to the warehouse, a file picked up and loaded. Those do not need a converter. They need a sync. The heavy transformation logic is usually a minority, and it is where the conversion tools earn their keep.
-
02
Run the assessment before you pick a target
PC2CDI grades every asset as automated, partial or manual, and SnowConvert AI produces its own report of what it will not translate. Run both against the same export if the target is still open. The count of manual items per tool is the project estimate, and it is far more predictive than any vendor's headline automation percentage.
-
03
Decide whether you are buying time or leaving
CDI-PC keeps the existing workloads running under cloud management with no conversion, and Informatica says Cloud Edition keeps you on standard support. That is a sensible bridge if the deadline is the problem. It is not a migration, because the domain and the data still run on your infrastructure, so decide explicitly whether it is the destination or the waiting room.
-
04
Rewrite the SQL overrides by hand
Every converter struggles with SQL embedded inside mappings. PC2CDI leaves it to you in a CONVERTED_SQL column, and AWS SCT exists largely to handle that one piece. Pull every SQL override, lookup override and pre or post session command into a list early, because this is the work that turns a three-month plan into nine.
-
05
Rebuild the simple movement jobs, do not convert them
A converted mapping carries twenty years of workarounds with it. A job that copies orders from an application into a database can be rebuilt in an afternoon on a modern sync tool, with incremental loads and retries built in, and it will be easier to own afterward than a faithful translation of the original.
-
06
Validate on totals, then run in parallel
Compare row counts per target table and sum every money and quantity column to the cent, for each converted workflow, against the PowerCenter output from the same input. Informatica bundles Cloud Data Validation for this. Run both systems in parallel for at least one full business cycle, month-end included, before switching PowerCenter off.
Who is moving off PowerCenter, and why
Past the March 2026 support date
The commonest reason this page gets read. Standard support for 10.5.x ended on 31 March 2026, and an unsupported ETL server in a regulated estate is an audit finding waiting to happen. The decision in front of you is whether to renew into extended support while you migrate, or move now.
Consolidating onto the warehouse
The warehouse already runs the transformations as SQL. Converting PowerCenter mappings into dbt on Snowflake or Spark on Databricks puts the logic where the compute already is, and removes a separate ETL server from the estate.
Staying with Informatica, moving to the cloud
A perfectly reasonable choice for estates that also use Informatica data quality, catalog or MDM. PowerCenter Cloud Edition is built for exactly this, and the cost question becomes how many IPUs the converted workload burns per month.
Retiring the app-to-database syncs
Many PowerCenter repositories are full of simple jobs that copy data between business applications and databases. Those move to a flat-priced integration platform faster than they convert, and cost less to run.
Reacting to the ownership change
Informatica is now part of Salesforce. Some buyers see that as stability, others as a reason to reassess concentration risk. Either way it is a legitimate trigger to put the platform decision back on the table before a multi-year IPU commitment.
Escaping a hardware refresh
The PowerCenter servers are due for replacement and nobody wants to buy hardware for software that is past standard support. A migration timed against the refresh avoids paying for both.
The fourth case is the one most migration plans overlook. A PowerCenter repository built up over fifteen years usually holds a long tail of jobs that do nothing a modern sync tool cannot do out of the box, and converting them faithfully preserves every workaround they ever needed. Rebuilding them on a flat-priced platform is faster and leaves the converter budget for the mappings that deserve it. If Informatica is on your list for the replacement too, the trade-offs are on our Informatica alternative page, and the IDMC meter is explained in Informatica pricing.
Where Adapters is the wrong choice
We are a sync platform, not a PowerCenter converter. That makes us a good home for part of a PowerCenter estate and the wrong tool for the rest of it.
- We do not read PowerCenter XML and we do not convert mappings. If the value is in thousands of transformation-heavy mappings, you want SnowConvert AI, Lakebridge, PC2CDI or a partner, not us.
- We are not a transformation engine for heavy multi-step logic. If a mapping does complex joins, aggregations and routing, that logic belongs in the warehouse as dbt or Spark, not in a sync tool.
- If you also run Informatica data quality, catalog or MDM, staying inside IDMC can be the honest answer. Moving only the integration layer off Informatica saves less than it appears to.
- We do not provide vendor-attested lineage for auditors. Regulated programs that need that evidence should weigh Informatica's governance tooling seriously.
- For an estate that will be gone within months, a short extended-support renewal plus a converter can cost less than any new subscription, including ours.
Four questions to ask any PowerCenter migration vendor
Ask for the manual count from your own repository
Not the headline percentage. Every vendor quotes an upper bound, and the six figures in the table above range from preview with no number to up to 100 percent. The only number that estimates your project is the count of assets graded partial or manual in an assessment of your export.
Ask how the conversion itself is billed
PC2CDI meters objects processed during assessment and conversion against your IPU pool, so the migration spends from the same balance as production. SnowConvert AI and Lakebridge are free. Know which one you are signing up for before the assessment runs.
Ask what happens to SQL overrides
This is the single most useful question, because it is the part every tool handles worst. If the answer is not specific, assume every override is a hand rewrite and count them.
Ask for extended support terms in writing
Informatica publishes the 10.5.x end-of-support date and routes extended support to a contact address. The end dates quoted on third-party blogs are not on Informatica's pages, so a plan that depends on them needs them in the contract.
Related migration and pricing guides
PowerCenter to IDMC migration cost
The one public IPU price, what the conversion consumes, and the support bill while you decide.
Data migration tools
The pillar above this page: twelve tools, type mapping traps and cutover methods.
Data integration pricing
Nine platforms by billing unit, including the IPU, and one job priced under each rule.
Informatica pricing
How IDMC meters IPUs per service, and the rate card tiers Informatica documents.
Oracle to Snowflake migration tools
The source most PowerCenter jobs read from, moved into the warehouse they now feed.
Talend alternative
The other legacy ETL suite buyers weigh when leaving PowerCenter.
Questions buyers ask about PowerCenter migration
- When is PowerCenter end of support?
- Informatica states that PowerCenter 10.5.x reached end of support on 31 March 2026, and directs customers who need extended support to contact it. PowerCenter 10.4 ended standard support two years earlier, on 31 March 2024. Later end dates for extended and sustaining support circulate on third-party blogs, but we could not find Informatica publishing them, so get them in writing from your account team.
- Is Informatica PowerCenter being discontinued?
- Not in the sense of the software disappearing. Informatica still ships 10.5.x maintenance releases, and its documentation portal lists 10.5.11 as released in August 2026. What changed is standard support for 10.5.x, which ended on 31 March 2026. There is no 10.6 documentation, and Informatica's own path forward for PowerCenter customers is PowerCenter Cloud Edition inside IDMC.
- What is replacing Informatica PowerCenter?
- Inside Informatica, Cloud Data Integration in IDMC, reached through PowerCenter Cloud Edition. That bundle has three parts: CDI-PC, which runs existing PowerCenter workloads in a compatible mode without converting them, PC2CDI, which converts mappings and workflows into Cloud Data Integration assets, and Cloud Data Validation. Outside Informatica, the replacement is whichever warehouse or pipeline platform the converted jobs land on.
- What are the alternatives to Informatica PowerCenter?
- The realistic ones are the platforms with a converter that reads PowerCenter exports: Snowflake SnowConvert AI, which is free and outputs dbt projects, Databricks Lakebridge, which is open source and outputs PySpark and Spark SQL, and Matillion's Maia migration agent, in preview. Qlik Talend and the AWS Glue partners offer conversion as a service. For the app and database syncs PowerCenter also ran, a flat-priced integration platform is the cheaper home.
- How do I migrate from PowerCenter to IICS?
- Run the repository assessment first. PC2CDI sorts every asset into automated, partial and manual, and that report is your project plan. Then convert mappings, mapplets, sessions and workflows into Cloud Data Integration mappings, mapping tasks and taskflows, run a separate parameter file conversion task, and rewrite embedded SQL by hand in the CONVERTED_SQL column. Validate with Cloud Data Validation before cutover.
- What is PowerCenter Cloud Edition?
- Informatica's modernization bundle for PowerCenter customers, generally available since 19 September 2023. It packages CDI-PC for running PowerCenter workloads unchanged under cloud management, PC2CDI for converting them to native Cloud Data Integration, and Cloud Data Validation for testing the result. It is priced on Informatica's IPU consumption model, and Informatica says upgrading to it keeps you on standard support.
- How much does it cost to migrate from PowerCenter to IDMC?
- Informatica prices IDMC in IPUs and publishes no price per IPU on its own site. Its AWS Marketplace listing is the one public figure: 120 IPUs a month for $131,760 on a 12-month contract, about $91.50 per IPU-month at list. The conversion also consumes IPUs, because PC2CDI meters every object it assesses and converts. Add partner services and the parallel run.
- Can PowerCenter mappings be converted to Snowflake automatically?
- Partly. Snowflake SnowConvert AI reads PowerCenter XML exports and generates dbt projects and Snowflake task graphs, but Snowflake labels Informatica PowerCenter migration as preview, requires exactly one workflow per export file, and lists unsupported pieces including SQL Transform, Transaction Control, XML source qualifiers, Salesforce Lookup, and the Command, Control, Event Wait and Timer workflow tasks.
- Can PowerCenter be migrated to Databricks?
- Yes, through Lakebridge, the free open-source migration toolkit Databricks launched in June 2025 after acquiring BladeBridge. Its changelog records conversion of Informatica PowerCenter into notebooks with PySpark and Spark SQL, and an experimental LLM-based route into Lakeflow pipelines. Two caveats: the public transpile documentation still lists only DataStage and SSIS as ETL sources, and the project carries no formal support SLA.
- Is Informatica owned by Salesforce?
- Yes. Salesforce announced the acquisition on 27 May 2025 at about $8 billion in equity value, $25 a share in cash, and completed it on 18 November 2025, when Informatica was delisted from the NYSE. Salesforce said it would support Informatica across any cloud, hybrid or multi-cloud environment. We found no public statement since then specific to the PowerCenter roadmap.
Rebuild the PowerCenter jobs that only move data, on a price that never meters
Map the fields once, backfill, then run incrementally with retries, alerts and per-record logs. From $49 a month, no IPUs, no rows counted.
The live demo needs no card, and Starter is $49 a month.