Move beyond SSIS.
Keep the work
your team built.
SSIS ties your data integration to SQL Server: every server that runs packages needs a SQL Server licence, the tooling lives in Visual Studio on Windows, and moving to the cloud means either Azure-SSIS or a rewrite. Apache Hop runs anywhere — Linux, containers, any cloud — and still talks to every SQL Server database you have. Our converter, soon to be open source, turns your .dtsx packages into Apache Hop workflows and pipelines and reports exactly what needs attention. We audit your packages, 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 SSIS packages 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 SSIS 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. The last column shows what the converter does with each one today.
| SSIS | Apache Hop equivalent | Converter |
|---|---|---|
| Package, Sequence container | Workflow (.hwf) — orchestrates the tasks in the order the precedence constraints set, running independent tasks in parallel as SSIS does | Automatic |
| Data Flow Task | Pipeline (.hpl) — the core unit of transformation logic in Hop, run from the workflow | Automatic |
| Precedence constraints | Hops that follow success, failure or completion; a constraint with an expression is evaluated before the next task runs | Automatic |
| Execute SQL Task | SQL action; a single-row result becomes a query that sets variables. Parameters are substituted as text, so each one is listed for a check | Review |
| Execute Package Task | Workflow action on the child package, with its parameter bindings | Automatic |
| Foreach Loop, For Loop | A pipeline that lists the files, items or query rows and runs the loop body per item; a Repeat action for a For Loop | Review |
| Event handlers (OnPreExecute, OnPostExecute, OnError) | The package or task runs inside a workflow between its handlers, in SSIS's order | Review |
| OLE DB / ADO.NET / ODBC Source and Destination | Table Input and Table Output, with the column mapping | Automatic |
| Flat File and Excel Source / Destination | CSV and text file input and output (delimited or fixed width); Excel input and writer | Automatic |
| Derived Column, Conditional Split | SSIS expressions translated, not copied — NULL handling, casts and date functions keep SSIS's rules | Automatic |
| Lookup | Stream Lookup for a full cache; a per-row database query for partial or no cache, so the database decides what matches, as in SSIS | Automatic |
| Sort, Merge Join, Aggregate, Union All, Multicast | Sort Rows, Merge Join, Memory Group By, and streams that merge or copy rows | Automatic |
| Slowly Changing Dimension | A lookup on the current dimension rows that routes each row to the outputs the SSIS wizard built — your dimension tables stay as they are | Automatic |
| OLE DB Command | A SQL statement run per row, with bound parameters | Automatic |
| Error outputs | Hop error handling on the transform that rejects the row | Review |
| Project parameters, package variables | Hop environment config and workflow parameters — set per environment (dev, test, prod) | Automatic |
| Connection managers | Hop connections, generated from the packages; passwords are never stored in a package, so you add them through environment variables | Review |
| Script Task, Script Component | The C# is kept next to the workflow for reference. Script Components can optionally be translated to Java by a language model while you import, and are always flagged for a person to check | Manual |
| Third-party and rarely used components | A placeholder that keeps the name and the connections in the flow, listed in the report with the settings to redo | Manual |
| SQL Server Agent schedules | Putki scheduler — triggers workflows on cron, event, or dependency; includes monitoring and alerting | Manual |
Send us your packages, get your conversion report.
SSIS estates vary enormously, and a generic conversion rate wouldn't tell you much about yours. For a sense of what the converter does with a real one: Microsoft's own Wide World Importers daily ETL converts with no failed components. Running it in Hop against the sample warehouse that SSIS had loaded, and reprocessing a month of changes, left the four fact tables we could compare identical to what SSIS produced. Your packages will have their own figures. Share your .dtsx files and project. We'll run them through the converter, show you what converted, what's flagged and why, and hand your team a plan they can execute with confidence.
Your team's expertise doesn't start from zero
SSIS and Apache Hop are built on the same ideas — a control flow that orchestrates tasks, and data flows that stream rows through transforms. Experienced SSIS developers ramp up fast. The vocabulary changes. The thinking doesn't.
How a guided SSIS migration unfolds
Every estate is different — timelines depend on what the audit surfaces. But the structure is the same for every engagement.
Your packages don't need a SQL Server licence to run.
If you're weighing up what comes after SSIS, the audit is the right first step — it costs nothing and gives your team everything they need to plan the migration properly.
Move beyond SSIS.
Keep the work
your team built.
SSIS ties your data integration to SQL Server: every server that runs packages needs a SQL Server licence, the tooling lives in Visual Studio on Windows, and moving to the cloud means either Azure-SSIS or a rewrite. Apache Hop runs anywhere — Linux, containers, any cloud — and still talks to every SQL Server database you have. Our converter, soon to be open source, turns your .dtsx packages into Apache Hop workflows and pipelines and reports exactly what needs attention. We audit your packages, 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 SSIS packages 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 SSIS 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. The last column shows what the converter does with each one today.
| SSIS | Apache Hop equivalent | Converter |
|---|---|---|
| Package, Sequence container | Workflow (.hwf) — orchestrates the tasks in the order the precedence constraints set, running independent tasks in parallel as SSIS does | Automatic |
| Data Flow Task | Pipeline (.hpl) — the core unit of transformation logic in Hop, run from the workflow | Automatic |
| Precedence constraints | Hops that follow success, failure or completion; a constraint with an expression is evaluated before the next task runs | Automatic |
| Execute SQL Task | SQL action; a single-row result becomes a query that sets variables. Parameters are substituted as text, so each one is listed for a check | Review |
| Execute Package Task | Workflow action on the child package, with its parameter bindings | Automatic |
| Foreach Loop, For Loop | A pipeline that lists the files, items or query rows and runs the loop body per item; a Repeat action for a For Loop | Review |
| Event handlers (OnPreExecute, OnPostExecute, OnError) | The package or task runs inside a workflow between its handlers, in SSIS's order | Review |
| OLE DB / ADO.NET / ODBC Source and Destination | Table Input and Table Output, with the column mapping | Automatic |
| Flat File and Excel Source / Destination | CSV and text file input and output (delimited or fixed width); Excel input and writer | Automatic |
| Derived Column, Conditional Split | SSIS expressions translated, not copied — NULL handling, casts and date functions keep SSIS's rules | Automatic |
| Lookup | Stream Lookup for a full cache; a per-row database query for partial or no cache, so the database decides what matches, as in SSIS | Automatic |
| Sort, Merge Join, Aggregate, Union All, Multicast | Sort Rows, Merge Join, Memory Group By, and streams that merge or copy rows | Automatic |
| Slowly Changing Dimension | A lookup on the current dimension rows that routes each row to the outputs the SSIS wizard built — your dimension tables stay as they are | Automatic |
| OLE DB Command | A SQL statement run per row, with bound parameters | Automatic |
| Error outputs | Hop error handling on the transform that rejects the row | Review |
| Project parameters, package variables | Hop environment config and workflow parameters — set per environment (dev, test, prod) | Automatic |
| Connection managers | Hop connections, generated from the packages; passwords are never stored in a package, so you add them through environment variables | Review |
| Script Task, Script Component | The C# is kept next to the workflow for reference. Script Components can optionally be translated to Java by a language model while you import, and are always flagged for a person to check | Manual |
| Third-party and rarely used components | A placeholder that keeps the name and the connections in the flow, listed in the report with the settings to redo | Manual |
| SQL Server Agent schedules | Putki scheduler — triggers workflows on cron, event, or dependency; includes monitoring and alerting | Manual |
Send us your packages, get your conversion report.
SSIS estates vary enormously, and a generic conversion rate wouldn't tell you much about yours. For a sense of what the converter does with a real one: Microsoft's own Wide World Importers daily ETL converts with no failed components. Running it in Hop against the sample warehouse that SSIS had loaded, and reprocessing a month of changes, left the four fact tables we could compare identical to what SSIS produced. Your packages will have their own figures. Share your .dtsx files and project. We'll run them through the converter, show you what converted, what's flagged and why, and hand your team a plan they can execute with confidence.
Your team's expertise doesn't start from zero
SSIS and Apache Hop are built on the same ideas — a control flow that orchestrates tasks, and data flows that stream rows through transforms. Experienced SSIS developers ramp up fast. The vocabulary changes. The thinking doesn't.
How a guided SSIS migration unfolds
Every estate is different — timelines depend on what the audit surfaces. But the structure is the same for every engagement.
Your packages don't need a SQL Server licence to run.
If you're weighing up what comes after SSIS, the audit is the right first step — it costs nothing and gives your team everything they need to plan the migration properly.