DatriseAI-first ETL

Sellsy to Supabase Integration

AI-first ETL from Sellsy into Supabase. Governed entities, incremental sync, typed landing tables.

How Datrise loads Sellsy into Supabase

Datrise syncs Sellsy's prospects, opportunities, estimates, invoices, tickets, and timeline events 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

Sellsy: French CRM with quoting, invoicing, and support tickets.

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

How Sellsy entities map to Supabase

Sellsy entitySupabase objectNotes
prospectssellsy_prospectsid PK · custom fields → jsonb columns
opportunitiessellsy_opportunitiesid PK · linked to sellsy_prospects
estimatessellsy_estimatesid PK · linked to sellsy_prospects
invoicessellsy_invoicesid PK · linked to sellsy_prospects

FAQ

How does Datrise handle Sellsy'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 Sellsy 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 Sellsy 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.