Supported databases
Browse Omni Loader sources and targets across operational databases, cloud warehouses, data lakes, and file formats, then open an engine for its migration details.
A broad connection surface
Start with the source and target you actually have.
Review supported engines, warehouses, lakes, and file formats before you design the migration plan around a single assumed platform.
Amazon RDS
Use Amazon RDS as a source or target for a high-volume, one-time migration.
Amazon Redshift
Use Amazon Redshift as a source or target for a high-volume, one-time migration.
Analytics Platform System
Use Analytics Platform System as a source or target for a high-volume, one-time migration.
Apache Parquet
Use Apache Parquet as a source or target for a high-volume, one-time migration.
Azure SQL
Use Azure SQL as a source or target for a high-volume, one-time migration.
CockroachDB
Read CockroachDB as a source for a high-volume, one-time migration.
CSV
Use CSV as a source or target for a high-volume, one-time migration.
Databricks
Use Databricks as a source or target for a high-volume, one-time migration.
Exadata
Use Exadata as a source or target for a high-volume, one-time migration.
Fabric Lakehouse
Use Fabric Lakehouse as a source or target for a high-volume, one-time migration.
Fabric Warehouse
Use Fabric Warehouse as a source or target for a high-volume, one-time migration.
Google AlloyDB
Use Google AlloyDB as a source or target for a high-volume, one-time migration.
Google BigQuery
Use Google BigQuery as a source or target for a high-volume, one-time migration.
Google Spanner
Use Google Spanner as a source or target for a high-volume, one-time migration.
Greenplum
Use Greenplum as a source or target for a high-volume, one-time migration.
IBM DB2 for i
Use IBM DB2 for i as a source or target for a high-volume, one-time migration.
IBM DB2 LUW
Use IBM DB2 LUW as a source or target for a high-volume, one-time migration.
IBM DB2 z/OS
Use IBM DB2 z/OS as a source or target for a high-volume, one-time migration.
JSON
Use JSON as a source or target for a high-volume, one-time migration.
MariaDB
Use MariaDB as a source or target for a high-volume, one-time migration.
MySQL
Use MySQL as a source or target for a high-volume, one-time migration.
Netezza
Read Netezza as a source for a high-volume, one-time migration.
NuoDB
Use NuoDB as a source or target for a high-volume, one-time migration.
ODBC
Use ODBC as a source or target for a high-volume, one-time migration.
Oracle
Use Oracle as a source or target for a high-volume, one-time migration.
Oracle RDB
Use Oracle RDB as a source or target for a high-volume, one-time migration.
PostgreSQL
Use PostgreSQL as a source or target for a high-volume, one-time migration.
SAP Adaptive Server Enterprise
Use SAP Adaptive Server Enterprise as a source or target for a high-volume, one-time migration.
SAP IQ
Use SAP IQ as a source or target for a high-volume, one-time migration.
Snowflake
Use Snowflake as a source or target for a high-volume, one-time migration.
SQL Server
Use SQL Server as a source or target for a high-volume, one-time migration.
Synapse Dedicated Pool
Use Synapse Dedicated Pool as a source or target for a high-volume, one-time migration.
Synapse SQL Serverless
Use Synapse SQL Serverless as a source or target for a high-volume, one-time migration.
Teradata
Use Teradata as a source or target for a high-volume, one-time migration.
Vertica
Use Vertica as a source or target for a high-volume, one-time migration.
Yellowbrick
Read Yellowbrick as a source for a high-volume, one-time migration.
Easy database connections
We include all native database drivers that we're licensed to distribute, so you can connect and start working immediately in most cases. For databases where licensing restrictions prevent bundling, we handle the license acceptance and driver installation automatically. It takes just seconds.
Our specialization in database migration ensures comprehensive support for modern database systems, delivering reliable and accurate migrations regardless of your source or target platform.
The practical details
Frequently asked questions
What does Omni Loader migrate? +
Omni Loader moves full datasets between operational databases, cloud warehouses, data lakes, and supported file formats. It combines schema preparation with parallel, resumable bulk data movement.
Which databases can Omni Loader move? +
The supported database catalog covers operational databases, cloud warehouses, lakes, and file formats. Each database page identifies whether the engine can be used as a bulk migration source, target, or both.
How does Omni Loader handle very large tables? +
Large tables can be divided into bounded slices by partition, numeric or date range, text prefix, or file range. Multiple workers then process independent tables and slices in parallel.
Do I have to install anything on my database server? +
Omni Loader runs on Windows or Linux compute with network access to the source and target. Database drivers are included where licensing allows, and external drivers can be installed when a vendor license requires it.
How does Omni Loader choose a loading method? +
The project can use provider bulk APIs, multi-row statements, direct writers, or staged native ingestion according to the destination. Defaults provide a practical starting point and table-level overrides handle exceptions.
Can Omni Loader consolidate multiple sources? +
Yes. A saved project can define multiple aliased source catalogs and load selected objects into one target while preserving explicit mapping and selection rules.
How can I verify a completed migration? +
Validation can compare row counts, table hashes, or individual records according to the source and target capabilities. Snapshot reconciliation can also persist added, changed, and deleted differences for review and controlled repair.
Can a failed migration be resumed? +
Run history records completed and failed work. Reported failed work units can be replayed without restarting every table in a large migration project.