Skip to main content

Assess a Talend project

Before you plan a migration, import the whole project once into a scratch folder and read the report. It costs one command, changes nothing in Talend, and tells you where the work is, job by job and component by component.

1. Export the project​

Use the project folder from your Talend workspace (<workspace>/<PROJECT>/), or an export of it (Export items in Talend Studio, all jobs, with dependencies). The importer needs:

  • process/: the jobs and joblets (.item files);
  • context/: the repository context groups;
  • metadata/connections/: the repository connections.

Include every saved version: the importer picks the newest version of each job.

2. Import into a scratch folder​

<hop>/hop-import.sh -t talend -i <project-folder> -o /tmp/talend-assessment

An import never writes into the input folder, and with the default --skip-existing it leaves files that already exist in the output folder alone. Use an empty folder for an assessment.

3. Read the report​

Open /tmp/talend-assessment/talend-migration-report.md, in this order:

  1. Totals: the size of the project, and how much of it was converted with no placeholder (AUTO).
  2. Most frequent source components: what the project is made of. Many tJava or tJavaFlex components mean hand work; many tMap components mean expressions to check.
  3. Needs review: every flagged component with the reason. Group it by reason: the same reason on forty jobs is one decision, made once.
  4. Per job: jobs with nothing flagged can move first; they are also the quickest way to try your validation process.
  5. Jobs that failed to import, at the end, if there are any.

4. Size the work​

For each reason in Needs review, decide who does it and how long one takes, then multiply. Add the work the report does not see: schedules in Talend Administration Center, files and libraries the jobs use at run time, and validation.

Keep the scratch output: the converted jobs with nothing flagged are a good first batch to validate.