Real-time
Two-way sync
Changes in DuckDB or Sage 100 instantly reflect in both systems. No stale data, no manual imports.
Database ⇄ ERP
DuckDB to Sage 100 integration — real-time, two-way sync
Keep DuckDB and Sage 100 in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
- SOC 2 and 6 other compliance frameworks
- POC with real engineers in minutes
Adopted by fast-scaling companies moving mission-critical data in real time
Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect DuckDB and Sage 100
Give your engineers Sage 100's data in DuckDB: read it with normal queries, write back through the sync, and skip the ERP API entirely.
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 Journal Entries, Customers, Vendors, Inventory Items from Sage 100 into DuckDB and keeps both sides consistent in real time. Whatever Sage 100 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 Sage 100 with its validations respected.
Common use cases
- 01 Sync SaaS data to Parquet on object storage and query it with DuckDB without standing up a warehouse.
- 02 Push aggregates computed in DuckDB out to a CRM or business tools so analysis results reach operational systems.
- 03 Replicate GL and sales history to a warehouse or Postgres database for reporting off the on-premise system.
- 04 Sync customers, invoices, and payment status into a CRM so sales sees AR standing without opening the ERP.
Common sync patterns
React to ERP changes
Updates in Sage 100 arrive as row changes in DuckDB, so jobs and triggers can respond as the business record changes.
Where Sage 100 is the HR system of record: people data for internal systems
Worker and org records stay current in DuckDB for provisioning, access, and reporting systems that read from the database.
Controlled write-back
Choose exactly which tables and fields may flow from DuckDB back into Sage 100, keeping the ERP authoritative.
What you can sync between DuckDB and Sage 100
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 | Sage 100 objects | How this pairing syncs | |
|---|---|---|---|
| Attached databases Additional database files or external systems attached into one session for cross-source queries. | Sales Orders Order headers and lines, the usual write target for web and EDI orders. | Attached databases is specific to DuckDB and Sales Orders to Sage 100 — each maps to any object or custom field on the other side. | |
| Database files Single-file .duckdb databases that jobs read and write directly on disk or object storage. | AR Invoices Billing documents synced outward for payment status and revenue reporting. | Database files is specific to DuckDB and AR Invoices to Sage 100 — each maps to any object or custom field on the other side. | |
| Schemas Namespaces within a database used to organize tables in sync outputs. | Purchase Orders Procurement documents read for spend and receiving workflows. | Schemas is specific to DuckDB and Purchase Orders to Sage 100 — each maps to any object or custom field on the other side. | |
| Tables Columnar tables created via SQL; the destination for materialized sync data. | GL Accounts Chart of accounts read for mapping transactions in finance integrations. | Tables is specific to DuckDB and GL Accounts to Sage 100 — each maps to any object or custom field on the other side. | |
| Views SQL views used to shape or filter data for downstream consumers. | Journal Entries Posted GL activity replicated to warehouses for FP&A. | Views is specific to DuckDB and Journal Entries to Sage 100 — each maps to any object or custom field on the other side. | |
| External files (Parquet/CSV/JSON) Files DuckDB queries in place without loading, common as a sync interchange format. | Customers AR customer master records synced to CRMs for account and credit visibility. | External files (Parquet/CSV/JSON) is specific to DuckDB and Customers to Sage 100 — each maps to any object or custom field on the other side. |
How changes propagate between DuckDB and Sage 100
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.
DuckDB Sage 100 Interval-based propagation
DetectionStacksync polls DuckDB for changes on an incremental schedule, reading only records changed since the previous pass. Polling or full re-reads.
DeliveryEach detected change is applied to Sage 100 as a row-level write, with types converted between the two schemas.
Sage 100 DuckDB Interval-based propagation
DetectionStacksync polls Sage 100 for changes on an incremental schedule, reading only records changed since the previous pass. Scheduled polling.
DeliveryEach detected change is applied to DuckDB as a row-level write, with types converted between the two schemas.
Rate-limit considerations
- DuckDB: No API rate limits; throughput is bounded by local compute and I/O.
What ships with DuckDB ⇄ Sage 100
Connect DuckDB and Sage 100 for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every DuckDB–Sage 100 connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever DuckDB or Sage 100 data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
At scale
Event queues
Handle millions of events per minute without losing a single DuckDB or Sage 100 record.
Observability
Monitoring
Track your DuckDB ⇄ Sage 100 sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between DuckDB and Sage 100.
How the DuckDB and Sage 100 connectors work
DuckDB
- Integration surface
- 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)
- Change detection
- Polling or full re-reads; no change feed or transaction log API
- Capabilities
- read · write
- Rate limits
- No API rate limits; throughput is bounded by local compute and I/O
Sage 100
- Integration surface
- ODBC (ProvideX driver) for reads; Business Object Interface (BOI) or Sage-provided web services for writes
- Authentication
- Sage 100 company and user credentials; ODBC DSN credentials for direct reads
- Change detection
- Scheduled polling; no webhooks or change log on the integration surface
- Capabilities
- read · write
How it works
How to connect DuckDB to Sage 100 — three steps, no code
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.
- 01
Connect your apps
Authenticate DuckDB and Sage 100 with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
DuckDB
connected
Sage 100
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the DuckDB and Sage 100 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.
objects · DuckDB ⇄ Sage 100Customers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
DuckDB Sage 100Company company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
DuckDB and Sage 100 integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between DuckDB and Sage 100: 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.
-
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 Sage 100: React to ERP changes; Where Sage 100 is the HR system of record: people data for internal systems; Controlled write-back. Updates in Sage 100 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). Sage 100: ODBC (ProvideX driver) for reads; Business Object Interface (BOI) or Sage-provided web services for writes. Authentication: Sage 100 company and user credentials; ODBC DSN credentials for direct reads. Stacksync manages authentication, retries, and rate limits on both sides.
-
DuckDB: It queries Parquet, CSV, and JSON files directly without importing them, which makes file-based exchange a natural sync pattern. Sage 100: There is no event or webhook surface, so integrations detect changes with scheduled polling and often run during off-hours to avoid contention on the on-prem server. Stacksync's field mapping accounts for these differences between DuckDB and Sage 100 without custom code.
-
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means DuckDB and Sage 100 records are not retained after a sync operation.
SECURITY
Security teams trust Stacksync
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.
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS
SSO & SCIM
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Alerts
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Secure connection options
Securely connects to your systems with:
Related integrations
Every pair below is a real-time, two-way sync. Search all 449 integrations available for DuckDB and Sage 100.
Popular · 5 of 449
-
DuckDB ⇄ Dynamics 365 Business Central -
DuckDB ⇄ SAP Business ByDesign -
Sage 100 ⇄ InterSystems IRIS -
Sage 100 ⇄ MarkLogic -
Sage 100 ⇄ Neo4j
No integrations match .
