Guides
Guides for specific sources, destinations, and the combinations in between — the caveats, the defaults, and a sensible place to start for each one.
By source database
Section titled “By source database”By managed Postgres destination
Section titled “By managed Postgres destination”Destination-specific playbooks: the real provider connection, TLS, pooling, and firewall setup — not just generic source advice rewarmed. Grouped by where your data is headed:
- Supabase: from MySQL · from MSSQL · from Azure SQL · from PlanetScale · from RDS MySQL · from Cloud SQL MySQL
- Neon: from MySQL · from MSSQL · from Azure SQL · from PlanetScale · from RDS MySQL · from Cloud SQL MySQL
- PlanetScale Postgres: from MySQL · from MSSQL
- Railway Postgres: from MySQL · from MSSQL
- Render Postgres: from MySQL · from MSSQL
By managed source environment
Section titled “By managed source environment”Where your source lives changes the access, TLS, and firewall story as much as the destination does. These guides cover the source-side specifics for managed and hosted databases:
- Managed MySQL sources: PlanetScale (MySQL/Vitess) — to Supabase · to Neon; AWS RDS / Aurora MySQL — to Supabase · to Neon; Google Cloud SQL for MySQL — to Supabase · to Neon
- Azure SQL / SQL Server sources: Azure SQL to Supabase · Azure SQL to Neon · MSSQL to Railway · MSSQL to Render