DatriseAI-first ETL

Salesforce NPSP MySQL

AI-first ETL from Salesforce NPSP into MySQL. Governed entities, incremental sync, typed landing tables.

How Datrise loads Salesforce NPSP into MySQL

Datrise syncs Salesforce NPSP's contacts, accounts, deals, activities, and lifecycle events 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

Salesforce NPSP: Nonprofit CRM for donors, campaigns, and stewardship.

MySQL: Widely used OSS relational engine (InnoDB).

How Salesforce NPSP entities map to MySQL

Salesforce NPSP entityMySQL objectNotes
contactssalesforce_npsp_contactsid PK · custom fields → JSON columns
accountssalesforce_npsp_accountsid PK · linked to salesforce_npsp_contacts
dealssalesforce_npsp_dealsid PK · linked to salesforce_npsp_contacts
activitiessalesforce_npsp_activitiesDATETIME/TIMESTAMP events

FAQ

How does Datrise handle Salesforce NPSP'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 Salesforce NPSP 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 Salesforce NPSP 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.