Two-way sync
Changes in Acumatica or BigQuery instantly reflect in both systems. No stale data, no manual imports.
Keep Acumatica and BigQuery in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Syncing Acumatica into BigQuery makes ERP activity part of the company's analytics warehouse. Sales Orders, Invoices, and Stock Items flow into BigQuery Tables inside dedicated Datasets, where they join marketing, product, and finance data for reporting at warehouse scale.
Stacksync syncs Sales Orders, Invoices, Purchase Orders, Stock Items from Acumatica 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 Acumatica where that is useful.
Acumatica Invoices and Sales Orders sync into Partitioned tables for date-ranged revenue analysis
Acumatica Stock Items land in Clustered tables for fast SKU-level queries across Projects
Acumatica Purchase Orders and Vendors sync into a Dataset for procurement dashboards
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.
| Acumatica objects | BigQuery objects | How this pairing syncs | |
|---|---|---|---|
| Projects Project cost and billing structures synced with delivery tools. | Projects Connection scope: the service account grants access per project. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Payments Customer payment records reconciled against invoices from payment platforms. | Tables The syncable unit: only tables can be synced per the Stacksync docs. | Payments is specific to Acumatica and Tables to BigQuery — each maps to any object or custom field on the other side. | |
| Journal Transactions GL entries replicated into reporting databases. | Partitioned tables Synced like regular tables; partition columns map to target fields. | Journal Transactions is specific to Acumatica and Partitioned tables to BigQuery — each maps to any object or custom field on the other side. | |
| Opportunities and Cases Built-in CRM records synced with external sales and support tools. | Clustered tables Supported; clustering is transparent to the sync. | Opportunities and Cases is specific to Acumatica and Clustered tables to BigQuery — each maps to any object or custom field on the other side. | |
| Customers AR master data synced with CRMs and billing tools. | Datasets Organizational container — you pick which dataset’s tables to sync. | Customers is specific to Acumatica and Datasets to BigQuery — each maps to any object or custom field on the other side. |
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.
DetectionAcumatica notifies Stacksync of record changes through webhook events. Push notifications configurable on data changes, plus polling on LastModifiedDateTime fields.
DeliveryEach detected change is applied to BigQuery as a row-level write, with types converted between the two schemas.
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 Acumatica through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Acumatica–BigQuery connection.
Changes in Acumatica or BigQuery instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Acumatica or BigQuery data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Acumatica or BigQuery record.
Track your Acumatica ⇄ BigQuery sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Acumatica and BigQuery.
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.
Authenticate Acumatica and BigQuery with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the Acumatica and BigQuery 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Acumatica and BigQuery: authenticate both systems, choose the objects to sync (such as Acumatica's Projects and Payments), map fields visually, and changes propagate both ways in milliseconds — no code required.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Acumatica and BigQuery connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Acumatica–BigQuery integration in-house.
Yes — Stacksync ships production-grade connectors for both Acumatica and BigQuery. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection on Acumatica: Push notifications configurable on data changes, plus polling on LastModifiedDateTime fields. On BigQuery: 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. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the BigQuery side: Partitioned tables, Clustered tables, Datasets, Projects, plus custom fields where BigQuery exposes them. On the Acumatica side: Sales Orders, Invoices, Purchase Orders, Stock Items. Stacksync auto-detects both schemas and converts types between the two systems.
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 552 integrations available for Acumatica and BigQuery.