Two-way sync
Changes in Acumatica or DuckDB instantly reflect in both systems. No stale data, no manual imports.
Keep Acumatica and DuckDB in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
ERP data sits behind interfaces built for the ERP's own modules, not for your internal systems. Teams that need those records, for reporting services, internal tools, or automations, end up writing integration code against a strict API and maintaining it through every upgrade.
Stacksync mirrors Payments, Journal Transactions, Projects, Opportunities and Cases from Acumatica into DuckDB and keeps both sides consistent in real time. Whatever Acumatica is the system of record for, whether financials, operations, people, or procurement, those records become rows your code can query, and changes written in DuckDB sync back into Acumatica with its validations respected.
Scripts and services read and write the synced tables; Stacksync handles the Acumatica interface, limits, and retries.
Updates in Acumatica arrive as row changes in DuckDB, so jobs and triggers can respond as the business record changes.
Worker and org records stay current in DuckDB for provisioning, access, and reporting systems that read from the database.
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 | DuckDB objects | |
|---|---|---|
| Opportunities and Cases Built-in CRM records synced with external sales and support tools. | Schemas Namespaces within a database used to organize tables in sync outputs. | |
| Customers AR master data synced with CRMs and billing tools. | Tables Columnar tables created via SQL; the destination for materialized sync data. | |
| Vendors Supplier records aligned with procurement and AP automation. | Views SQL views used to shape or filter data for downstream consumers. | |
| Sales Orders Order documents created from e-commerce and CRM systems, read back for fulfillment status. | External files (Parquet/CSV/JSON) Files DuckDB queries in place without loading, common as a sync interchange format. | |
| Invoices AR and AP billing documents synced for payment tracking and CRM visibility. | Attached databases Additional database files or external systems attached into one session for cross-source queries. | |
| Purchase Orders Procurement documents exchanged with supplier-facing systems. | Database files Single-file .duckdb databases that jobs read and write directly on disk or object storage. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Acumatica–DuckDB connection.
Changes in Acumatica or DuckDB instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Acumatica or DuckDB 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 DuckDB record.
Track your Acumatica ⇄ DuckDB sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Acumatica and DuckDB.
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 DuckDB 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 DuckDB 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 DuckDB: authenticate both systems, choose the objects to sync (such as Acumatica's Opportunities and Cases and Customers), map fields visually, and changes propagate both ways in milliseconds — no code required.
On the DuckDB side: Attached databases, Database files, Schemas, Tables, plus custom fields where DuckDB exposes them. On the Acumatica side: Payments, Journal Transactions, Projects, Opportunities and Cases. 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 DuckDB: Internal tools and automations without API code; React to ERP changes; Where Acumatica is the HR system of record: people data for internal systems. Scripts and services read and write the synced tables; Stacksync handles the Acumatica interface, limits, and retries.
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. DuckDB: In-process SQL engine via client libraries (Python, Node.js, JDBC, CLI); no server or network API by default. Authentication: None built in; access control is file-system level (MotherDuck adds token auth for its hosted service). Stacksync manages authentication, retries, and rate limits on both sides.
DuckDB: DuckDB runs in-process like SQLite; there is no server, so integrations embed the engine or operate on the single-file databases it produces. Acumatica: The contract-based REST API uses versioned endpoints with a defined entity contract, so integrations pin an endpoint version and remain stable across upgrades. Stacksync's field mapping accounts for these differences between Acumatica and DuckDB without custom code.
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 386 integrations available for Acumatica and DuckDB.