What changes for you
Use the project name or project ID arguments, optionally select tables for a single-source project, and consume console logs and exit codes from the calling system.
Automation · Command line
Save the project in the UI. Run it from automation.
Omni Loader provides a one-shot console runner for saved projects. Select a project by name or ID and let an external scheduler or CI/CD system own timing and orchestration.
Headless execution Load · execute · report
Automation ready
Inputs
Saved projectREADY
EnvironmentREADY
Scheduler triggerREADY
Saved project runner Load · execute · report
Outputs
Migration runREADY
Structured logsREADY
Exit statusREADY
The job to be done
Move the full dataset without turning failure into a restart.
A large migration is not finished when the first rows arrive. Omni Loader keeps parallel work productive, adapts the loading path to the target, and records enough progress to recover the part that failed.
Configure connections, selection, mapping, DDL, loading, validation, and target behavior in the product interface before automation takes over.
Why this path matters
Build and review the project interactively.
Configure connections, selection, mapping, DDL, loading, validation, and target behavior in the product interface before automation takes over.
The outcome
Save the configuration once, then call it from the scheduler or CI/CD system your team already trusts.
The payoff
See what the capability changes.
Name or ID
Saved project selection
Execute the reviewed project configuration.
Optional
Table restriction
Limit a single-source run to a semicolon-delimited table list.
Exit codes
Automation signal
Return process status to the calling scheduler or pipeline.
Where the work happens
The details that make the result usable.
Read each capability as part of the operating path. The important question is not whether a feature exists, but what work it removes and what evidence it leaves behind.
At a glance
A visual summary of the work.
The CLI is the supported automation surface. Use a scheduler, deployment pipeline, or job runner to invoke it; Omni Loader does not claim a public REST API or built-in scheduler.
UI for design
Build and review the project interactively.
Configure connections, selection, mapping, DDL, loading, validation, and target behavior in the product interface before automation takes over.
CLI for execution
Run an already saved project once.
Use the project name or project ID arguments, optionally select tables for a single-source project, and consume console logs and exit codes from the calling system.
External scheduling
Keep orchestration in the tool your operations team already runs.
The CLI is the supported automation surface. Use a scheduler, deployment pipeline, or job runner to invoke it; Omni Loader does not claim a public REST API or built-in scheduler.
The path to confidence
See the work. Make the call. Prove the result.
The page keeps the product detail close to the decision it supports. Your team can see what the software handles automatically, what it changes for the target, and what the result leaves ready to operate.
Build and review the project interactively.
Configure connections, selection, mapping, DDL, loading, validation, and target behavior in the product interface before automation takes over.
Run an already saved project once.
Use the project name or project ID arguments, optionally select tables for a single-source project, and consume console logs and exit codes from the calling system.
Keep orchestration in the tool your operations team already runs.
The CLI is the supported automation surface. Use a scheduler, deployment pipeline, or job runner to invoke it; Omni Loader does not claim a public REST API or built-in scheduler.
Take the next step
Make a reviewed migration project repeatable.
Save the configuration once, then call it from the scheduler or CI/CD system your team already trusts.
Plan my migration