Burst Load profiles the source, divides large tables into bounded slices, moves many independent units concurrently, and records run and failed-task state for review and supported replay.
TargetBulk ingest The job to be done
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.
Omni Loader inspects tables, keys, sizes, and target behavior before execution. Large tables become concurrent ranges while smaller tables move alongside them, all within explicit worker and bandwidth limits.
Why this path matters
Omni Loader inspects tables, keys, sizes, and target behavior before execution. Large tables become concurrent ranges while smaller tables move alongside them, all within explicit worker and bandwidth limits.
What changes for you
Omni Loader records run, stage, table, and task status. Supported tasks that report failure retain a serialized payload for cleanup and replay; a process or host loss before failure is recorded is not a complete crash-resume checkpoint.
The outcome
Bring table sizes, keys, source limits, target ingestion, and the migration window. We will map slices, workers, recovery, and delivery.
The payoff
Use bounded workers across large tables and independent objects.
Start from measured behavior and tune only the exceptions.
Clean up and retry supported tasks that finish with an explicit failure.
Where the work happens
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
Extract large binary values to object storage, produce compressed warehouse-ready files, or apply precise transformation and mapping rules without replacing the movement engine.
Plan
Omni Loader inspects tables, keys, sizes, and target behavior before execution. Large tables become concurrent ranges while smaller tables move alongside them, all within explicit worker and bandwidth limits.
Run and recover
Omni Loader records run, stage, table, and task status. Supported tasks that report failure retain a serialized payload for cleanup and replay; a process or host loss before failure is recorded is not a complete crash-resume checkpoint.
Specialized outputs
Extract large binary values to object storage, produce compressed warehouse-ready files, or apply precise transformation and mapping rules without replacing the movement engine.
Before you choose
Use the page-specific details below as a short discovery checklist. They are the conditions and work areas that shape the capability, not generic product promises.
The path to confidence
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.
Omni Loader inspects tables, keys, sizes, and target behavior before execution. Large tables become concurrent ranges while smaller tables move alongside them, all within explicit worker and bandwidth limits.
Omni Loader records run, stage, table, and task status. Supported tasks that report failure retain a serialized payload for cleanup and replay; a process or host loss before failure is recorded is not a complete crash-resume checkpoint.
Extract large binary values to object storage, produce compressed warehouse-ready files, or apply precise transformation and mapping rules without replacing the movement engine.
Keep the plan connected
A capability becomes easier to operate when the next decision follows from the constraint you just uncovered. Explore the related work that completes this part of the path.
See slicing, workers, and throughput boundaries.
See adaptive defaults and measured exceptions.
See durable work-unit recovery.
Move binary values into object storage.
Run versioned plans from automation.
Build parallel analytical loads.
Apply shared rules and table overrides.
Your working set
Take the next step
Bring table sizes, keys, source limits, target ingestion, and the migration window. We will map slices, workers, recovery, and delivery.
Plan my migration