One File Action copies, moves or deletes files on S3, Azure Blob, GCS, SFTP or a network share, before the data is processed or after the run succeeds or fails. It names no folder of its own: the input, List Files or File from URL wired to its Files anchor hands it the files.
Job Control
Theirs
Trinium
Notes
ExecuteGraph
No node
A Run pipeline step in a Flow.
Condition
No node
A Flow wire's condition: on success, on failure or on complete. Inside a pipeline, Filter and Route branch on values.
Barrier
No node
A Flow step with several incoming wires waits for all of them.
Loop, Sleep
No node
Not supported: a Flow does not loop and has no wait step.
Subgraph
No node
No reusable part of a pipeline. A shared pipeline run from several Flows, each step handing it its own parameters, covers reuse at the job level.
What does not carry over
Custom Java components and transforms. Trinium has no Java extension point. Put the logic behind an HTTPS endpoint of your own, and API Batch Lookup sends it the rows many at a time.
Message streams and EDI: Kafka, JMS, HL7, EDIFACT and X12 are not read or written.
Loops and waits in a jobflow, and passing a value one step produced to a later step. Hand data between pipelines through a table or a folder.
Fixed-width files and XML output.
Moving a graph
Create a connection for each system the graph reads or writes.
Rebuild the components with the table above. There is no metadata to declare: each node's columns follow from its settings and the node before it.
Rewrite CTL transforms as SQL expressions in Formula, Filter and the other nodes that take a rule.
Press Test for a 50-row sample, deploy to Staging, and compare a full run with the CloverDX output using Data Compare.
Rebuild each jobflow as a Flow, one Run pipeline step per graph.
CloverDX component and job names are as of CloverDX 7.6.1, from CloverDX's public documentation: the component reference, job types, subgraphs and listeners. CloverDX is a trademark of its owner. Trinium is not affiliated with CloverDX.