Skip to content
LayerbaseLayerbase

Database conversions

A new engine for your existing data.

Choose where you are starting and where you want to go. See what carries over, what needs attention, and what gets checked before you switch.

Choose your current engine.

Choose a destination to see its conversion guide.

Compatible engine conversions

Keep the SQL schema or keyspace and compare counts after copying. MySQL/MariaDB and Redis/Valkey share their family protocol. SQLite to libSQL needs a different client.

Available

MySQLMariaDB

Move your MySQL schema and rows into MariaDB on Layerbase, with a pre-check for objects that need attention and a count report after the copy.

Available

MariaDBMySQL

Move MariaDB tables into MySQL after reviewing MariaDB-only types, sequences, collations, and authentication. The target requires a plan that includes MySQL.

Available

RedisValkey

Copy your Redis keyspace into Valkey, then compare key counts before pointing your application at the new target.

Available

ValkeyRedis

Copy your Valkey keyspace into Redis, then compare key counts before pointing your application at the new target.

Available

SQLitelibSQL

Copy SQLite tables into libSQL for its remote HTTPS interface. This is a SQL-compatible conversion, not a drop-in client swap: replace the Postgres-wire client with the libSQL client.

Documents to relational tables

Review a mapping before copying Mongo-wire documents into PostgreSQL. The planned workflow checks counts, ID checksums, field coverage, and sampled round trips before cutover.

Available

MongoDBPostgreSQL

Review a proposed relational schema before moving documents into tables. The source _id stays with each root row, and unmapped fields can be preserved as JSONB.

Available

DocumentDBPostgreSQL

Review a proposed relational schema before moving documents into tables. The source _id stays with each root row, and unmapped fields can be preserved as JSONB.

Available

FerretDBPostgreSQL

Review a proposed relational schema before moving documents into tables. The source _id stays with each root row, and unmapped fields can be preserved as JSONB.

Moving from another hosting platform? See migration paths. For the current Convert tab, read the conversion guide.