Gong to Microsoft Power BI Integration

How Datrise loads Gong into Microsoft Power BI

Datrise syncs Gong's calls, transcripts, deals, users, trackers, and call topics into Microsoft Power BI as star-schema-friendly tables for an Import or DirectQuery dataset. Flexible or custom fields land in flattened columns (nested fields expanded), and timestamps such as created, updated, and status changes are typed as date/time columns with a date table.

Sync is incremental: Datrise uses incremental-refresh windows aligned to Power BI's RangeStart/RangeEnd, so re-runs update only what changed. Date-partitioned fact tables matching incremental-refresh policies. Power BI measures and relationships live in the .pbix model, so Datrise keeps the underlying tables stable and star-schema-shaped.

Ideal for Microsoft-stack self-serve reporting.

Endpoints

Gong: Revenue intelligence from recorded sales calls.

Microsoft Power BI: Microsoft business intelligence with datasets, reports, and semantic models.

How Gong entities map to Microsoft Power BI

Gong entity	Microsoft Power BI object	Notes
calls	`gong_calls`	id PK · custom fields → flattened columns (nested fields expanded)
transcripts	`gong_transcripts`	id PK · linked to gong_calls
deals	`gong_deals`	id PK · linked to gong_calls
users	`gong_users`	id PK · linked to gong_calls

FAQ

How does Datrise handle Gong's custom fields in Microsoft Power BI?

Flexible values are stored as flattened columns (nested fields expanded), so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Microsoft Power BI types.

How does the Gong to Microsoft Power BI sync stay up to date?

It runs incrementally — Datrise uses incremental-refresh windows aligned to Power BI's RangeStart/RangeEnd.

Related pipelines

Early access

Connect Gong to Microsoft Power BI 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.