Microsoft Dynamics 365 → Google BigQuery
AI-first ETL from Microsoft Dynamics 365 into Google BigQuery. Governed entities, incremental sync, typed landing tables.
How Datrise loads Microsoft Dynamics 365 into Google BigQuery
Datrise syncs Microsoft Dynamics 365's accounts, opportunities, activities, and enterprise CRM process data 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
Microsoft Dynamics 365: Microsoft enterprise CRM and ERP suite.
Google BigQuery: Serverless analytics warehouse on GCP.
How Microsoft Dynamics 365 entities map to Google BigQuery
| Microsoft Dynamics 365 entity | Google BigQuery object | Notes |
|---|---|---|
| accounts | microsoft_dynamics_accounts | id PK · custom fields → JSON or nested/repeated (STRUCT) columns |
| opportunities | microsoft_dynamics_opportunities | id PK · linked to microsoft_dynamics_accounts |
| activities | microsoft_dynamics_activities | TIMESTAMP events |
| enterprise CRM process data | microsoft_dynamics_enterprise_crm_process_data | id PK · linked to microsoft_dynamics_accounts |
FAQ
How does Datrise handle Microsoft Dynamics 365'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 Microsoft Dynamics 365 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 Microsoft Dynamics 365
- Microsoft Dynamics 365 → Amazon Redshift
- Microsoft Dynamics 365 → Databricks SQL Warehouse
- Microsoft Dynamics 365 → ClickHouse
- Microsoft Dynamics 365 → DuckDB
- Microsoft Dynamics 365 → Amazon Athena
- Microsoft Dynamics 365 → Amazon S3 Data Lake
- Microsoft Dynamics 365 → Azure Data Lake Storage
- Microsoft Dynamics 365 → Azure Synapse
- Microsoft Dynamics 365 → Spreadsheets
- Microsoft Dynamics 365 → Airtable
- Microsoft Dynamics 365 → CSV Files
- Microsoft Dynamics 365 → MongoDB
More sources for Google BigQuery
- Freshsales → Google BigQuery
- Copper → Google BigQuery
- Insightly → Google BigQuery
- Google Sheets → Google BigQuery
- Close → Google BigQuery
- Nimble → Google BigQuery
- ActiveCampaign → Google BigQuery
- ClickUp → Google BigQuery
- Google Ads → Google BigQuery
- Google Analytics → Google BigQuery
- Twitter/X Ads → Google BigQuery
- LinkedIn Ads → Google BigQuery
Early access
Connect Microsoft Dynamics 365 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.