DonorPerfect to MySQL Integration

How Datrise loads DonorPerfect into MySQL

Datrise syncs DonorPerfect's donors, gifts, pledges, campaigns, appeals, and recurring gift schedules 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

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

MySQL: Widely used OSS relational engine (InnoDB).

How DonorPerfect entities map to MySQL

DonorPerfect entity	MySQL object	Notes
donors	`donorperfect_donors`	id PK · custom fields → JSON columns
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 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 DonorPerfect 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 DonorPerfect 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.