What changes for you
Use project-wide naming, type, creation, and load defaults, then override tables and columns that require source-specific treatment.
Solution · Consolidation
Bring multiple source databases into one governed migration project.
Omni Loader can maintain multiple aliased source connections in one saved project and route each selected table from its own source into a shared target.
Many catalogs · one target Alias · map · coordinate
Sources aligned
Inputs
OracleREADY
PostgreSQLREADY
SQL ServerREADY
Consolidation plan Alias · map · coordinate
Output
A single database with multiple schemasREADY
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.
Add and remove aliased sources, browse their metadata, and preserve source identity on each selected table so execution reaches the correct system.
Why this path matters
Select from more than one source connection.
Add and remove aliased sources, browse their metadata, and preserve source identity on each selected table so execution reaches the correct system.
The outcome
Bring the source inventory, overlap rules, and target naming policy. We will map the project structure.
The payoff
See what the capability changes.
Many → one
Source consolidation
Coordinate multiple source catalogs against one target.
Aliased
Stable source identity
Keep table ownership clear throughout planning and execution.
Collision-aware
Output naming
Add source context where file or table paths would collide.
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.
When multiple sources would produce the same table or file path, Omni Loader can retain source context in the generated destination path.
One project, multiple estates
Select from more than one source connection.
Add and remove aliased sources, browse their metadata, and preserve source identity on each selected table so execution reaches the correct system.
Shared target rules
Apply common policy without losing exceptions.
Use project-wide naming, type, creation, and load defaults, then override tables and columns that require source-specific treatment.
Collision handling
Keep staged outputs unambiguous.
When multiple sources would produce the same table or file path, Omni Loader can retain source context in the generated destination path.
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.
Alias each source connection
Keep each source connection’s identity attached to every selected table throughout the project.
Apply shared target rules
Set common naming, type, creation, and load defaults once, then override only source-specific exceptions.
Deduplicate the target automatically
When multiple sources would produce the same table or file path, Omni Loader automatically deduplicates the target.
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
- Source consolidation
- Stable source identity
- Select from more than one source connection.
- Apply common policy without losing exceptions.
- Consolidate sources without losing their identity.
Take the next step
Consolidate sources without losing their identity.
Bring the source inventory, overlap rules, and target naming policy. We will map the project structure.
Plan my migration