Migration sources
Tested with: Generated from catalogue/migration-sources.yaml at build time
Each source has its own guide with the same structure: what you need before you start, where to find the
connection string, notes specific to that source, the steps in the portal, the zb CLI and the API, how the copy is
verified, cutover, rollback and troubleshooting. There are 28 sources in the catalogue.
Sources marked coming soon do not have a guided preset yet. Most of them still work today as a generic connection-string or file migration; each guide says what applies.
Managed providers
Section titled “Managed providers”| Source | Group | Target engines | Continuous sync | Status |
|---|---|---|---|---|
| Neon | PostgreSQL | PostgreSQL | Yes | Available |
| Supabase | PostgreSQL | PostgreSQL | Yes | Available |
| Amazon RDS and Aurora | Multi-engine | PostgreSQL, MySQL, MariaDB | Yes | Coming soon · phase 2 |
| Render | Multi-engine | PostgreSQL, Valkey | Yes | Coming soon · phase 2 |
| Railway | Multi-engine | PostgreSQL, MySQL, Valkey, MongoDB (Percona Server) | Yes | Coming soon · phase 2 |
| Heroku | Multi-engine | PostgreSQL, Valkey | No | Coming soon · phase 2 |
| Fly.io | PostgreSQL | PostgreSQL | Yes | Coming soon · phase 2 |
| Aiven | Multi-engine | PostgreSQL, MySQL, Valkey, ClickHouse | Yes | Coming soon · phase 2 |
| DigitalOcean Managed Databases | Multi-engine | PostgreSQL, MySQL, Valkey, MongoDB (Percona Server) | Yes | Coming soon · phase 2 |
| Crunchy Bridge | PostgreSQL | PostgreSQL | Yes | Coming soon · phase 2 |
| Vercel Postgres (legacy, now Neon) | PostgreSQL | PostgreSQL | Yes | Coming soon · phase 2 |
| Prisma Postgres | PostgreSQL | PostgreSQL | No | Coming soon · phase 2 |
| Xata | PostgreSQL | PostgreSQL | No | Coming soon · phase 3 |
| Netlify DB | PostgreSQL | PostgreSQL | Yes | Coming soon · phase 2 |
| Google Cloud SQL | Multi-engine | PostgreSQL, MySQL | Yes | Coming soon · phase 3 |
| Azure Database | Multi-engine | PostgreSQL, MySQL | Yes | Coming soon · phase 3 |
| PlanetScale | MySQL | MySQL | No | Available |
| Upstash Redis | Key-value | Valkey | No | Available |
| Vercel KV (legacy, now Upstash) | Key-value | Valkey | No | Coming soon · phase 2 |
| Redis Cloud | Key-value | Valkey, Redis (compat) | No | Coming soon · phase 2 |
| Turso | SQLite family | libSQL / SQLite | No | Available |
| Cloudflare D1 | SQLite family | libSQL / SQLite | No | Coming soon · phase 2 |
| MongoDB Atlas | Document | MongoDB (Percona Server), FerretDB (MongoDB-compatible) | No | Available |
| Algolia | Search | Meilisearch | No | Coming soon · phase 3 |
Servers, containers and files
Section titled “Servers, containers and files”| Source | Group | Target engines | Continuous sync | Status |
|---|---|---|---|---|
| Self-hosted server | Servers, containers and files | PostgreSQL, TimescaleDB, MySQL, MariaDB, Valkey, Redis (compat), MongoDB (Percona Server), FerretDB (MongoDB-compatible), ClickHouse, InfluxDB 3, QuestDB, Meilisearch, Qdrant, Weaviate, CouchDB, TypeDB | Yes | Available |
| Local files and dumps | Servers, containers and files | PostgreSQL, TimescaleDB, MySQL, MariaDB, Valkey, Redis (compat), libSQL / SQLite, DuckDB, MongoDB (Percona Server), FerretDB (MongoDB-compatible), ClickHouse, QuestDB | No | Available |
| Docker container | Servers, containers and files | PostgreSQL, TimescaleDB, MySQL, MariaDB, Valkey, Redis (compat), MongoDB (Percona Server) | No | Available |
| Another Databasezy instance | Servers, containers and files | PostgreSQL, MySQL, MariaDB, Valkey, Redis (compat), libSQL / SQLite, DuckDB, MongoDB (Percona Server), FerretDB (MongoDB-compatible), ClickHouse, InfluxDB 3, QuestDB, Meilisearch, Qdrant, Weaviate, CouchDB, TypeDB, TimescaleDB | Yes | Coming soon · phase 2 |
Not listed?
Section titled “Not listed?”Any database that the zb CLI can reach, or that you can dump to a file, can be migrated: see
from a self-hosted server and local databases and files.
Switching engines on the way, for example from Redis to Valkey, is covered in
engine conversions.