Two-way sync
Changes in DuckDB or Epicor ERP instantly reflect in both systems. No stale data, no manual imports.
Keep DuckDB and Epicor ERP 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 Purchase orders, Jobs, Quotes, AR invoices from Epicor ERP into DuckDB and keeps both sides consistent in real time. Whatever Epicor ERP 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 Epicor ERP with its validations respected.
Updates in Epicor ERP 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.
Choose exactly which tables and fields may flow from DuckDB back into Epicor ERP, keeping the ERP authoritative.
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.
| DuckDB objects | Epicor ERP objects | |
|---|---|---|
| Attached databases Additional database files or external systems attached into one session for cross-source queries. | Suppliers Vendor masters kept aligned with procurement and AP automation tools. | |
| Database files Single-file .duckdb databases that jobs read and write directly on disk or object storage. | Parts Item masters that anchor inventory, BOM, and order line syncs. | |
| Schemas Namespaces within a database used to organize tables in sync outputs. | Sales orders Created from won CRM opportunities; status and line changes sync back out. | |
| Tables Columnar tables created via SQL; the destination for materialized sync data. | Purchase orders Synced with procurement systems and matched against receipts. | |
| Views SQL views used to shape or filter data for downstream consumers. | Jobs Production jobs whose status feeds shop-floor dashboards and delivery-date updates. | |
| External files (Parquet/CSV/JSON) Files DuckDB queries in place without loading, common as a sync interchange format. | Quotes Estimates that pair with CRM opportunities during the sales cycle. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every DuckDB–Epicor ERP connection.
Changes in DuckDB or Epicor ERP instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever DuckDB or Epicor ERP data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single DuckDB or Epicor ERP record.
Track your DuckDB ⇄ Epicor ERP sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between DuckDB and Epicor ERP.
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 DuckDB and Epicor ERP 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 DuckDB and Epicor ERP 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 DuckDB and Epicor ERP: authenticate both systems, choose the objects to sync (such as DuckDB's Attached databases and Database files), map fields visually, and changes propagate both ways in milliseconds — no code required.
On the DuckDB side: Schemas, Tables, Views, External files (Parquet/CSV/JSON), plus custom fields where DuckDB exposes them. On the Epicor ERP side: Purchase orders, Jobs, Quotes, AR invoices. 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 DuckDB and Epicor ERP: React to ERP changes; Where Epicor ERP is the HR system of record: people data for internal systems; Controlled write-back. Updates in Epicor ERP arrive as row changes in DuckDB, so jobs and triggers can respond as the business record changes.
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). Epicor ERP: REST API (OData) over Epicor business objects, plus BAQ (Business Activity Query) endpoints. Authentication: API key combined with basic or token authentication, depending on version and deployment. Stacksync manages authentication, retries, and rate limits on both sides.
DuckDB: Concurrency is single-writer: one process holds write access to a database file at a time, which shapes how sync jobs schedule writes. Epicor ERP: BAQs (Business Activity Queries) can be exposed as read endpoints, letting integrations query joined ERP data without composing multiple object calls. Stacksync's field mapping accounts for these differences between DuckDB and Epicor ERP 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 DuckDB and Epicor ERP.