Two-way sync
Changes in Acumatica or MotherDuck instantly reflect in both systems. No stale data, no manual imports.
Keep Acumatica and MotherDuck in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Teams sync Acumatica into MotherDuck to analyze ERP data with warehouse-scale SQL. Invoices, Sales Orders, and Purchase Orders land as Tables in MotherDuck Schemas, ready for DuckDB queries, dashboards, and sharing without exporting from Acumatica.
Stacksync syncs Sales Orders, Invoices, Purchase Orders, Stock Items from Acumatica into tables in MotherDuck continuously, managing API limits and schema drift along the way. The connection is bi-directional, so values computed in MotherDuck can be written back to fields in Acumatica where that is useful.
Acumatica Invoices and Sales Orders sync to MotherDuck Tables for margin and revenue queries across periods.
Purchase Orders and Vendors land in a MotherDuck Schema for spend reporting.
synced Customer and Stock Item Tables are published as Database Shares so other teams query them without new pipelines.
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 | MotherDuck objects | How this pairing syncs | |
|---|---|---|---|
| Customers AR master data synced with CRMs and billing tools. | Database Shares Read-only copies of a database shared with other users or teams. | Customers is specific to Acumatica and Database Shares to MotherDuck — each maps to any object or custom field on the other side. | |
| Vendors Supplier records aligned with procurement and AP automation. | Attached Local DuckDB Databases Local files attached alongside cloud databases for hybrid queries. | Vendors is specific to Acumatica and Attached Local DuckDB Databases to MotherDuck — each maps to any object or custom field on the other side. | |
| Sales Orders Order documents created from e-commerce and CRM systems, read back for fulfillment status. | Databases Cloud-hosted DuckDB databases that scope a sync's reads and writes. | Sales Orders is specific to Acumatica and Databases to MotherDuck — each maps to any object or custom field on the other side. | |
| Invoices AR and AP billing documents synced for payment tracking and CRM visibility. | Schemas Namespaces within a database used to organize synced tables. | Invoices is specific to Acumatica and Schemas to MotherDuck — each maps to any object or custom field on the other side. | |
| Purchase Orders Procurement documents exchanged with supplier-facing systems. | Tables The main landing target for synced records and source for analysis. | Purchase Orders is specific to Acumatica and Tables to MotherDuck — each maps to any object or custom field on the other side. | |
| Stock Items Inventory master data with quantities shared with external sales channels. | Views Modeled projections used as outbound sync sources. | Stock Items is specific to Acumatica and Views to MotherDuck — 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 MotherDuck as a row-level write, with types converted between the two schemas.
DetectionStacksync polls MotherDuck for changes on an incremental schedule, reading only records changed since the previous pass. Polling.
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–MotherDuck connection.
Changes in Acumatica or MotherDuck instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Acumatica or MotherDuck 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 MotherDuck record.
Track your Acumatica ⇄ MotherDuck sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Acumatica and MotherDuck.
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 MotherDuck 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 MotherDuck 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 MotherDuck: authenticate both systems, choose the objects to sync (such as Acumatica's Customers and Vendors), map fields visually, and changes propagate both ways in milliseconds — no code required.
Change detection on Acumatica: Push notifications configurable on data changes, plus polling on LastModifiedDateTime fields. On MotherDuck: Polling; no log-based CDC or webhook surface is exposed. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the MotherDuck side: Tables, Views, Database Shares, Attached Local DuckDB Databases, plus custom fields where MotherDuck 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.
Common patterns for Acumatica and MotherDuck: Revenue analytics; Procurement analysis; Shared ERP datasets. Acumatica Invoices and Sales Orders sync to MotherDuck Tables for margin and revenue queries across periods.
Acumatica: Contract-based REST API (JSON over versioned endpoints), plus SOAP web services and OData access to Generic Inquiries. Authentication: OAuth 2.0 or cookie-based session login with Acumatica credentials. MotherDuck: SQL through DuckDB clients and drivers using a MotherDuck (md:) connection. Authentication: Access token created in MotherDuck (Settings > General > Create Token), pasted into Stacksync; database name and schema configurable if not using defaults. Stacksync manages authentication, retries, and rate limits on both sides.
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 459 integrations available for Acumatica and MotherDuck.