DatriseAI-first ETL

MyCase Amazon Redshift

AI-first ETL from MyCase into Amazon Redshift. Governed entities, incremental sync, typed landing tables.

How Datrise loads MyCase into Amazon Redshift

Datrise syncs MyCase's contacts, accounts, deals, activities, and lifecycle events into Amazon Redshift as a typed table per source entity. Flexible or custom fields land in SUPER columns, and timestamps such as created, updated, and status changes are typed as TIMESTAMPTZ.

Sync is incremental: Datrise uses COPY from staged files, then a delete-and-insert merge on stable id, so re-runs update only what changed. A DISTKEY on the join id and a SORTKEY on the load timestamp. Redshift performance hinges on dist/sort keys, so Datrise picks them from your entity ids and sync timestamps rather than defaulting to EVEN distribution.

Ideal for AWS-native warehouses already using the Redshift ecosystem.

Endpoints

MyCase: Legal practice CRM for matters, clients, and intake workflows.

Amazon Redshift: AWS petabyte-scale warehouse with Spectrum.

How MyCase entities map to Amazon Redshift

MyCase entityAmazon Redshift objectNotes
contactsmycase_contactsid PK · custom fields → SUPER columns
accountsmycase_accountsid PK · linked to mycase_contacts
dealsmycase_dealsid PK · linked to mycase_contacts
activitiesmycase_activitiesTIMESTAMPTZ events

FAQ

How does Datrise handle MyCase's custom fields in Amazon Redshift?

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

How does the MyCase to Amazon Redshift sync stay up to date?

It runs incrementally — Datrise uses COPY from staged files, then a delete-and-insert merge on stable id.

Related pipelines

Early access

Connect MyCase to Amazon Redshift 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.