Real-time
Two-way sync
Changes in Dremio or Epicor ERP instantly reflect in both systems. No stale data, no manual imports.
Data warehouse ⇄ ERP
Dremio to Epicor ERP integration — real-time, two-way sync
Keep Dremio 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.
- 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 Dremio and Epicor ERP
Put Epicor ERP's records in Dremio as live tables for reporting and analysis, without extract jobs, and write results back where Epicor ERP 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 Epicor ERP carries financials, operations, workforce data, or all three, the analysis belongs in Dremio next to everything else the company measures.
Stacksync syncs Bills of materials, Customers, Suppliers, Parts from Epicor ERP into tables in Dremio continuously, managing API limits and schema drift along the way. The connection is bi-directional, so values computed in Dremio can be written back to fields in Epicor ERP where that is useful.
Common use cases
- 01 Sync curated Dremio views into an operational Postgres so applications get low-latency access to lakehouse data.
- 02 Reverse-ETL aggregates computed over lake data out to CRMs and finance tools for business users.
- 03 Keep supplier and purchase order data synced with procurement or AP automation tools.
- 04 Sync shipment confirmations out to commerce platforms and customer portals as jobs complete.
Common sync patterns
Write-back where Epicor ERP exposes writable fields
Classifications or reference values computed in Dremio sync back onto the corresponding records in Epicor ERP.
Where Epicor ERP holds the books: finance reporting from live data
Financial records land in Dremio as they change, so period-end reporting queries current numbers rather than last night's extract.
Where Epicor ERP is the HR system of record: workforce analytics
Worker and organization data syncs into Dremio for headcount, cost, and planning analysis alongside other company data.
What you can sync between Dremio and Epicor ERP
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.
| Dremio objects | Epicor ERP objects | How this pairing syncs | |
|---|---|---|---|
| Jobs Query execution records useful for monitoring sync workloads. | Jobs Production jobs whose status feeds shop-floor dashboards and delivery-date updates. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Spaces and folders Namespaces that organize virtual datasets and govern access. | Quotes Estimates that pair with CRM opportunities during the sales cycle. | Spaces and folders is specific to Dremio and Quotes to Epicor ERP — each maps to any object or custom field on the other side. | |
| Reflections Materialized accelerations that make repeated extraction queries cheaper. | AR invoices Billing records surfaced in CRM or finance tools for collections visibility. | Reflections is specific to Dremio and AR invoices to Epicor ERP — each maps to any object or custom field on the other side. | |
| Sources Connected storage and database systems (S3, ADLS, relational databases) Dremio queries in place. | Shipments Fulfillment confirmations synced to customer portals and commerce systems. | Sources is specific to Dremio and Shipments to Epicor ERP — each maps to any object or custom field on the other side. | |
| Physical datasets Tables and files promoted from sources; the raw data a sync ultimately reads. | Bills of materials Methods of manufacturing read for costing and planning integrations. | Physical datasets is specific to Dremio and Bills of materials to Epicor ERP — each maps to any object or custom field on the other side. | |
| Virtual datasets (views) SQL views layering semantics over physical data; the preferred sync target for curated extracts. | Customers Master records synced with CRM accounts so sales and the ERP agree on ownership and credit status. | Virtual datasets (views) is specific to Dremio and Customers to Epicor ERP — each maps to any object or custom field on the other side. |
How changes propagate between Dremio and Epicor ERP
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.
Dremio Epicor ERP Interval-based propagation
DetectionStacksync polls Dremio for changes on an incremental schedule, reading only records changed since the previous pass. Polling via SQL.
DeliveryEach detected change is written to Epicor ERP through its API, with automatic retries and rate-limit backoff.
Epicor ERP Dremio Interval-based propagation
DetectionStacksync polls Epicor ERP for changes on an incremental schedule, reading only records changed since the previous pass. Polling on change-date fields.
DeliveryEach detected change is applied to Dremio as a row-level write, with types converted between the two schemas.
Rate-limit considerations
- Dremio: Bounded by engine capacity and workload management rather than API rate limits.
- Epicor ERP: Subject to the platform's API rate limits and per-tenant throttling on Kinetic cloud deployments.
What ships with Dremio ⇄ Epicor ERP
Connect Dremio and Epicor ERP for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Dremio–Epicor ERP connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Dremio or Epicor ERP 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 Dremio or Epicor ERP record.
Observability
Monitoring
Track your Dremio ⇄ Epicor ERP sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Dremio and Epicor ERP.
How the Dremio and Epicor ERP connectors work
Dremio
- Integration surface
- Arrow Flight SQL, JDBC/ODBC, and a REST API
- Authentication
- Personal access tokens or username/password; OAuth-based SSO on Dremio Cloud
- Change detection
- Polling via SQL; Iceberg table snapshots can anchor incremental reads; no consumer-facing change feed
- Capabilities
- read · write
- Rate limits
- Bounded by engine capacity and workload management rather than API rate limits
Epicor ERP
- Integration surface
- 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
- Change detection
- Polling on change-date fields; outbound calls can be wired through BPM directives, but there is no standard webhook subscription surface
- Capabilities
- read · write
- Rate limits
- Subject to the platform's API rate limits and per-tenant throttling on Kinetic cloud deployments
How it works
How to connect Dremio to Epicor ERP — 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 Dremio 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.
Dremio
connected
Epicor ERP
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Dremio 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.
objects · Dremio ⇄ Epicor ERPCustomers 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.
Dremio Epicor ERPCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Dremio and Epicor ERP integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Dremio and Epicor ERP: authenticate both systems, choose the objects to sync (such as Dremio's Jobs and Spaces and folders), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Yes — Stacksync ships production-grade connectors for both Dremio and Epicor ERP. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Dremio: Polling via SQL; Iceberg table snapshots can anchor incremental reads; no consumer-facing change feed. On Epicor ERP: Polling on change-date fields; outbound calls can be wired through BPM directives, but there is no standard webhook subscription surface. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Dremio side: Jobs, Sources, Physical datasets, Virtual datasets (views), plus custom fields where Dremio exposes them. On the Epicor ERP side: Bills of materials, Customers, Suppliers, Parts. 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 Dremio and Epicor ERP: Write-back where Epicor ERP exposes writable fields; Where Epicor ERP holds the books: finance reporting from live data; Where Epicor ERP is the HR system of record: workforce analytics. Classifications or reference values computed in Dremio sync back onto the corresponding records in Epicor ERP.
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 438 integrations available for Dremio and Epicor ERP.
Popular · 7 of 438
-
Dremio ⇄ Dynamics 365 Business Central -
Dremio ⇄ SAP Business ByDesign -
Dremio ⇄ SAP Business One -
Epicor ERP ⇄ Tinybird -
Epicor ERP ⇄ Vertica -
Epicor ERP ⇄ Yellowbrick -
Epicor ERP ⇄ Snowflake
No integrations match .
