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.

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.

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.

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.

At a glance

A visual summary of the work.

Illustration of mapping, transformation, and migration customization

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.

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