What changes for you
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.
Omni Loader maps source schemas, tables, columns, names, types, and values into the target model with global rules and granular overrides.
Why this path matters
Define schema, table, and column naming rules, resolve collisions, and preserve stable source identity throughout the project.
What changes for you
Start from adapter-provided mappings and override individual columns when business semantics or target constraints require a different representation.
The payoff
Apply consistent schema, table, and column conventions.
Change the objects that cannot follow the default.
Convert source values through target-aware readers.
Where the work happens
At a glance

Value conversion
The transforming reader converts each source value into its target representation before bulk, statement, file, or native ingestion.
Take the next step
Document the naming standard, type exceptions, and value rules before the production run.
Plan my migration