Skip to content
Data warehouse ⇄ ERP

BigQuery to Dynamics 365 Business Central integration — real-time, two-way sync

Keep BigQuery and Dynamics 365 Business Central in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect BigQuery and Dynamics 365 Business Central

Put Dynamics 365 Business Central's records in BigQuery as live tables for reporting and analysis, without extract jobs, and write results back where Dynamics 365 Business Central can use them.

Finance and operations teams sync Dynamics 365 Business Central with BigQuery to report on the ERP without querying it directly. Customers, Sales Orders, and Sales Invoices replicate into BigQuery Tables, giving analysts fulfillment and revenue truth in the same warehouse as marketing and product data.

Stacksync syncs Vendors, Items, Sales Orders, Sales Invoices from Dynamics 365 Business Central into tables in BigQuery continuously, managing API limits and schema drift along the way. The connection is bi-directional, so values computed in BigQuery can be written back to fields in Dynamics 365 Business Central where that is useful.

Common use cases

  • 01 Reconcile Sales Invoices against bank and payment data inside BigQuery at close.
  • 02 Rank Vendors by Purchase Order spend across entities in one BigQuery Project.
  • 03 Blend Customers and Sales Orders with web analytics in BigQuery for demand forecasting.
  • 04 Feed ML feature tables in BigQuery from operational systems on a continuous schedule

Common sync patterns

Order-to-cash reporting

Business Central Sales Orders and Sales Invoices sync to partitioned BigQuery Tables for revenue and aging analysis.

Procurement analytics

Purchase Orders and Vendors land in a BigQuery Dataset to track spend by supplier.

Inventory visibility

Business Central Items replicate to BigQuery for demand and stock-turn queries.

What you can sync between BigQuery and Dynamics 365 Business Central

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

BigQuery objects Dynamics 365 Business Central objects How this pairing syncs
Tables The syncable unit: only tables can be synced per the Stacksync docs. Purchase Orders Procurement documents exchanged with supplier-facing systems. Tables is specific to BigQuery and Purchase Orders to Dynamics 365 Business Central — each maps to any object or custom field on the other side.
Partitioned tables Synced like regular tables; partition columns map to target fields. General Ledger Entries Posted financial transactions read for reporting; posted entries are immutable. Partitioned tables is specific to BigQuery and General Ledger Entries to Dynamics 365 Business Central — each maps to any object or custom field on the other side.
Clustered tables Supported; clustering is transparent to the sync. Journals Staging records for financial postings created by integrations before posting. Clustered tables is specific to BigQuery and Journals to Dynamics 365 Business Central — each maps to any object or custom field on the other side.
Datasets Organizational container — you pick which dataset’s tables to sync. Dimensions Analytical tags (department, project) that syncs preserve for reporting integrity. Datasets is specific to BigQuery and Dimensions to Dynamics 365 Business Central — each maps to any object or custom field on the other side.
Projects Connection scope: the service account grants access per project. Payments Customer and vendor payment records reconciled against invoices. Projects is specific to BigQuery and Payments to Dynamics 365 Business Central — each maps to any object or custom field on the other side.

How changes propagate between BigQuery and Dynamics 365 Business Central

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

BigQuery Dynamics 365 Business Central Sub-second propagation

DetectionChanges in BigQuery are captured at the source via change data capture — no polling loop against its API. Real-time notification service deployed into your Google Cloud project: Eventarc ("a notification service that enables real-time updates to happen").

DeliveryEach detected change is written to Dynamics 365 Business Central through its API, with automatic retries and rate-limit backoff.

Dynamics 365 Business Central BigQuery Sub-second propagation

DetectionDynamics 365 Business Central notifies Stacksync of record changes through webhook events. API webhooks (change notifications on subscribed entities) plus polling on lastModifiedDateTime.

DeliveryEach detected change is applied to BigQuery as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • BigQuery: Subject to Google Cloud quotas on queries, DML, and streaming; DML is supported but the platform favors append-heavy batch and streaming loads over row-at-a-time writes.
What ships with BigQuery ⇄ Dynamics 365 Business Central

Connect BigQuery and Dynamics 365 Business Central for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every BigQuery–Dynamics 365 Business Central connection.

Real-time

Two-way sync

Changes in BigQuery or Dynamics 365 Business Central instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever BigQuery or Dynamics 365 Business Central data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single BigQuery or Dynamics 365 Business Central record.

Observability

Monitoring

Track your BigQuery ⇄ Dynamics 365 Business Central sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between BigQuery and Dynamics 365 Business Central.

How the BigQuery and Dynamics 365 Business Central connectors work

BigQuery

Integration surface
GoogleSQL via the BigQuery REST API, client libraries, JDBC/ODBC drivers, and the Storage Read/Write APIs
Authentication
Google Cloud service account: create a dedicated service account, grant roles (BigQuery Data Editor, BigQuery Job User, Cloud Functions Service Agent, Cloud Run Developer, Eventarc Event Receiver
Change detection
Real-time notification service deployed into your Google Cloud project: Eventarc ("a notification service that enables real-time updates to happen") with a Cloud Run "secure portal for real-time notification service in
Capabilities
read · write · CDC
Rate limits
Subject to Google Cloud quotas on queries, DML, and streaming; DML is supported but the platform favors append-heavy batch and streaming loads over row-at-a-time writes
BigQuery setup guide

Dynamics 365 Business Central

Integration surface
REST API built on OData v4 (standard API v2.0), extensible with custom API pages in AL
Authentication
OAuth 2.0 via Microsoft Entra ID
Change detection
API webhooks (change notifications on subscribed entities) plus polling on lastModifiedDateTime
Capabilities
read · write · webhooks
How it works

How to connect BigQuery to Dynamics 365 Business Central — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate BigQuery and Dynamics 365 Business Central with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    BigQuery connected
    Dynamics 365 Business Central connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the BigQuery and Dynamics 365 Business Central objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · BigQuery ⇄ Dynamics 365 Business Central
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    BigQuery Dynamics 365 Business Central
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

BigQuery and Dynamics 365 Business Central integration FAQ

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
CSA STAR
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.