Compatibility
Supported Databases
| Database | As Source | As Target | Migration Tracking |
|---|---|---|---|
| Oracle | ✅ Supported | ❌ | ❌ |
| PostgreSQL | ✅ Supported | ✅ Supported | ✅ Supported |
| SQL Server | ✅ Supported | ✅ Supported | ✅ Supported |
| Netezza | ✅ Supported | ❌ | ❌ |
Source databases
Any of the four supported databases can serve as a migration source. MigratorXpress reads the schema metadata and data, translates the DDL to the target dialect, and streams rows via FastTransfer.
- Oracle -- thin and thick client modes, Rowid-based parallel extraction
- PostgreSQL -- Ctid-based parallel extraction
- SQL Server -- PhysLoc-based parallel extraction
- Netezza -- source-only support, default port 5480
Target databases
PostgreSQL and SQL Server are supported as migration targets. MigratorXpress creates the schema, transfers data, and optionally copies constraints (PK, AK, FK).
- PostgreSQL -- target schema is created automatically
- SQL Server -- supports Clustered Columnstore Indexes via
--cci_threshold
Migration tracking database
The migration tracking database can be SQL Server or PostgreSQL. It stores per-table transfer status, row counts, constraint copy results, and event logs. This database enables the --resume capability and provides a full audit trail. The backend is selected by the ds_type of the entry referenced by --migration_db_auth_id (mssql or postgres) and is auto-detected; no extra flag is required.
- SQL Server as Migration Tracking -- default, mature path
- PostgreSQL as Migration Tracking -- added in v0.6.32, tracking tables live in the
publicschema
Supported Platforms
| Platform | Architecture |
|---|---|
| Windows | x64 |
| Linux | x64 |
MigratorXpress ships as a native binary for each platform. No runtime installation (Python, Java, .NET) is required.
See Also
- Quick Start Guide -- get started in 5 minutes
- CLI Reference -- all command-line options
- Database Configuration -- connection setup for each database type