Two-way sync
Changes in Epicor ERP or MariaDB instantly reflect in both systems. No stale data, no manual imports.
Keep Epicor ERP and MariaDB 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 Sales orders, Purchase orders, Jobs, Quotes from Epicor ERP into MariaDB and keeps both sides consistent in real time. Whatever Epicor ERP is the system of record for, whether financials, operations, people, or procurement, those records become rows your code can query, and changes written in MariaDB sync back into Epicor ERP with its validations respected.
Scripts and services read and write the synced tables; Stacksync handles the Epicor ERP interface, limits, and retries.
Updates in Epicor ERP arrive as row changes in MariaDB, so jobs and triggers can respond as the business record changes.
Worker and org records stay current in MariaDB for provisioning, access, and reporting systems that read from the database.
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.
| Epicor ERP objects | MariaDB objects | |
|---|---|---|
| Customers Master records synced with CRM accounts so sales and the ERP agree on ownership and credit status. | Tables The primary sync target; rows map to records in connected systems. | |
| Suppliers Vendor masters kept aligned with procurement and AP automation tools. | Views Read-side projections used as outbound sync sources. | |
| Parts Item masters that anchor inventory, BOM, and order line syncs. | Columns Field-level mapping targets with engine-typed values. | |
| Sales orders Created from won CRM opportunities; status and line changes sync back out. | Primary and Unique Keys Match keys for idempotent upserts. | |
| Purchase orders Synced with procurement systems and matched against receipts. | System-Versioned Tables Temporal tables that retain row history natively, useful for auditing synced changes. | |
| Jobs Production jobs whose status feeds shop-floor dashboards and delivery-date updates. | JSON Columns Semi-structured payloads validated with JSON functions. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Epicor ERP–MariaDB connection.
Changes in Epicor ERP or MariaDB instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Epicor ERP or MariaDB data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Epicor ERP or MariaDB record.
Track your Epicor ERP ⇄ MariaDB sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Epicor ERP and MariaDB.
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 Epicor ERP and MariaDB 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 Epicor ERP and MariaDB 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 Epicor ERP and MariaDB: authenticate both systems, choose the objects to sync (such as Epicor ERP's Customers and Suppliers), map fields visually, and changes propagate both ways in milliseconds — no code required.
Change detection on Epicor ERP: Polling on change-date fields; outbound calls can be wired through BPM directives, but there is no standard webhook subscription surface. On MariaDB: Database triggers — Stacksync creates deterministic triggers for internal logging and syncing. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the MariaDB side: Databases (Schemas), Tables, Views, Columns, plus custom fields where MariaDB exposes them. On the Epicor ERP side: Sales orders, Purchase orders, Jobs, Quotes. 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 Epicor ERP and MariaDB: Internal tools and automations without API code; React to ERP changes; Where Epicor ERP is the HR system of record: people data for internal systems. Scripts and services read and write the synced tables; Stacksync handles the Epicor ERP interface, limits, and retries.
Epicor ERP: 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. MariaDB: SQL wire protocol (MySQL-compatible client/server protocol). Authentication: Database credentials (connection string or parameters), with optional SSL root certificate upload and optional SSH tunnel (SSH user + host). 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 Epicor ERP and MariaDB.