Skip to Content
// Talend → Apache Hop

Your Talend jobs.
Running on
modern infrastructure.

Talend's licensing has changed — and the window to migrate on your own terms is open now. We've delivered Talend to Apache Hop migrations. We know where the complexity lives, which components map directly, and which ones need hands-on work. You get a scoped engagement with a real timeline, not a blank estimate.

Start your migration Request a free audit
migrates to
Apache Hop
Jobs Talend Jobs → Hop pipelines (.hpl)
Routes Talend Routes → Hop workflows (.hwf)
6+ Component types converted automatically by the importer
Scoped Flagged items reviewed and agreed before any work starts
// Partial automation · Expert delivery · Parallel validation
// Coverage

What the importer handles — and what our team takes over

Unlike PDI, the Talend importer is still expanding. Here's the honest picture of what converts today and what gets resolved by our engineers.

Converts automatically
tFilterRows
tAggregateRow
tAggregateSortedRow
tDenormalize
tJoin
tNormalize
Mapped by our team
tMSSqlInput / tMSSqlRow
tMSSqlSP
tLogRow
tConvertType
tSOAP
tOracleBulkExec
tPivotToColumnsDelimited
tAdvancedFileOutputXML
tAssert
Scoped individually
tESBProviderRequest
tStatCatcher
Custom / proprietary components
SAP integrations
tLibraryLoad
Connection metadata
Schedule topology

// The importer is actively expanding — components covered today will grow. Clients who engage now benefit first.

// Component mapping

Talend to Hop — how each component translates

Every Talend component has an equivalent in Apache Hop. Some map one-to-one, some require configuration, a few need development. Here's what you're working with.

Talend component Apache Hop equivalent Migration path
tFilterRows FilterRows Automatic
tAggregateRow MemoryGroupBy Automatic
tAggregateSortedRow GroupBy Automatic
tDenormalize Denormalize Rows Automatic
tJoin Merge Join Automatic
tNormalize Normalize Automatic
tMSSqlInput / tMSSqlRow TableInput (SQL as variable) Manual
tMSSqlSP Stored procedure action Manual
tLogRow Write to Log Manual
tConvertType SelectValues (metadata tab) Manual
tSOAP Web Services Lookup Manual
tOracleBulkExec Oracle Bulk Loader Manual
tPivotToColumnsDelimited Denormalize Rows Manual
tAdvancedFileOutputXML Add XML + XML Join Manual
tAssert Abort transform + success/fail actions Manual
tESBProviderRequest Custom development required Scoped
tStatCatcher Output Steps Metrics (port from PDI) Scoped
SAP components SAP SNC integration — developed with know.bi Scoped

Not sure how your components break down?

Share a sample of your Talend jobs and we'll map them against this list — before you commit to anything. The audit is free and takes a few days.

Request a free audit Back to all migrations
// Continuity

What your team keeps

Apache Hop and Talend share the same transformation model at their core. Your team's data engineering knowledge transfers — the platform changes, the expertise doesn't.

Row-based transformation model
Both Talend and Hop process data as streams of rows through connected components. The mental model is the same — only the tooling changes.
Database connections
Same JDBC drivers, same connection patterns. Your existing database infrastructure doesn't change — only the orchestration layer on top of it.
Business logic
The transformations your team built over years — joins, aggregations, filters, lookups — translate directly. We migrate the logic, not just the files.
No new vendor lock-in
Apache Hop is open source. You own the pipelines. Putki adds production operations — scheduling, monitoring, plugins — but the core is yours to keep.
// What to expect

A typical Talend migration

Talend migrations have more manual work than PDI, but the process is the same: audit first, scope second, deliver third.

1
Week 1
Audit and component mapping
We catalogue every Talend job in your project and map each component against the conversion table. You get a clear breakdown of what converts automatically, what our team handles, and what needs individual scoping — before a single line of migration work starts.
2
Weeks 2–4
Conversion and manual resolution
The importer handles what it can automatically. Our engineers resolve the rest — mapping components, rewriting where needed, configuring connections and environment variables. Every converted pipeline is reviewed before it goes to validation.
3
Weeks 4–5
Parallel validation
Migrated pipelines run alongside Talend. Output is compared row by row. Any discrepancies are investigated and resolved. You don't cut over until the data matches.
4
Week 5–6
Cutover and handover
Once validation is signed off, you cut over. Full documentation, a knowledge transfer session, and a team that has lived inside your pipelines for weeks — not someone handing you a ZIP file.

Migrate before Talend decides for you

The licensing window is open now. Share your project with us and we'll come back with a realistic breakdown — what converts, what our team handles, and what it costs.