DatriseAI-first ETL

Salesforce NPSP to Birst Integration

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

How Datrise loads Salesforce NPSP into Birst

Datrise syncs Salesforce NPSP's contacts, households, opportunities, recurring donations, general accounting units, and campaigns into Birst as warehouse tables for Birst's automated star schema. Flexible or custom fields land in flattened columns, and timestamps such as created, updated, and status changes are typed as date/time dimensions.

Sync is incremental: Datrise uses incremental refresh of the source tables Birst ingests, so re-runs update only what changed. Date-partitioned facts. Birst builds its own semantic layer, so Datrise lands conformed, well-keyed tables it can automate against.

Ideal for networked, governed enterprise BI.

Endpoints

Salesforce NPSP: Nonprofit Success Pack for donations and household giving.

Birst: Cloud BI with networked analytics and enterprise semantic layers.

How Salesforce NPSP entities map to Birst

Salesforce NPSP entityBirst objectNotes
contactssalesforce_npsp_contactsid PK · custom fields → flattened columns
householdssalesforce_npsp_householdsid PK · linked to salesforce_npsp_contacts
opportunitiessalesforce_npsp_opportunitiesid PK · linked to salesforce_npsp_contacts
recurring donationssalesforce_npsp_recurring_donationsid PK · linked to salesforce_npsp_contacts

FAQ

How does Datrise handle Salesforce NPSP's custom fields in Birst?

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

How does the Salesforce NPSP to Birst sync stay up to date?

It runs incrementally — Datrise uses incremental refresh of the source tables Birst ingests.

Related pipelines

Early access

Connect Salesforce NPSP to Birst 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.