DatriseAI-first ETL

Salesforce NPSP Domo

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

How Datrise loads Salesforce NPSP into Domo

Datrise syncs Salesforce NPSP's contacts, accounts, deals, activities, and lifecycle events into Domo as datasets in Domo's cloud store via connector. Flexible or custom fields land in flattened columns for Magic ETL, and timestamps such as created, updated, and status changes are typed as date/time columns.

Sync is incremental: Datrise uses partitioned dataset updates rather than full replaces, so re-runs update only what changed. Domo dataset partitions keyed on load date. Domo stores its own copy of data, so Datrise sends incremental partitions to avoid re-uploading whole datasets.

Ideal for all-in-one cloud BI with built-in ETL.

Endpoints

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

Domo: Cloud BI platform combining data integration and executive dashboards.

How Salesforce NPSP entities map to Domo

Salesforce NPSP entityDomo objectNotes
contactssalesforce_npsp_contactsid PK · custom fields → flattened columns for Magic ETL
accountssalesforce_npsp_accountsid PK · linked to salesforce_npsp_contacts
dealssalesforce_npsp_dealsid PK · linked to salesforce_npsp_contacts
activitiessalesforce_npsp_activitiesdate/time columns events

FAQ

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

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

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

It runs incrementally — Datrise uses partitioned dataset updates rather than full replaces.

Related pipelines

Early access

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