DatriseAI-first ETL

Salesforce NPSP Yellowfin

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

How Datrise loads Salesforce NPSP into Yellowfin

Datrise syncs Salesforce NPSP's contacts, accounts, deals, activities, and lifecycle events into Yellowfin as warehouse tables Yellowfin builds views on. 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 connected tables, so re-runs update only what changed. Date-partitioned facts. Yellowfin views reference columns by name, so Datrise lands stable, well-typed columns to keep reports valid.

Ideal for dashboards with automated data storytelling.

Endpoints

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

Yellowfin: BI suite with dashboards, automated insights, and data storytelling.

How Salesforce NPSP entities map to Yellowfin

Salesforce NPSP entityYellowfin objectNotes
contactssalesforce_npsp_contactsid PK · custom fields → flattened columns
accountssalesforce_npsp_accountsid PK · linked to salesforce_npsp_contacts
dealssalesforce_npsp_dealsid PK · linked to salesforce_npsp_contacts
activitiessalesforce_npsp_activitiesdate/time dimensions events

FAQ

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

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 Yellowfin types.

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

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

Related pipelines

Early access

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