Query transfer, direct stream and schema transfer have different source, target and type requirements. Preflight must resolve capability before a write is attempted.
Controlled data migration
Move migration work from isolated scripts into persisted, observable run flows.
Connect approved legacy and target Sources, choose an implemented transfer pattern, retain the PipelineRun outcome and add explicit quality checks around the hand-off.
Data Quality can compare counts, required values or referential expectations before a Master flow continues. The QualityRun and PipelineRun preserve separate status and diagnostic meaning.
Job definitions are mutable, saved schedules do not dispatch jobs, and there is no general cancel, retry, rollback or exactly-once contract. The solution is valuable because these boundaries remain visible.
Select the transfer pattern the connectors support.
Query transfer, direct stream and schema transfer have different source, target and type requirements. Preflight must resolve capability before a write is attempted.
Treat validation as a control step.
Data Quality can compare counts, required values or referential expectations before a Master flow continues. The QualityRun and PipelineRun preserve separate status and diagnostic meaning.
Do not promise a workflow engine that is not there.
Job definitions are mutable, saved schedules do not dispatch jobs, and there is no general cancel, retry, rollback or exactly-once contract. The solution is valuable because these boundaries remain visible.
Next step
Start with the flow that cannot afford ambiguity.
Bring the systems, owners, rules, delivery obligations and evidence requirements that matter.
Discuss a critical flow