What changes for you
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.
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
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 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.
At a glance
A visual summary of the work.
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.
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