Skip to Content
// PDI → Apache Hop

The converter
that does the
heavy lifting

Most of your PDI pipelines already speak Apache Hop — they just need translating. Our converter turns .ktr and .kjb files into working Hop pipelines and workflows automatically — so your team spends time validating, not rebuilding.

Start your migration Request a free audit
converts to
Apache Hop
.ktr Transformation files → Hop pipelines (.hpl)
.kjb Job files → Hop workflows (.hwf)
~85% Transforms converted automatically on a typical project
Pre-scoped Flagged items reviewed and agreed before any work starts
// Automated conversion · Human review · Parallel validation
// Coverage

What converts automatically — and what doesn't

We don't hide the edge cases. Here's exactly what the converter handles out of the box, and what gets flagged for review.

Converts automatically
Table Input
Table Output
Stream Lookup
Sort Rows
Filter Rows
Select Values
Add Constants
Calculator
String Operations
CSV Input / Output
Execute SQL
Database Join
Flagged for review
Modified JavaScript
Custom plugins
Legacy Kettle steps
Complex Regex transforms
External tool integrations
Non-standard JDBC drivers
Migrated by our team
Flagged items — reviewed and resolved
Connection metadata
Schedule topology
Environment variables
Error handling logic
Documentation
// File mapping

Your files. New format.

The structure of your project maps directly to Apache Hop. Nothing gets lost — it gets translated.

.ktr — Transformation
PDI pipeline logic
.hpl — Pipeline
Hop pipeline
.kjb — Job
PDI orchestration
.hwf — Workflow
Hop workflow
kettle.properties
Environment variables
environment config
Hop environment
Spoon schedules
PDI scheduler
Putki scheduler
With monitoring

Not sure how much of your project converts automatically?

Send us a sample of your pipelines — or the whole project. We'll run the converter, share the flagged list, and give you a realistic scope before you commit to anything.

Request a free audit Back to all migrations
// Continuity

What your team won't have to relearn

Apache Hop was built by the engineers who built PDI. The concepts are identical — the platform is a decade newer.

Transform model
Rows, streams, hops — the mental model is identical. If your team knows PDI, they know Hop.
Database connections
Same JDBC drivers, same connection model. Your existing connections migrate with the project.
Pipeline logic
The business logic your team built over years stays intact. We translate the format, not the intent.
Orchestration patterns
Jobs become workflows. The same dependency patterns, error handling, and branching logic — in a cleaner format.
// What to expect

A typical PDI migration

Timelines vary by project size, but this is how most PDI migrations with the converter unfold.

1
Week 1
Audit and converter run
We catalogue your pipelines and run the converter across the full project. You get a report of what converted cleanly and a list of flagged items with estimated effort to resolve each one.
2
Weeks 2–3
Manual resolution and environment setup
Flagged items are resolved by our team. Connections, environment variables, and schedules are migrated. Your Putki environment is configured and the first pipelines are running.
3
Weeks 3–4
Parallel validation
Migrated pipelines run alongside PDI. Output is compared row by row. Discrepancies are investigated and resolved before any cutover decision is made.
4
Week 4–5
Cutover and handover
Once validation is signed off, you cut over. Your team receives full documentation, a knowledge transfer session, and a clear picture of how every migrated pipeline works.

Ready to run the converter?

Share your project with us — even a sample. We'll show you exactly what converts and what doesn't, before you commit to anything.