Sellsy → PlanetScale
AI-first ETL from Sellsy into PlanetScale. Governed entities, incremental sync, typed landing tables.
How Datrise loads Sellsy into PlanetScale
Datrise syncs Sellsy's contacts, accounts, deals, activities, and lifecycle events into PlanetScale as a typed table per source entity. Flexible or custom fields land in JSON columns, and timestamps such as created, updated, and status changes are typed as DATETIME.
Sync is incremental: Datrise uses a watermark on updated-at, applied with INSERT … ON DUPLICATE KEY UPDATE, so re-runs update only what changed. Vitess sharding by tenant or entity key for very large tables. PlanetScale disallows foreign-key constraints by default, so Datrise models relationships by stable id columns rather than enforced FKs.
Ideal for horizontally scalable MySQL apps on Vitess.
Endpoints
Sellsy: European CRM for SMB and mid-market sales teams.
PlanetScale: Serverless MySQL platform with safe schema workflows.
How Sellsy entities map to PlanetScale
| Sellsy entity | PlanetScale object | Notes |
|---|---|---|
| contacts | sellsy_contacts | id PK · custom fields → JSON columns |
| accounts | sellsy_accounts | id PK · linked to sellsy_contacts |
| deals | sellsy_deals | id PK · linked to sellsy_contacts |
| activities | sellsy_activities | DATETIME events |
FAQ
How does Datrise handle Sellsy's custom fields in PlanetScale?
Flexible values are stored as JSON columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native PlanetScale types.
How does the Sellsy to PlanetScale sync stay up to date?
It runs incrementally — Datrise uses a watermark on updated-at, applied with INSERT … ON DUPLICATE KEY UPDATE.
Related pipelines
More destinations for Sellsy
More sources for PlanetScale
Early access
Connect Sellsy to PlanetScale 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.