Talend 7.3 reached end of life on November 30, 2024; paid extended support for it ends in December 2026 [1]. Talend Open Studio was retired on January 31, 2024 [2]. In May 2026 Qlik told customers that Talend Studio's tSAPODPInput and tSAPADSOInput components in RFC mode are affected by SAP Note 3255746 [3][4]. Lima converts Talend jobs in batches: each job becomes a pipeline, tMap becomes a mapping operator, reject flows become exception records with owners, and the SAP components are replaced by released-interface extraction with nothing installed in SAP.
Talend 7.3 jobs keep running after December 2026 without support. Jobs that use the SAP ODP components in RFC mode stop working when SAP's opt-out expires in the same month. Talend 8 has no end-of-life date [1], so the question is where the jobs should live for the next ten years.
The conversion is a mapping, and the mapping is short. What has no equivalent is listed too.
| Today | In Lima | What to know |
|---|---|---|
| Job | Pipeline on the canvas | Components and links carry over as operators and edges. |
| tMap | Mapping operator | Joins, lookups, expressions and rejects in one place, with the reject outputs becoming exception records. |
| tFileInput* / tFileOutput* | File connectors | CSV, JSON, XML, Excel, Parquet; SFTP pick-up with a manifest. |
| tDBInput / tDBOutput (tOracle*, tMSSql*, tPostgresql*) | Database connectors | Partitioned reads, change capture where the database offers it, bulk loads. |
| tSAPODPInput / tSAPADSOInput (RFC mode) | SAP connector: released interfaces | Table reads via a released function module, BAPIs, CDS views, change pointers and extractor delta queues; nothing installed in SAP; no ODP RFC. |
| tSAPBapi | SAP connector: BAPI read and write | Reads and write-back with SAP's response as the confirmation. |
| tAggregateRow, tSortRow, tUniqRow, tFilterRow | Operators of the same kind | One operator each. |
| tJava / tJavaRow / routines | Python operator | Custom logic moves to Python; the inventory lists each routine. |
| Context variables and context groups | Connection registry and pipeline parameters | Environment values live with the connection or the schedule. |
| tRunJob, joblets | Sub-pipelines | Reused once, changed once. |
| TAC / TMC schedules and triggers | Orchestration on Airflow | Schedules, event triggers, dependencies, run windows with deadlines. |
| Reject flows and tDie / tWarn | Exception records and owner routing | Bad rows kept and routed; failures pause the run and its deadline clock. |
The assessment reads exported job definitions from Studio or the management console and needs no access to production data.
| What it reads | What it reports |
|---|---|
| Jobs, joblets, routines | Counts by pattern: copies, tMap-heavy jobs, aggregations, scripts, change capture. |
| Components by family | File, database, SAP, cloud and application components, with the Lima connector for each. |
| SAP ODP components | Every tSAPODPInput and tSAPADSOInput in RFC mode, and the released-interface method that replaces it. |
| Custom code | tJava routines by size, with the Python conversion effort. |
| Effort bands | Per batch of ten to twenty jobs. |
One week. You send the exported jobs; we return the count by pattern, the SAP ODP flags and the effort bands. No charge.
Get the assessment →Fixed priceThe first ten to twenty jobs converted, run side by side, reconciled and cut over on a fixed price; SAP ODP jobs first when the December date matters.
Offers and principles →Your databases, warehouse, files and Qlik analytics stay as they are. Qlik Replicate can keep feeding non-SAP databases while Lima takes the SAP and planning paths.
Talend keeps running the jobs that have not moved; the inventory shows what is left after every batch.
Talend 8 has no end-of-life date [1] and stays on Qlik's capacity meters. Lima's argument is the SAP path with nothing installed in SAP, the planning targets, the return to the ERP, and a price fixed by the tier. The inventory gives you the effort figure to weigh.
The ODP RFC exit kit: the scanner lists the affected jobs; the first ten are converted at a fixed price to released-interface extraction.
No. The mapping operator carries joins, lookups and expressions; the inventory shows which tMaps convert directly and which need review.
One week, no charge. You get the count by pattern, the exposure flags and the effort bands, whatever you decide next.
