Two-way sync
Changes in DuckDB or IQMS (DELMIAworks) instantly reflect in both systems. No stale data, no manual imports.
Keep DuckDB and IQMS (DELMIAworks) 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 Shipments, Quality Records, Production Monitoring Data, Sales Orders from IQMS (DELMIAworks) into DuckDB and keeps both sides consistent in real time. Whatever IQMS (DELMIAworks) 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 IQMS (DELMIAworks) with its validations respected.
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 IQMS (DELMIAworks), keeping the ERP authoritative.
Records from IQMS (DELMIAworks) live in DuckDB as ordinary tables or collections, joinable with the rest of your data.
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 | IQMS (DELMIAworks) objects | |
|---|---|---|
| External files (Parquet/CSV/JSON) Files DuckDB queries in place without loading, common as a sync interchange format. | Shipments Ship confirmations flow to customer-facing systems for order tracking. | |
| Attached databases Additional database files or external systems attached into one session for cross-source queries. | Quality Records Quality and compliance data consolidates into reporting systems. | |
| Database files Single-file .duckdb databases that jobs read and write directly on disk or object storage. | Production Monitoring Data Machine and process data from the MES layer feeds BI dashboards. | |
| Schemas Namespaces within a database used to organize tables in sync outputs. | Sales Orders Order headers and lines sync with CRM and EDI channels to remove re-keying. | |
| Tables Columnar tables created via SQL; the destination for materialized sync data. | Work Orders Production order status feeds sales tools so quoted lead times reflect the floor. | |
| Views SQL views used to shape or filter data for downstream consumers. | Items & Inventory Item and on-hand data drive availability in commerce and planning systems. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every DuckDB–IQMS (DELMIAworks) connection.
Changes in DuckDB or IQMS (DELMIAworks) instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever DuckDB or IQMS (DELMIAworks) 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 IQMS (DELMIAworks) record.
Track your DuckDB ⇄ IQMS (DELMIAworks) sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between DuckDB and IQMS (DELMIAworks).
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 IQMS (DELMIAworks) 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 IQMS (DELMIAworks) 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 IQMS (DELMIAworks): authenticate both systems, choose the objects to sync (such as DuckDB's External files (Parquet/CSV/JSON) and Attached databases), map fields visually, and changes propagate both ways in milliseconds — no code required.
On the DuckDB side: External files (Parquet/CSV/JSON), Attached databases, Database files, Schemas, plus custom fields where DuckDB exposes them. On the IQMS (DELMIAworks) side: Shipments, Quality Records, Production Monitoring Data, Sales Orders. 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 IQMS (DELMIAworks): Where IQMS (DELMIAworks) is the HR system of record: people data for internal systems; Controlled write-back; Read ERP records with a query. Worker and org records stay current in DuckDB for provisioning, access, and reporting systems that read from the database.
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). IQMS (DELMIAworks): Database-level access and vendor integration interfaces; no broadly documented public REST API. Authentication: Database credentials or vendor-issued integration credentials. 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. IQMS (DELMIAworks): The product has historically been deployed on an Oracle database, so integrations often read from the database tier where a public API does not cover the needed data. Stacksync's field mapping accounts for these differences between DuckDB and IQMS (DELMIAworks) 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 IQMS (DELMIAworks).