Databases migration
Overview · Updated Sep 2026
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.
- How to Migrate MySQL or MariaDB to Quake AI: Move an existing MySQL or MariaDB database onto a Quake AI instance: check engine compatibility, dump the source, transfer through a bastion, restore, verify, and cut over.
- How to Migrate PostgreSQL to Quake AI: Move an existing PostgreSQL database onto a Quake AI instance: check versions, dump the source, transfer the dump through a bastion, restore, verify, and cut the application over.
Related migration guides#
- Migrate a Docker application from AWS: moves an application and its database together.
- Migrate from Docker Compose: keeps a Compose-managed database on its named volume.
- Migrate e-commerce storefronts to Quake AI: storefront cutover with a self-managed PostgreSQL target.
- Migrate B2B SaaS to Quake AI: multi-tenant application cutover with a private database tier.
See Also
Was this page helpful?