Two-way sync
Changes in DuckDB or Microsoft Dynamics GP instantly reflect in both systems. No stale data, no manual imports.
Keep DuckDB and Microsoft Dynamics GP 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 Company Databases, Customers, Vendors, Sales Documents (SOP) from Microsoft Dynamics GP into DuckDB and keeps both sides consistent in real time. Whatever Microsoft Dynamics GP 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 Microsoft Dynamics GP with its validations respected.
Choose exactly which tables and fields may flow from DuckDB back into Microsoft Dynamics GP, keeping the ERP authoritative.
Records from Microsoft Dynamics GP live in DuckDB as ordinary tables or collections, joinable with the rest of your data.
Scripts and services read and write the synced tables; Stacksync handles the Microsoft Dynamics GP interface, limits, and retries.
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 | Microsoft Dynamics GP objects | |
|---|---|---|
| Attached databases Additional database files or external systems attached into one session for cross-source queries. | Vendors Payables master records aligned with procurement and AP automation. | |
| Database files Single-file .duckdb databases that jobs read and write directly on disk or object storage. | Sales Documents (SOP) Quotes, orders, and invoices created via eConnect from web or CRM orders. | |
| Schemas Namespaces within a database used to organize tables in sync outputs. | Purchase Orders (POP) Procurement documents reconciled with receiving and vendor systems. | |
| Tables Columnar tables created via SQL; the destination for materialized sync data. | Inventory Items (IV) Item master and quantity data mirrored to ecommerce and planning systems. | |
| Views SQL views used to shape or filter data for downstream consumers. | GL Accounts & Journal Entries Financial ledger data replicated to warehouses for consolidated reporting. | |
| External files (Parquet/CSV/JSON) Files DuckDB queries in place without loading, common as a sync interchange format. | Receivables & Payables Transactions Open and historical AR/AP transactions read for cash and aging reporting. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every DuckDB–Microsoft Dynamics GP connection.
Changes in DuckDB or Microsoft Dynamics GP instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever DuckDB or Microsoft Dynamics GP 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 Microsoft Dynamics GP record.
Track your DuckDB ⇄ Microsoft Dynamics GP sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between DuckDB and Microsoft Dynamics GP.
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 Microsoft Dynamics GP 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 Microsoft Dynamics GP 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 Microsoft Dynamics GP: 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.
Change detection on DuckDB: Polling or full re-reads; no change feed or transaction log API. On Microsoft Dynamics GP: SQL Server change tracking or log-based CDC on the company database, or polling on row timestamps. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the DuckDB side: External files (Parquet/CSV/JSON), Attached databases, Database files, Schemas, plus custom fields where DuckDB exposes them. On the Microsoft Dynamics GP side: Company Databases, Customers, Vendors, Sales Documents (SOP). 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 Microsoft Dynamics GP: Controlled write-back; Read ERP records with a query; Internal tools and automations without API code. Choose exactly which tables and fields may flow from DuckDB back into Microsoft Dynamics GP, keeping the ERP authoritative.
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). Microsoft Dynamics GP: SQL Server database access plus the eConnect stored-procedure API; Web Services for GP on some deployments. Authentication: SQL Server credentials or Windows authentication. 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 386 integrations available for DuckDB and Microsoft Dynamics GP.