DatriseAI-first ETL

Recharge Holistics

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

How Datrise loads Recharge into Holistics

Datrise syncs Recharge's subscriptions, charges, customers, plans, and churn events into Holistics as warehouse tables modeled in Holistics. Flexible or custom fields land in flattened columns for the modeling layer, and timestamps such as created, updated, and status changes are typed as date/time dimensions.

Sync is incremental: Datrise uses incremental refresh of the modeled tables, so re-runs update only what changed. Date-partitioned facts for fast aggregates. Holistics models data as code on top of SQL, so Datrise lands stable column names to keep your models from drifting.

Ideal for as-code BI modeling on a warehouse.

Endpoints

Recharge: Subscription commerce for Shopify and recurring billing.

Holistics: Self-service BI with modeling layers and scheduled report delivery.

How Recharge entities map to Holistics

Recharge entityHolistics objectNotes
subscriptionsrecharge_subscriptionsid PK · custom fields → flattened columns for the modeling layer
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 Holistics?

Flexible values are stored as flattened columns for the modeling layer, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Holistics types.

How does the Recharge to Holistics sync stay up to date?

It runs incrementally — Datrise uses incremental refresh of the modeled tables.

Related pipelines

Early access

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