What changes for you
Translate the model, not just the spelling.
Source and target adapters provide their own metadata and DDL behavior. Global mappings establish the baseline while table and column overrides handle exceptional objects.
Migration foundation · Schema
Move more than rows. Build the target structure deliberately.
Omni Loader discovers source metadata, maps it to the target engine, and plans schemas, user-defined types, tables, indexes, sequences, counters, and foreign keys before data movement begins.
Metadata-to-DDL pipeline Map · order · preview
Target plan ready
Inputs
Tables + columnsREADY
Keys + indexesREADY
Types + defaultsREADY
Schema planner Map · order · preview
Outputs
Target tablesREADY
SequencesREADY
Foreign keysREADY
Why this path matters
Create, recreate, or preserve existing structures.
Choose whether Omni Loader creates the target, recreates selected objects, or expects an existing table. Object stages run in dependency-aware order around the data load.
- ✓Schemas and tables
- ✓User-defined types
- ✓Indexes and foreign keys
- ✓Sequences and counters
The payoff
See what the capability changes.
Metadata-driven
Target DDL planning
Generate target structures from the source catalog.
Heterogeneous
Cross-engine conversion
Map objects and types between different database families.
Reviewable
DDL preview and export
Inspect the planned target definition before execution.
Where the work happens
The details that make the result usable.
At a glance
A visual summary of the work.
Controlled execution
Preview what will happen before the migration runs.
Use the target DDL review and export surfaces to validate names, types, and object policy with database owners before loading production data.
Take the next step
Build a target your database team can review.
Bring the source and target engines. We will map the schema objects, type rules, and creation policy before the data move.
Plan my migration