MIGRATION AND MODERNIZATION AT SCALE · DATA INTEGRATION AND PLATFORMS

PowerCenter, SSIS, DataStage or Talend migration.Your data stays.

Jobs, mappings, transformations and orchestration from PowerCenter, DataStage, SSIS, ODI, Talend, dbt, MuleSoft, SAP BW, Databricks, Snowflake or Fabric: we move them to the integration tool you choose, to your data platform or to own code. Same target tables, with parity measured on your real data.

Legacy · Informatica PowerCenterEnd 2027 · SAP BWFewer licences per core and per consumptionParity measured table by table

Request a demo

Automatic demonstration · Tap your tool and see what comes out, where it can go and what stays.

ETL and data integration migration:the clock and the bill

Your data and your target tables are not migrated: they stay. What is migrated is what moves them: jobs, mappings, transformations and orchestration. And here there are real clocks: several integration tools have stopped being sold or have a date.

End of support

Two tools with a date and one that is no longer sold

Informatica PowerCenter is no longer sold and its standard support has ended: the official destination is IDMC, which bills by consumption (IPU). Migrating PowerCenter does not have to mean migrating to IDMC.
SAP BW: end 2027 with ECC. The warehouse goes out; S/4HANA or ECC stay as the source of the data.
SSIS, DataStage, ODI and Talend Studio are still supported, but each version has its date and the vendor pushes you to its cloud: Fabric, Cloud Pak, OCI, Qlik Talend Cloud.

What you pay

Per core, per processor or per consumption

Per-core or per-processor licences for PowerCenter, DataStage and ODI: you pay for the machine, whatever you use.
Consumption: IPU in IDMC, the MuleSoft subscription, the compute of every data platform you have duplicated.
The team that maintains the jobs, with knowledge that lives only in that tool and in one or two people.

What staysand what goes

Your data stays: the source and target databases, the tables, the model. They are the reference for parity: each target table is compared with today’s, row by row, on your real data.

What moves them goes: mappings, workflows, jobs, packages, load plans, routines, surrounding scripts and the orchestration. Nothing from the tool’s repository or server.

We neither implement your data platform nor replace it: Databricks, Snowflake or Fabric are yours and you choose the destination. If you want to unify several into one, that also moves with measured parity.

Where what moves your data ends up:tool, platform or code

Three destinations and you choose. None of them forces you to stay with the same vendor.

Another integration tool

IDMC, Qlik Talend Cloud, MuleSoft or dbt

If you want to stay with a tool: the new one from the same vendor (from PowerCenter to IDMC, from Talend Studio to Qlik Talend Cloud) or someone else’s. The mappings are rewritten in the target tool, with measured parity.

Your data platform

Databricks, Snowflake or Microsoft Fabric

The logic lives where the data is: your platform’s native SQL and orchestration. It is the natural destination for SSIS (Microsoft takes it to Fabric), for SAP BW and for ODI’s CDC. No integration tool licence.

Own code

Java · Spring Batch, .NET or Python, with your orchestrator

No tool licence: Talend jobs are already Java, BW’s ABAP routines and PowerCenter’s shell move to own code, and MuleSoft’s APIs to services of your own. The platform subscription goes away.

How to migrate an integration toolin four steps, table by table

1Repository inventoryWith read-only access: mappings, jobs, packages, parameters, connections, schedules and the surrounding shell or SQL. What runs, what has not run for months and which table each one feeds.
2It stays, it goes or it is switched offEach job with its verdict and its destination. What has not run in months is not migrated: it is switched off. The plan goes by load chain, not by individual job.
3Rebuild with your orchestrated AIDevelopment instances that rewrite, test and document each mapping in the target with the same method. Your team decides and validates.
4Cut-over with measured parityThe two chains run in parallel on your real data and are compared table by table. Each chain is cut over when it matches, not all at once.

The rules

The data and target tables stay
What does not run is not migrated
Chain by chain, no single cut-over
You choose the destination

Tool by tool:what goes out and where it ends up

One summary per tool and platform. In the chart above you have each piece and its path: tap the tool or follow the link.

Legacyno longer sold

Migrating Informatica PowerCenterto IDMC, to your data platform or to own code

