DatriseAI-first ETL

Recharge Snowflake

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

How Datrise loads Recharge into Snowflake

Datrise syncs Recharge's subscriptions, charges, customers, plans, and churn events into Snowflake as a typed table per source entity. Flexible or custom fields land in VARIANT columns, and timestamps such as created, updated, and status changes are typed as TIMESTAMP_TZ.

Sync is incremental: Datrise uses staged loads merged on stable id with MERGE, so credits scale with change volume, not table size, so re-runs update only what changed. Automatic micro-partitioning, with optional clustering keys on high-cardinality ids. Snowflake upper-cases unquoted identifiers, so Datrise standardizes on lower-case quoted names to keep column references stable.

Ideal for central analytics warehouses feeding BI and AI workloads.

Endpoints

Recharge: Subscription commerce for Shopify and recurring billing.

Snowflake: Cloud data warehouse with separated compute and storage.

How Recharge entities map to Snowflake

Recharge entitySnowflake objectNotes
subscriptionsrecharge_subscriptionsid PK · custom fields → VARIANT 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 Snowflake?

Flexible values are stored as VARIANT columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Snowflake types.

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

It runs incrementally — Datrise uses staged loads merged on stable id with MERGE, so credits scale with change volume, not table size.

Related pipelines

Early access

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