What changes for you
Use source and target filters, full or append behavior, delta keys, partition selection, and explicit cutoff rules where the migration requires them.
Project design · Data selection
Move the data the target needs. Keep selection explicit.
Omni Loader combines metadata browsing with table, column, filter, load-mode, partition, slice, validation, and cutoff controls.
Migration scope Discover · filter · tier
Scope calculated
Inputs
Catalog metadataREADY
Business filtersREADY
Cutoff tiersREADY
Selection plan Discover · filter · tier
Outputs
Chosen tablesREADY
Chosen columnsREADY
Chosen rowsREADY
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.
Browse discovered metadata, search large estates, inspect approximate sizes, and select the objects that belong in the migration.
Why this path matters
Choose tables and columns from the real catalog.
Browse discovered metadata, search large estates, inspect approximate sizes, and select the objects that belong in the migration.
The outcome
Define the selected objects, row filters, load modes, tier cutoffs, and validation policy together.
The payoff
See what the capability changes.
Catalog
Metadata selection
Search and choose tables from discovered source metadata.
Full · delta · append
Load behavior
Choose the data-copy mode per migration need.
Hot · warm · normal
Cutoff tiers
Route current and historical data through separate passes.
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.
Configure hot, warm, and normal passes to send different time ranges through target-specific storage or ingestion paths.
Object selection
Choose tables and columns from the real catalog.
Browse discovered metadata, search large estates, inspect approximate sizes, and select the objects that belong in the migration.
Row selection
Control what each table contributes.
Use source and target filters, full or append behavior, delta keys, partition selection, and explicit cutoff rules where the migration requires them.
Tiered passes
Handle current and historical data differently.
Configure hot, warm, and normal passes to send different time ranges through target-specific storage or ingestion paths.
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.
Choose tables and columns from the real catalog.
Browse discovered metadata, search large estates, inspect approximate sizes, and select the objects that belong in the migration.
Control what each table contributes.
Use source and target filters, full or append behavior, delta keys, partition selection, and explicit cutoff rules where the migration requires them.
Handle current and historical data differently.
Configure hot, warm, and normal passes to send different time ranges through target-specific storage or ingestion paths.
Keep the plan connected
Take the next useful step.
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.
Your working set
What this page leaves you with
- Metadata selection
- Load behavior
- Choose tables and columns from the real catalog.
- Control what each table contributes.
- Turn scope into an executable migration project.
Take the next step
Turn scope into an executable migration project.
Define the selected objects, row filters, load modes, tier cutoffs, and validation policy together.
Plan my migration