What changes for you
Start from adapter-provided mappings and override individual columns when business semantics or target constraints require a different representation.
Migration control · Mapping
Set the common rule once. Override the exception precisely.
Omni Loader maps source schemas, tables, columns, names, types, and values into the target model with global rules and granular overrides.
Explicit target contract Rename · convert · represent
Preview available
Inputs
Source namesREADY
Source typesREADY
Source valuesREADY
Mapping rules Rename · convert · represent
Outputs
Target namesREADY
Target typesREADY
Target valuesREADY
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.
Define schema, table, and column naming rules, resolve collisions, and preserve stable source identity throughout the project.
Why this path matters
Control the target model explicitly.
Define schema, table, and column naming rules, resolve collisions, and preserve stable source identity throughout the project.
The outcome
Document the naming standard, type exceptions, and value rules before the production run.
The payoff
See what the capability changes.
Project-wide
Naming policy
Apply consistent schema, table, and column conventions.
Per table
Scoped exceptions
Change the objects that cannot follow the default.
Per value
Target representation
Convert source values through target-aware readers.
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 transforming reader converts each source value into its target representation before bulk, statement, file, or native ingestion.
Naming and identity
Control the target model explicitly.
Define schema, table, and column naming rules, resolve collisions, and preserve stable source identity throughout the project.
Type mapping
Translate data types with target context.
Start from adapter-provided mappings and override individual columns when business semantics or target constraints require a different representation.
Value conversion
Transform values while they move.
The transforming reader converts each source value into its target representation before bulk, statement, file, or native ingestion.
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.
Control the target model explicitly.
Define schema, table, and column naming rules, resolve collisions, and preserve stable source identity throughout the project.
Translate data types with target context.
Start from adapter-provided mappings and override individual columns when business semantics or target constraints require a different representation.
Transform values while they move.
The transforming reader converts each source value into its target representation before bulk, statement, file, or native ingestion.
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
- Naming policy
- Scoped exceptions
- Control the target model explicitly.
- Translate data types with target context.
- Make target conventions part of the migration plan.
Take the next step
Make target conventions part of the migration plan.
Document the naming standard, type exceptions, and value rules before the production run.
Plan my migration