📄️ Assess a Talend project
Run the importer on a copy of your Talend project to see, before any migration work starts, which jobs convert and where the work is.
📄️ Import into a Hop project
Import Talend jobs straight into an existing Apache Hop project, with your own run configurations, and use the generated environments.
📄️ Run the import in CI
Re-run the Talend import automatically and fail the build when a job no longer converts, using the importer's exit codes.
📄️ Port Java components
Finish tJava, tJavaRow and tJavaFlex components after import - what the importer translated, what it left as comments, and where each belongs in Hop.
📄️ Finish connections and passwords
Give the database connections the Talend importer created their values for each environment, add the passwords the export cannot carry, and test them.
📄️ Fix what the import could not convert
The jobs that fail after a Talend import, and the ones that run but write the wrong data - empty strings, connections, operating system commands, custom Java, Talend counters in filters, dynamic child jobs and Dynamic schemas - with the fix for each.
📄️ Troubleshoot
What to do when the Talend importer finds no jobs, a job fails to import, or a converted pipeline does not run.