1С:CRM → Supabase
AI-first ETL from 1С:CRM into Supabase. Governed entities, incremental sync, typed landing tables.
How Datrise loads 1С:CRM into Supabase
Datrise syncs 1С:CRM's contacts, accounts, deals, activities, and lifecycle 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
1С:CRM: CRM with strong adoption in CIS markets for sales and operations.
Supabase: Postgres platform with auth, storage, and realtime APIs.
How 1С:CRM entities map to Supabase
| 1С:CRM entity | Supabase object | Notes |
|---|---|---|
| contacts | 1c_crm_contacts | id PK · custom fields → jsonb columns |
| accounts | 1c_crm_accounts | id PK · linked to 1c_crm_contacts |
| deals | 1c_crm_deals | id PK · linked to 1c_crm_contacts |
| activities | 1c_crm_activities | timestamptz events |
FAQ
How does Datrise handle 1С:CRM'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 1С:CRM 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
More destinations for 1С:CRM
Early access
Connect 1С:CRM 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.