Salesforce NPSP to Google BigQuery Integration
AI-first ETL from Salesforce NPSP into Google BigQuery. Governed entities, incremental sync, typed landing tables.
How Datrise loads Salesforce NPSP into Google BigQuery
Datrise syncs Salesforce NPSP's contacts, households, opportunities, recurring donations, general accounting units, and campaigns into Google BigQuery as a partitioned table per source entity. Flexible or custom fields land in JSON or nested/repeated (STRUCT) columns, and timestamps such as created, updated, and status changes are typed as TIMESTAMP.
Sync is incremental: Datrise uses appends to a staging table, then MERGE on stable id into the partitioned target, so re-runs update only what changed. Partition by ingestion or event date and cluster by entity id to keep scanned bytes low. BigQuery bills by bytes scanned, so Datrise partitions and clusters every table to keep query costs predictable.
Ideal for Google-stack analytics and ML on serverless infrastructure.
Endpoints
Salesforce NPSP: Nonprofit Success Pack for donations and household giving.
Google BigQuery: Serverless analytics warehouse on GCP.
How Salesforce NPSP entities map to Google BigQuery
| Salesforce NPSP entity | Google BigQuery object | Notes |
|---|---|---|
| contacts | salesforce_npsp_contacts | id PK · custom fields → JSON or nested/repeated (STRUCT) columns |
| households | salesforce_npsp_households | id PK · linked to salesforce_npsp_contacts |
| opportunities | salesforce_npsp_opportunities | id PK · linked to salesforce_npsp_contacts |
| recurring donations | salesforce_npsp_recurring_donations | id PK · linked to salesforce_npsp_contacts |
FAQ
How does Datrise handle Salesforce NPSP's custom fields in Google BigQuery?
Flexible values are stored as JSON or nested/repeated (STRUCT) columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Google BigQuery types.
How does the Salesforce NPSP to Google BigQuery sync stay up to date?
It runs incrementally — Datrise uses appends to a staging table, then MERGE on stable id into the partitioned target.
Related pipelines
More destinations for Salesforce NPSP
- Salesforce NPSP → Amazon Redshift
- Salesforce NPSP → Databricks SQL Warehouse
- Salesforce NPSP → ClickHouse
- Salesforce NPSP → DuckDB
- Salesforce NPSP → Amazon Athena
- Salesforce NPSP → Amazon S3 Data Lake
- Salesforce NPSP → Azure Data Lake Storage
- Salesforce NPSP → Azure Synapse
- Salesforce NPSP → Spreadsheets
- Salesforce NPSP → Airtable
- Salesforce NPSP → CSV Files
- Salesforce NPSP → MongoDB
More sources for Google BigQuery
- Veeva CRM → Google BigQuery
- Salesforce Health Cloud → Google BigQuery
- DealerSocket → Google BigQuery
- VinSolutions → Google BigQuery
- JobNimbus → Google BigQuery
- Buildertrend → Google BigQuery
- ServiceTitan → Google BigQuery
- Housecall Pro → Google BigQuery
- Jobber → Google BigQuery
- Mindbody → Google BigQuery
- Clio → Google BigQuery
- MyCase → Google BigQuery
Early access
Connect Salesforce NPSP to Google BigQuery 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.