DatriseAI-first ETL

Recharge MySQL

AI-first ETL from Recharge into MySQL. Governed entities, incremental sync, typed landing tables.

How Datrise loads Recharge into MySQL

Datrise syncs Recharge's subscriptions, charges, customers, plans, and churn events 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

Recharge: Subscription commerce for Shopify and recurring billing.

MySQL: Widely used OSS relational engine (InnoDB).

How Recharge entities map to MySQL

Recharge entityMySQL objectNotes
subscriptionsrecharge_subscriptionsid PK · custom fields → JSON columns
chargesrecharge_chargesid PK · linked to recharge_subscriptions
customersrecharge_customersid PK · linked to recharge_subscriptions
plansrecharge_plansid PK · linked to recharge_subscriptions

FAQ

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

Early access

Connect Recharge 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.