# Databases migration

Source: https://docs.quake.ai/docs/databases/migration
Markdown: https://docs.quake.ai/docs/databases/migration.md
> Move an existing PostgreSQL, MySQL, or MariaDB database onto Quake AI with a dump, transfer, restore, and verification pass.

---

# Databases migration

Moving a relational database onto Quake AI follows the same four steps regardless of where the data starts: dump the source, transfer the dump into the private subnet, restore it into the target engine, then compare schemas and row counts before you repoint the application. The guides below cover each engine.

<DocsSectionLinks section="databases/migration" />

## Related migration guides

- [Migrate a Docker application from AWS](/docs/compute/migration/migrate-docker-app-from-aws): moves an application and its database together.
- [Migrate from Docker Compose](/docs/automation/migration/from-docker-compose): keeps a Compose-managed database on its named volume.
- [Migrate e-commerce storefronts to Quake AI](/resources/migration/migrate-ecommerce-storefronts-to-quake-ai): storefront cutover with a self-managed PostgreSQL target.
- [Migrate B2B SaaS to Quake AI](/resources/migration/migrate-saas-b2b-to-quake-ai): multi-tenant application cutover with a private database tier.