Square → MySQL
AI-first ETL from Square into MySQL. Governed entities, incremental sync, typed landing tables.
How Datrise loads Square into MySQL
Datrise syncs Square's payments, orders, customers, catalog items, and locations into MySQL 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/TIMESTAMP.
Sync is incremental: Datrise uses a watermark on updated-at, applied with INSERT … ON DUPLICATE KEY UPDATE, so re-runs update only what changed. Optional RANGE partitioning by load date. MySQL collation matters for CRM text, so Datrise lands utf8mb4 to preserve emoji and non-Latin characters.
Ideal for operational reporting and app databases already standardized on MySQL.
Endpoints
Square: Payments and commerce platform for retail and online sellers.
MySQL: Widely used OSS relational engine (InnoDB).
How Square entities map to MySQL
| Square entity | MySQL object | Notes |
|---|---|---|
| payments | square_payments | id PK · custom fields → JSON columns |
| orders | square_orders | id PK · linked to square_payments |
| customers | square_customers | id PK · linked to square_payments |
| catalog items | square_catalog_items | id PK · linked to square_payments |
FAQ
How does Datrise handle Square's custom fields in MySQL?
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 MySQL types.
How does the Square to MySQL 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 Square
Early access
Connect Square to MySQL 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.