Supported databases

Any source. Any target. One way to move.

Morph migrates across 13 engines and five data models — homogeneous upgrades, cross-engine dialect shifts and full cross-paradigm remodels. Pick a family below to explore the matrix.

coverage
Relational
7 engines
Document
1 engine
Key-value
2 engines
Wide-column
1 engine
Warehouse
2 engines
Support matrix

Every engine, grouped by data model

Each is a valid source and a valid target. Filter by family, then hover a tile.

Relational

Rows, schemas and SQL.7 engines
PG
Relational

PostgreSQL

Versions
1615141312
source & target
SQL
Relational

MySQL

Versions
8.48.05.7
source & target
MDB
Relational

MariaDB

Versions
1110.1110.6
source & target
MSS
Relational

SQL Server

Versions
202220192017
source & target
ORA
Relational

Oracle

Versions
23ai21c19c
source & target
LITE
Relational

SQLite

Versions
3
source & target
CRDB
Relational

CockroachDB

Versions
2423
source & target

Document

Nested JSON-style records.1 engine
MNGO
Document

MongoDB

Versions
8.07.06.0
source & target

Key-value

Fast lookups by key.2 engines
DDB
Key-value

DynamoDB

Versions
n/a
source & target
RDS
Key-value

Redis

Versions
7.47.2
source & target

Wide-column

Partitioned column families.1 engine
CASS
Wide-column

Cassandra

Versions
5.04.1
source & target

Warehouse

Columnar analytics at scale.2 engines
SNOW
Warehouse

Snowflake

Versions
current
source & target
BQ
Warehouse

BigQuery

Versions
current
source & target
How distance maps to price

The further the move, the more remodeling

Complexity — and therefore your one-time price — scales with how far the data model travels. These multipliers are applied deterministically, server-side.

base price

Same engine, new home

PostgreSQL 13 → PostgreSQL 16

A version upgrade or a lift to new infrastructure. The schema is preserved; the work is safe movement, validation and a clean cutover.

× 1.25

Different engine, same paradigm

MySQL → PostgreSQL

Still relational, but dialects and types diverge. Morph rewrites DDL to the target's idioms and maps every column — AUTO_INCREMENT, ENUM, JSON and friends.

× 1.6

Different data model entirely

PostgreSQL → MongoDB

Relational to document, or SQL to NoSQL. Morph derives collections from your access patterns and decides embedding versus referencing per entity — the deepest remodel.

On top of the move’s class, price reflects data volume and table breadth — and tighter downtime windows add orchestration. Plans start at $499 for small homogeneous moves and scale to Enterprise for cross-paradigm, mission-critical cutovers.

See pricing
Common pairings

Moves teams run through Morph

ORAOracle
cross-engine
PGPostgreSQL

Cutting licensing cost

SQLMySQL
cross-engine
PGPostgreSQL

Richer types & extensions

PGPostgreSQL
cross-paradigm
MNGOMongoDB

Flexible document model

MSSSQL Server
cross-engine
PGPostgreSQL

Open-source consolidation

MNGOMongoDB
cross-paradigm
PGPostgreSQL

Back to relational integrity

PGPostgreSQL
cross-engine
CRDBCockroachDB

Horizontal scale-out

Don’t see your exact pair?

Describe your source and target. Morph scores the move, quotes a fixed price, and generates every artifact — across engines and paradigms alike.