DatriseAI-first ETL

Salesforce NPSP Mode

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

How Datrise loads Salesforce NPSP into Mode

Datrise syncs Salesforce NPSP's contacts, accounts, deals, activities, and lifecycle events into Mode as warehouse tables Mode queries with SQL. Flexible or custom fields land in flattened columns for SQL and notebooks, and timestamps such as created, updated, and status changes are typed as temporal columns.

Sync is incremental: Datrise uses incremental refresh of the queried tables, so re-runs update only what changed. Date-partitioned facts for report queries. Mode runs analyst-written SQL, so Datrise lands stable, documented tables that won't break saved reports.

Ideal for SQL-first analysis with Python and R notebooks.

Endpoints

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

Mode: Collaborative analytics workspace for SQL, Python, and shared reports.

How Salesforce NPSP entities map to Mode

Salesforce NPSP entityMode objectNotes
contactssalesforce_npsp_contactsid PK · custom fields → flattened columns for SQL and notebooks
accountssalesforce_npsp_accountsid PK · linked to salesforce_npsp_contacts
dealssalesforce_npsp_dealsid PK · linked to salesforce_npsp_contacts
activitiessalesforce_npsp_activitiestemporal columns events

FAQ

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

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

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

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

Related pipelines

Early access

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