Skip to content

Migrating by engine

Tested with: Databasezy API v1 · zb CLI 0.1

Every Databasezy engine has a migrate-in path. Postgres, MySQL, Valkey, FerretDB and libSQL are covered in how migrations work and the provider guides; the pages below cover the other engines.

EngineSources
MariaDBSelf-hosted MariaDB or MySQL, Amazon RDS for MariaDB, Docker containers, .sql / .sql.gz dumps, another Databasezy instance.
RedisRedis Cloud, Upstash, any reachable Redis or Valkey server, Docker containers, .rdb snapshots, another Databasezy instance.
MongoDBMongoDB Atlas, Railway, DigitalOcean, self-hosted MongoDB or FerretDB, Docker containers, mongodump archives (.bson.tar), another Databasezy instance.
TimescaleDBTimescale or self-hosted TimescaleDB, any PostgreSQL source (Neon, Supabase, RDS, self-hosted), Docker containers, pg_dump files (.dump, .sql, .sql.gz), another Databasezy instance.
ClickHouseSelf-hosted ClickHouse, ClickHouse Cloud and Aiven (connection string), .sql / .sql.gz scripts, CSV and Parquet files, another Databasezy instance.
DuckDBA .duckdb database file, a CSV file, or another Databasezy DuckDB instance.
CouchDBSelf-hosted CouchDB (any reachable server), another Databasezy instance.
MeilisearchSelf-hosted Meilisearch or Meilisearch Cloud (connection string), another Databasezy instance. Algolia import is tracked separately (coming later).
QdrantQdrant Cloud or self-hosted Qdrant (connection string), another Databasezy instance.
WeaviateWeaviate Cloud or self-hosted Weaviate (connection string), another Databasezy instance.
InfluxDBInfluxDB 3 (Core, Enterprise or Cloud) by connection string, another Databasezy instance.
QuestDBSelf-hosted QuestDB (REST or Postgres-wire URL), CSV files, another Databasezy instance.
TypeDBSelf-hosted TypeDB or TypeDB Cloud (3.4 or newer), another Databasezy instance.