Google Cloud SQL to Supabase Integration

How Datrise loads Google Cloud SQL into Supabase

Datrise syncs Google Cloud SQL's tables, rows, schemas, indexes, read replicas, and binlog changes into Supabase as a typed table per source entity in your Supabase Postgres. Flexible or custom fields land in jsonb columns, and timestamps such as created, updated, and status changes are typed as timestamptz.

Sync is incremental: Datrise uses a watermark on updated-at, applied with INSERT … ON CONFLICT DO UPDATE, so re-runs update only what changed. Optional declarative partitioning for high-volume tables. Datrise lands into a dedicated schema and leaves row-level security to you, so synced tables don't inherit public access by accident.

Ideal for app builders who want CRM data alongside their Supabase product data.

Endpoints

Google Cloud SQL: Managed MySQL, PostgreSQL, and SQL Server instances on GCP.

Supabase: Postgres platform with auth, storage, and realtime APIs.

How Google Cloud SQL entities map to Supabase

Google Cloud SQL entity	Supabase object	Notes
tables	`google_cloud_sql_tables`	id PK · custom fields → jsonb columns
rows	`google_cloud_sql_rows`	id PK · linked to google_cloud_sql_tables
schemas	`google_cloud_sql_schemas`	id PK · linked to google_cloud_sql_tables
indexes	`google_cloud_sql_indexes`	id PK · linked to google_cloud_sql_tables

FAQ

How does Datrise handle Google Cloud SQL's custom fields in Supabase?

Flexible values are stored as jsonb columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Supabase types.

How does the Google Cloud SQL to Supabase sync stay up to date?

It runs incrementally — Datrise uses a watermark on updated-at, applied with INSERT … ON CONFLICT DO UPDATE.

Related pipelines

Early access

Connect Google Cloud SQL to Supabase the easy way

Skip brittle scripts and manual exports. Join the waitlist to get a guided setup, AI-assisted mapping, and reliable incremental sync for this integration.