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.

Plan my migration Explore mappings

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.

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.

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.

What changes for you

Source and target adapters provide their own metadata and DDL behavior. Global mappings establish the baseline while table and column overrides handle exceptional objects.

The outcome

Bring the source and target engines. We will map the schema objects, type rules, and creation policy before the data move.

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.

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.

Use the target DDL review and export surfaces to validate names, types, and object policy with database owners before loading production data.

Isometric illustration of database structures and data paths

Target preparation

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

Engine-aware mapping

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.

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.

Before you choose

Check the path against your environment.

Use the page-specific details below as a short discovery checklist. They are the conditions and work areas that shape the capability, not generic product promises.

  • Schemas and tables
  • User-defined types
  • Indexes and foreign keys
  • Sequences and counters

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.

  1. 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.

  2. 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.

  3. 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.

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.

Mapping and transformations

Control names and values.

Customization

Override project defaults precisely.

Supported databases

Check source and target engines.

Your working set

What this page leaves you with

  • Target DDL planning
  • Cross-engine conversion
  • Create, recreate, or preserve existing structures.
  • Translate the model, not just the spelling.
  • Build a target your database team can review.

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