DonorPerfect to Mode Integration

How Datrise loads DonorPerfect into Mode

Datrise syncs DonorPerfect's donors, gifts, pledges, campaigns, appeals, and recurring gift schedules into Mode as warehouse tables Mode queries with SQL. Flexible or custom fields land in flattened columns for SQL and notebooks, and timestamps such as created, updated, and status changes are typed as temporal columns.

Sync is incremental: Datrise uses incremental refresh of the queried tables, so re-runs update only what changed. Date-partitioned facts for report queries. Mode runs analyst-written SQL, so Datrise lands stable, documented tables that won't break saved reports.

Ideal for SQL-first analysis with Python and R notebooks.

Endpoints

DonorPerfect: Fundraising database for gifts, pledges, and appeals.

Mode: Collaborative analytics workspace for SQL, Python, and shared reports.

How DonorPerfect entities map to Mode

DonorPerfect entity	Mode object	Notes
donors	`donorperfect_donors`	id PK · custom fields → flattened columns for SQL and notebooks
gifts	`donorperfect_gifts`	id PK · linked to donorperfect_donors
pledges	`donorperfect_pledges`	id PK · linked to donorperfect_donors
campaigns	`donorperfect_campaigns`	id PK · linked to donorperfect_donors

FAQ

How does Datrise handle DonorPerfect's custom fields in Mode?

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

How does the DonorPerfect to Mode sync stay up to date?

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

Related pipelines

Early access

Connect DonorPerfect to Mode 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.