Real-time
Two-way sync
Changes in Sage 100 or Starburst Enterprise instantly reflect in both systems. No stale data, no manual imports.
ERP ⇄ Data warehouse
Sage 100 to Starburst Enterprise integration — real-time, two-way sync
Keep Sage 100 and Starburst Enterprise 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 Sage 100 and Starburst Enterprise
Put Sage 100's records in Starburst Enterprise as live tables for reporting and analysis, without extract jobs, and write results back where Sage 100 can use them.
ERP data is some of the most asked-for data in the warehouse and some of the hardest to get: the record types are many, the APIs are strict, and extract jobs are brittle. Whether Sage 100 carries financials, operations, workforce data, or all three, the analysis belongs in Starburst Enterprise next to everything else the company measures.
Stacksync syncs Purchase Orders, GL Accounts, Journal Entries, Customers from Sage 100 into tables in Starburst Enterprise continuously, managing API limits and schema drift along the way. The connection is bi-directional, so values computed in Starburst Enterprise can be written back to fields in Sage 100 where that is useful.
Common use cases
- 01 Read federated views that join warehouse, lake, and database tables, then sync the result into operational tools like a CRM
- 02 Expose Iceberg or Hive lake tables to sync jobs through one SQL endpoint without moving the data first
- 03 Publish item, pricing, and on-hand inventory to online catalogs on a schedule.
- 04 Replicate GL and sales history to a warehouse or Postgres database for reporting off the on-premise system.
Common sync patterns
Where Sage 100 holds the books: finance reporting from live data
Financial records land in Starburst Enterprise as they change, so period-end reporting queries current numbers rather than last night's extract.
Where Sage 100 is the HR system of record: workforce analytics
Worker and organization data syncs into Starburst Enterprise for headcount, cost, and planning analysis alongside other company data.
Where Sage 100 runs operations: order and supply analysis
Operational records become queryable tables in Starburst Enterprise, joinable with sales and finance data.
What you can sync between Sage 100 and Starburst Enterprise
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.
| Sage 100 objects | Starburst Enterprise objects | How this pairing syncs | |
|---|---|---|---|
| Vendors AP vendor master records synced with procurement and payment tools. | Materialized views Precomputed results that make repeated sync reads cheaper. | Vendors is specific to Sage 100 and Materialized views to Starburst Enterprise — each maps to any object or custom field on the other side. | |
| Inventory Items Item master with pricing and quantities, synced to e-commerce catalogs. | Columns Typed per the Trino type system, mapped from each source's native types. | Inventory Items is specific to Sage 100 and Columns to Starburst Enterprise — each maps to any object or custom field on the other side. | |
| Sales Orders Order headers and lines, the usual write target for web and EDI orders. | Catalogs Each catalog maps to a connector (Iceberg, Hive, PostgreSQL, and others) exposing an external source. | Sales Orders is specific to Sage 100 and Catalogs to Starburst Enterprise — each maps to any object or custom field on the other side. | |
| AR Invoices Billing documents synced outward for payment status and revenue reporting. | Schemas Namespaces within a catalog, mirroring the underlying source's databases or schemas. | AR Invoices is specific to Sage 100 and Schemas to Starburst Enterprise — each maps to any object or custom field on the other side. | |
| Purchase Orders Procurement documents read for spend and receiving workflows. | Tables Queryable relations; writes pass through to sources whose connectors support them. | Purchase Orders is specific to Sage 100 and Tables to Starburst Enterprise — each maps to any object or custom field on the other side. | |
| GL Accounts Chart of accounts read for mapping transactions in finance integrations. | Views Engine-level SQL views used to shape federated data before syncing it out. | GL Accounts is specific to Sage 100 and Views to Starburst Enterprise — each maps to any object or custom field on the other side. |
How changes propagate between Sage 100 and Starburst Enterprise
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.
Sage 100 Starburst Enterprise 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 Starburst Enterprise as a row-level write, with types converted between the two schemas.
Starburst Enterprise Sage 100 Interval-based propagation
DetectionStacksync polls Starburst Enterprise for changes on an incremental schedule, reading only records changed since the previous pass. Query-based polling.
DeliveryEach detected change is applied to Sage 100 as a row-level write, with types converted between the two schemas.
Rate-limit considerations
- Starburst Enterprise: Throughput is governed by cluster sizing and resource groups rather than API quotas.
What ships with Sage 100 ⇄ Starburst Enterprise
Connect Sage 100 and Starburst Enterprise for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Sage 100–Starburst Enterprise connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Sage 100 or Starburst Enterprise 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 Sage 100 or Starburst Enterprise record.
Observability
Monitoring
Track your Sage 100 ⇄ Starburst Enterprise sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Sage 100 and Starburst Enterprise.
How the Sage 100 and Starburst Enterprise connectors work
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
Starburst Enterprise
- Integration surface
- ANSI SQL over JDBC/ODBC drivers and the Trino client REST protocol
- Authentication
- Deployment-dependent: username/password, LDAP, OAuth 2.0, or Kerberos
- Change detection
- Query-based polling; Starburst is a query engine and exposes no change log of its own
- Capabilities
- read · write
- Rate limits
- Throughput is governed by cluster sizing and resource groups rather than API quotas
How it works
How to connect Sage 100 to Starburst Enterprise — 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 Sage 100 and Starburst Enterprise with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Sage 100
connected
Starburst Enterprise
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Sage 100 and Starburst Enterprise 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 · Sage 100 ⇄ Starburst EnterpriseCustomers 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.
Sage 100 Starburst EnterpriseCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Sage 100 and Starburst Enterprise integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Sage 100 and Starburst Enterprise: authenticate both systems, choose the objects to sync (such as Sage 100's Vendors and Inventory Items), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Common patterns for Sage 100 and Starburst Enterprise: Where Sage 100 holds the books: finance reporting from live data; Where Sage 100 is the HR system of record: workforce analytics; Where Sage 100 runs operations: order and supply analysis. Financial records land in Starburst Enterprise as they change, so period-end reporting queries current numbers rather than last night's extract.
-
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. Starburst Enterprise: ANSI SQL over JDBC/ODBC drivers and the Trino client REST protocol. Authentication: Deployment-dependent: username/password, LDAP, OAuth 2.0, or Kerberos. Stacksync manages authentication, retries, and rate limits on both sides.
-
Starburst Enterprise: The engine stores no data itself; reads and writes pass through to the underlying sources, and write support depends on each connector. Sage 100: Writes should go through the Business Object Interface rather than direct file access, so module validation and GL postings are enforced. Stacksync's field mapping accounts for these differences between Sage 100 and Starburst Enterprise 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 Sage 100 and Starburst Enterprise records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Sage 100 and Starburst Enterprise connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Sage 100–Starburst Enterprise integration in-house.
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 437 integrations available for Sage 100 and Starburst Enterprise.
Popular · 5 of 437
-
Sage 100 ⇄ Apache Hive -
Sage 100 ⇄ Apache Impala -
Sage 100 ⇄ Apache Kylin -
Sage 100 ⇄ Apache Pinot -
Starburst Enterprise ⇄ Cin7
No integrations match .
