Migrations
The importers are about to be released as open source (Apache License 2.0). Until then, we run them for you: contact us.
Technical documentation for moving existing ETL work to Apache Hop with the open-source importers: what they convert, how to run them on your own exports, how to read the migration report, and how to prove a migrated pipeline does what the original did. For data engineers doing a migration or sizing one. Why you might migrate, and how we help, is on putki.io/migrations.
Start here
How the importers work explains what every importer does and does not promise. Read it before you read a migration report.
Contents
- How the importers work: rule-based conversion, the three statuses in the report, placeholders, and why there is no conversion rate.
- Validate a migration: run the original and the Hop version on the same input and compare the output, row by row.
- Talend: jobs, joblets, contexts and repository connections to Hop pipelines, workflows, environments and connections.
- Informatica: PowerCenter mappings and IICS tasks to Hop pipelines.
- SSIS: SQL Server Integration Services packages, project connection managers and project parameters to Hop workflows, pipelines, connections and environments.
How this section is organised
Each importer has the same kinds of page:
| Page | Use it when you want to |
|---|---|
| Overview | Understand what the importer converts, how, and what it leaves to you |
| Get started | Run it for the first time on a public set of jobs and read the result |
| Before and after | See one source job next to the pipeline the importer made from it |
| How-to guides | Do one task on your own exports: assess a project, import into a Hop project, run it in CI |
| Reference | Look up an option, a component or a report section |
Elsewhere
For Apache Hop itself: the concepts explain pipelines, workflows and transforms, and Install Apache Hop gets you a Hop to import into.