Skip to content
Data warehouse ⇄ ERP

BigQuery to SAP Business One integration — real-time, two-way sync

Keep BigQuery and SAP Business One 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 SAP Business One

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

Operations and finance teams at SAP Business One shops sync the ERP into BigQuery to report on the business without querying the ERP directly. Sales Orders, A/R Invoices, and Business Partners replicate into BigQuery Tables, giving analysts a fulfillment and billing source of truth in the warehouse.

Stacksync syncs Purchase Orders, Deliveries, Journal Entries, Warehouses from SAP Business One 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 SAP Business One where that is useful.

Common use cases

  • 01 Join Business Partners with CRM and marketing data already in BigQuery.
  • 02 Track Deliveries against Sales Orders in the warehouse to measure fulfillment performance.
  • 03 Build margin analysis on Items and A/R Invoices without loading SAP Business One.
  • 04 Feed ML feature tables in BigQuery from operational systems on a continuous schedule

Common sync patterns

Order-to-cash reporting

Sales Orders and A/R Invoices sync into partitioned BigQuery Tables for revenue and DSO analysis.

Inventory and item analytics

Items and Deliveries land in a BigQuery Dataset for stock-movement reporting.

Procurement analysis

Purchase Orders replicate to clustered BigQuery Tables for supplier spend review.

What you can sync between BigQuery and SAP Business One

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 SAP Business One objects How this pairing syncs
Partitioned tables Synced like regular tables; partition columns map to target fields. Price Lists Pricing data synced to quoting and e-commerce platforms. Partitioned tables is specific to BigQuery and Price Lists to SAP Business One — each maps to any object or custom field on the other side.
Clustered tables Supported; clustering is transparent to the sync. Activities CRM-style tasks and interactions aligned with external sales tools. Clustered tables is specific to BigQuery and Activities to SAP Business One — each maps to any object or custom field on the other side.
Datasets Organizational container — you pick which dataset’s tables to sync. Business Partners Combined customer, vendor, and lead master records; the anchor object for most syncs. Datasets is specific to BigQuery and Business Partners to SAP Business One — each maps to any object or custom field on the other side.
Projects Connection scope: the service account grants access per project. Items Product master data including inventory levels, aligned with e-commerce and warehouse systems. Projects is specific to BigQuery and Items to SAP Business One — each maps to any object or custom field on the other side.
Tables The syncable unit: only tables can be synced per the Stacksync docs. Sales Orders Order documents with header and line structure created from external channels. Tables is specific to BigQuery and Sales Orders to SAP Business One — each maps to any object or custom field on the other side.

How changes propagate between BigQuery and SAP Business One

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 SAP Business One 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 SAP Business One through its API, with automatic retries and rate-limit backoff.

SAP Business One BigQuery Interval-based propagation

DetectionStacksync polls SAP Business One for changes on an incremental schedule, reading only records changed since the previous pass. Polling on update timestamps.

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 ⇄ SAP Business One

Connect BigQuery and SAP Business One for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every BigQuery–SAP Business One connection.

Real-time

Two-way sync

Changes in BigQuery or SAP Business One instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever BigQuery or SAP Business One 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 SAP Business One record.

Observability

Monitoring

Track your BigQuery ⇄ SAP Business One 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 SAP Business One.

How the BigQuery and SAP Business One 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

SAP Business One

Integration surface
Service Layer, a REST API based on OData, plus the legacy COM-based DI API
Authentication
Session-based login with company database, username, and password against the Service Layer
Change detection
Polling on update timestamps; no general-purpose webhook mechanism on the standard surface
Capabilities
read · write
How it works

How to connect BigQuery to SAP Business One — 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 SAP Business One 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
    SAP Business One connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the BigQuery and SAP Business One 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 ⇄ SAP Business One
    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 SAP Business One
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

BigQuery and SAP Business One 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
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:

Related integrations

Every pair below is a real-time, two-way sync. Search all 550 integrations available for BigQuery and SAP Business One.

Popular · 8 of 550
Coworkers laughing in front of a laptop in a casual office setting

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