Get off Informatica.
Keep everything
you've built.
Informatica licence costs are significant — and they compound every year. Two of our clients have already moved to Apache Hop, preserving the logic their teams built over years while eliminating the recurring bill. We don't do the migration for you. We audit your environment, map the path, and guide your team through every decision so the migration lands right the first time.
We make sure your team can migrate.
The people who know your Informatica environment best are already on your team. Our job is to give them the knowledge, the plan, and the confidence to execute the migration without false starts.
How Informatica concepts map to Apache Hop
Your team will need to know these mappings. This is the reference we work through together during the audit and coaching sessions.
| Informatica | Apache Hop equivalent |
|---|---|
| Mapping | Pipeline (.hpl) — the core unit of transformation logic in Hop |
| Session | Run Pipeline action inside a Hop Workflow — executes a .hpl file with parameters |
| Workflow | Workflow (.hwf) — orchestrates pipelines, handles branching, error paths, and scheduling |
| Source Qualifier | TableInput (SQL-based) or CsvInput / ExcelInput for file sources — one transform per source, no implicit join at read time |
| Lookup | Stream Lookup for in-memory joins on smaller datasets; Database Lookup for row-by-row lookups against a table |
| Joiner | Merge Join — note: unlike Informatica's Joiner, Merge Join requires both input streams to be sorted on the join keys beforehand |
| Aggregator | MemoryGroupBy for unsorted input (holds data in memory); GroupBy for pre-sorted input (lower memory footprint) |
| Expression | ScriptValueMod (JavaScript) for complex logic; Calculator for arithmetic and date operations without scripting |
| Filter | FilterRows — routes rows to a true or false output stream based on a condition |
| Router | Switch / Case — routes rows to named output streams by value; equivalent to Informatica's multi-group Router |
| Sorter | SortRows — configurable memory limit with disk spill; required upstream of Merge Join and GroupBy |
| Update Strategy | No direct equivalent — implemented by routing rows through FilterRows and using TableOutput configured for insert or update, or a combination with Upsert |
| Normalizer | Normalize transform — pivots column values into rows |
| Union | Append Streams for unordered union; Sorted Merge when row order matters |
| Sequence Generator | Add Sequence transform — generates an auto-incrementing integer per row |
| Stored Procedure | Stored Procedure transform — calls a database stored procedure and maps input/output parameters |
| Connected Target | TableOutput, CsvOutput, or any output transform connected inline to the pipeline stream |
| Parameter file / Variables | Hop environment config — project-scoped variables defined per environment (dev, test, prod) |
| Workflow Scheduler | Putki scheduler — triggers workflows on cron, event, or dependency; includes monitoring and alerting |
The audit tells you what you're actually dealing with.
Informatica environments vary enormously. The only way to plan a migration accurately is to look at yours first. We inventory your environment, surface the hard parts, and hand your team a plan they can execute with confidence.
Your team's expertise doesn't start from zero
Informatica and Apache Hop use different paradigms — Informatica's port-and-link mapping model versus Hop's row-streaming pipeline — but the concepts are close enough that experienced Informatica engineers ramp up fast. The vocabulary changes. The thinking doesn't.
How a guided Informatica migration unfolds
Every environment is different — timelines depend on what the audit surfaces. But the structure is consistent across every engagement we've run.
The licence cost isn't going down.
Two clients have already made the move. If you're evaluating your options, the audit is the right first step — it costs nothing and gives your team everything they need to plan the migration properly.
Get off Informatica.
Keep everything
you've built.
Informatica licence costs are significant — and they compound every year. Two of our clients have already moved to Apache Hop, preserving the logic their teams built over years while eliminating the recurring bill. We don't do the migration for you. We audit your environment, map the path, and guide your team through every decision so the migration lands right the first time.
We make sure your team can migrate.
The people who know your Informatica environment best are already on your team. Our job is to give them the knowledge, the plan, and the confidence to execute the migration without false starts.
How Informatica concepts map to Apache Hop
Your team will need to know these mappings. This is the reference we work through together during the audit and coaching sessions.
| Informatica | Apache Hop equivalent |
|---|---|
| Mapping | Pipeline (.hpl) — the core unit of transformation logic in Hop |
| Session | Run Pipeline action inside a Hop Workflow — executes a .hpl file with parameters |
| Workflow | Workflow (.hwf) — orchestrates pipelines, handles branching, error paths, and scheduling |
| Source Qualifier | TableInput (SQL-based) or CsvInput / ExcelInput for file sources — one transform per source, no implicit join at read time |
| Lookup | Stream Lookup for in-memory joins on smaller datasets; Database Lookup for row-by-row lookups against a table |
| Joiner | Merge Join — note: unlike Informatica's Joiner, Merge Join requires both input streams to be sorted on the join keys beforehand |
| Aggregator | MemoryGroupBy for unsorted input (holds data in memory); GroupBy for pre-sorted input (lower memory footprint) |
| Expression | ScriptValueMod (JavaScript) for complex logic; Calculator for arithmetic and date operations without scripting |
| Filter | FilterRows — routes rows to a true or false output stream based on a condition |
| Router | Switch / Case — routes rows to named output streams by value; equivalent to Informatica's multi-group Router |
| Sorter | SortRows — configurable memory limit with disk spill; required upstream of Merge Join and GroupBy |
| Update Strategy | No direct equivalent — implemented by routing rows through FilterRows and using TableOutput configured for insert or update, or a combination with Upsert |
| Normalizer | Normalize transform — pivots column values into rows |
| Union | Append Streams for unordered union; Sorted Merge when row order matters |
| Sequence Generator | Add Sequence transform — generates an auto-incrementing integer per row |
| Stored Procedure | Stored Procedure transform — calls a database stored procedure and maps input/output parameters |
| Connected Target | TableOutput, CsvOutput, or any output transform connected inline to the pipeline stream |
| Parameter file / Variables | Hop environment config — project-scoped variables defined per environment (dev, test, prod) |
| Workflow Scheduler | Putki scheduler — triggers workflows on cron, event, or dependency; includes monitoring and alerting |
The audit tells you what you're actually dealing with.
Informatica environments vary enormously. The only way to plan a migration accurately is to look at yours first. We inventory your environment, surface the hard parts, and hand your team a plan they can execute with confidence.
Your team's expertise doesn't start from zero
Informatica and Apache Hop use different paradigms — Informatica's port-and-link mapping model versus Hop's row-streaming pipeline — but the concepts are close enough that experienced Informatica engineers ramp up fast. The vocabulary changes. The thinking doesn't.
How a guided Informatica migration unfolds
Every environment is different — timelines depend on what the audit surfaces. But the structure is consistent across every engagement we've run.
The licence cost isn't going down.
Two clients have already made the move. If you're evaluating your options, the audit is the right first step — it costs nothing and gives your team everything they need to plan the migration properly.