Your source and target databases stay. Nothing from the PowerCenter repository and server: its standard support has ended.

What goes out

Mappings, workflows and expressions → IDMC, Informatica’s official destination, or another tool; or native SQL on Databricks, Snowflake or Fabric; or own Java and Python
Surrounding shell and PL/SQL → the target’s orchestration, together with the rest of the chain

See the paths for PowerCenter

Consumption by IPU

Migrating Informatica IDMCstop paying for what moves

Your databases and your SaaS sources stay. What moves is no longer billed by IPU.

What goes out

Mappings and taskflows → another tool, such as Qlik Talend Cloud; or your data platform; or own code

See the paths for IDMC

Per-core licence

Migrating IBM DataStagewithout Information Server

Your source and target databases stay. Nothing from Information Server.

What goes out

Jobs, Transformer and BASIC routines → integration tool, data platform or own code

See the paths for DataStage

SQL Server

Migrating SSISto Fabric or to your data platform

SQL Server stays as a database, if you want to keep it. The packages go out.

What goes out

Packages and expressions → Fabric, where Microsoft takes SSIS, or another platform; or a tool; or own code
T-SQL and procedures → your platform’s SQL; in Fabric Warehouse, almost as they are

See the paths for SSIS

Per-processor licence

Migrating Oracle ODImappings, KMs and CDC out of the licence

Your Oracle databases and the rest of the sources stay. The ODI per-processor licence goes away.

What goes out

Mappings and KMs → integration tool, data platform or own code
CDC and load plans → the target’s native CDC and its orchestrator

See the paths for ODI

End 2027with ECC

Migrating SAP BWthe warehouse goes out, SAP stays as the source

S/4HANA or ECC stay as the source of the data. The BW warehouse goes out to the platform you choose.

What goes out

Models, transformations and loads → Databricks, Snowflake, Fabric or SAP Datasphere; or own code
ABAP routines → own code, with measured parity

See the paths for SAP BW

Studio · licence

Migrating Talendto Qlik Talend Cloud or to own Java

Your databases and your connections stay. The Studio jobs go out.

What goes out

Jobs and Java routines → Qlik Talend Cloud, from the same vendor, or another tool; or your data platform; or own Java, with no Studio and no licence for it

See the paths for Talend

Subscription

Migrating MuleSoftAPIs and flows as own services

The systems it connects stay, each with its APIs. The platform subscription goes away.

What goes out

APIs and integration flows → another integration tool, or own services and APIs

See the paths for MuleSoft

Data platforms

Migrating dbt, Databricks, Snowflake or Fabricunify or change platform

Your tables and your data model move with measured parity. It works to change platform or to unify several into one.

What goes out

dbt models and macros → your platform’s native SQL and orchestrator, or another tool
Notebooks, jobs, SQL, tasks, pipelines and warehouse → another platform, or own code

See the paths for the platforms

Frequently asked questions about Integration and data platforms

Does migrating Informatica PowerCenter force you to go to IDMC?

No. IDMC is Informatica’s official destination and it bills by consumption (IPU), but PowerCenter mappings can also go to another integration tool, to the native SQL and orchestration of Databricks, Snowflake or Fabric, or to own Java and Python. Your source and target databases stay.

Where do SSIS packages get migrated to?

To Fabric, which is where Microsoft takes SSIS, or to another data platform; T-SQL and procedures move to your platform’s SQL, almost as they are in Fabric Warehouse. SQL Server stays as a database if you want to keep it.

What happens to SAP BW when ECC support ends in 2027?

The BW warehouse goes out: models, transformations and loads go to Databricks, Snowflake, Fabric or SAP Datasphere, whichever you choose, and the ABAP routines to own code. S/4HANA or ECC stay as the source of the data.

How do you check that an ETL migration is correct?

The two load chains run in parallel on your real data and each target table is compared with today’s, row by row. Each chain is cut over when it matches, not all at once.

What moves your data today,and what does it cost you every year?

In a demo we show you the whole journey on a sample repository: the job inventory, what stays, what goes, where it ends up and how it is compared table by table. So that you can see what it would look like with yours.

Request a demo See the four scopes

We also migrate: ERP and CRM · Dashboards and analytics · Code and applications · systems migration