Your pipelines.
Better infrastructure.
Minimal rewrite.
Most ETL migrations fail not because of technical complexity, but because teams have to rebuild everything from scratch. We've found a better way — one that preserves what you've built and modernises the infrastructure around it.
Clients migrated from PDI, Talend, and Informatica
Automated converter for Pentaho / PDI pipelines
Open source foundation — no new vendor lock-in
Where are you coming from?
Every migration is different. Some benefit from automation, some need hands-on delivery — most need both. We've done all three, and we scope to what your project actually requires.
From Pentaho PDI
The most direct migration path — Apache Hop was built by the same team that built PDI
Converter available
Automated converter translates your .ktr and .kjb files — most pipelines run without touching a single transform
Apache Hop was created by the original Kettle / PDI engineers — the concepts are identical, the architecture is a decade newer
The converter handles the large majority of standard transforms automatically. Edge cases are flagged and reviewed before delivery
Clients have moved large PDI projects in weeks — not the months a manual rewrite would take
TAL
From Talend
Talend's licensing model has changed. Your migration window is now
Converter in development
We've delivered Talend to Hop migrations — our team knows where the complexity lives
A converter is in development — clients who engage now will be first to benefit when it ships
Until then, we deliver migrations as a scoped professional service — with a real timeline and defined outcomes
Every engagement covers audit, conversion, and parallel validation — so you cut over with confidence
INFO
From Informatica
Enterprise-grade migration — without the enterprise licence cost on the other side
Converter in development
Full audit of existing mappings, sessions, and parameter files before a single line is converted
A converter is in development — clients who engage now will be first to benefit when it ships
Clients have eliminated Informatica licence costs — preserving the logic, not the bill
We handle the hard parts: complex lookups, joiner transformations, session configs, and parameter files
Migration, not reconstruction
The logic you've built over years has value. We translate it — automatically where we can, carefully where we can't — so the result runs better without starting over.
1
Audit
We catalogue every pipeline, connection, and schedule. Complexity is surfaced before scoping — no surprises after the contract is signed.
2
Convert
Automated where tooling exists, manual where it doesn't. Either way, the output is working Apache Hop pipelines — reviewed by the team before handover.
3
Validate
Migrated pipelines run alongside the source system. Row-by-row output comparison means you cut over on evidence, not faith.
4
Cut over
When validation is complete, we cut over. Full documentation, knowledge transfer, and a team that actually knows how the pipelines work.
Things people ask
How much of a PDI project does the converter handle automatically?
The large majority of standard transforms —
Table Input, Table Output, Stream Lookup, Sort Rows, Filter Rows, and most others map directly. Complex steps, custom JavaScript, and legacy plugins are flagged for manual review. You see the flagged list before we start delivery, not after.When will the Talend and Informatica converters be ready?
Both are in active development. We're not publishing a date we can't stand behind. If your migration is in scope now, we can deliver it as a professional service — and apply the converter retroactively once it ships. Clients who engage early also get input into what gets prioritised.
Do we have to use Putki, or can we use open source Apache Hop?
The migrated pipelines run on Apache Hop — open source, yours to keep. Putki layers production operations on top: scheduling, monitoring, CVE patching, and a plugin ecosystem. You decide how much of that you want. There's no minimum.
How long does a migration take?
Honestly, it depends on what you're migrating from and how much of it. A 50–100 pipeline PDI project with the converter typically lands in a few weeks including validation. A large Informatica environment is a longer conversation. We scope after the audit — so the estimate you get is based on what we actually found, not a range designed to cover every eventuality.
What about our existing schedules and orchestration?
Schedules, dependencies, triggers, and error handling all migrate to Apache Hop workflows and the Putki scheduler. The operational behaviour comes with the pipelines — we don't deliver logic that runs but nothing that runs it.
Start with the audit
Tell us what platform you're on and roughly how many pipelines. We'll come back with a realistic scope — what the converter handles, what needs manual work, and what it costs.
Your pipelines.
Better infrastructure.
Minimal rewrite.
Most ETL migrations fail not because of technical complexity, but because teams have to rebuild everything from scratch. We've found a better way — one that preserves what you've built and modernises the infrastructure around it.
Clients migrated from PDI, Talend, and Informatica
Automated converter for Pentaho / PDI pipelines
Open source foundation — no new vendor lock-in
Where are you coming from?
Every migration is different. Some benefit from automation, some need hands-on delivery — most need both. We've done all three, and we scope to what your project actually requires.
From Pentaho PDI
The most direct migration path — Apache Hop was built by the same team that built PDI
Converter available
Automated converter translates your .ktr and .kjb files — most pipelines run without touching a single transform
Apache Hop was created by the original Kettle / PDI engineers — the concepts are identical, the architecture is a decade newer
The converter handles the large majority of standard transforms automatically. Edge cases are flagged and reviewed before delivery
Clients have moved large PDI projects in weeks — not the months a manual rewrite would take
TAL
From Talend
Talend's licensing model has changed. Your migration window is now
Converter in development
We've delivered Talend to Hop migrations — our team knows where the complexity lives
A converter is in development — clients who engage now will be first to benefit when it ships
Until then, we deliver migrations as a scoped professional service — with a real timeline and defined outcomes
Every engagement covers audit, conversion, and parallel validation — so you cut over with confidence
INFO
From Informatica
Enterprise-grade migration — without the enterprise licence cost on the other side
Converter in development
Full audit of existing mappings, sessions, and parameter files before a single line is converted
A converter is in development — clients who engage now will be first to benefit when it ships
Clients have eliminated Informatica licence costs — preserving the logic, not the bill
We handle the hard parts: complex lookups, joiner transformations, session configs, and parameter files
Migration, not reconstruction
The logic you've built over years has value. We translate it — automatically where we can, carefully where we can't — so the result runs better without starting over.
1
Audit
We catalogue every pipeline, connection, and schedule. Complexity is surfaced before scoping — no surprises after the contract is signed.
2
Convert
Automated where tooling exists, manual where it doesn't. Either way, the output is working Apache Hop pipelines — reviewed by the team before handover.
3
Validate
Migrated pipelines run alongside the source system. Row-by-row output comparison means you cut over on evidence, not faith.
4
Cut over
When validation is complete, we cut over. Full documentation, knowledge transfer, and a team that actually knows how the pipelines work.
Things people ask
How much of a PDI project does the converter handle automatically?
The large majority of standard transforms —
Table Input, Table Output, Stream Lookup, Sort Rows, Filter Rows, and most others map directly. Complex steps, custom JavaScript, and legacy plugins are flagged for manual review. You see the flagged list before we start delivery, not after.When will the Talend and Informatica converters be ready?
Both are in active development. We're not publishing a date we can't stand behind. If your migration is in scope now, we can deliver it as a professional service — and apply the converter retroactively once it ships. Clients who engage early also get input into what gets prioritised.
Do we have to use Putki, or can we use open source Apache Hop?
The migrated pipelines run on Apache Hop — open source, yours to keep. Putki layers production operations on top: scheduling, monitoring, CVE patching, and a plugin ecosystem. You decide how much of that you want. There's no minimum.
How long does a migration take?
Honestly, it depends on what you're migrating from and how much of it. A 50–100 pipeline PDI project with the converter typically lands in a few weeks including validation. A large Informatica environment is a longer conversation. We scope after the audit — so the estimate you get is based on what we actually found, not a range designed to cover every eventuality.
What about our existing schedules and orchestration?
Schedules, dependencies, triggers, and error handling all migrate to Apache Hop workflows and the Putki scheduler. The operational behaviour comes with the pipelines — we don't deliver logic that runs but nothing that runs it.
Start with the audit
Tell us what platform you're on and roughly how many pipelines. We'll come back with a realistic scope — what the converter handles, what needs manual work, and what it costs.