Two-way sync
Changes in Acumatica or MySQL instantly reflect in both systems. No stale data, no manual imports.
Keep Acumatica and MySQL in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Replicating Acumatica into MySQL gives teams standard SQL access to ERP records. Customers, Invoices, and Sales Orders map to MySQL Tables with defined Columns and Primary Keys, so internal tools, reports, and integrations query the database instead of the Acumatica API.
Stacksync mirrors Payments, Journal Transactions, Projects, Opportunities and Cases from Acumatica into MySQL and keeps both sides consistent in real time. Whatever Acumatica is the system of record for, whether financials, operations, people, or procurement, those records become rows your code can query, and changes written in MySQL sync back into Acumatica with its validations respected.
Acumatica Customers and Sales Orders sync to MySQL Tables, and permitted updates in MySQL flow back to Acumatica.
MySQL Views over synced Invoices and Purchase Orders feed BI dashboards.
order attributes sync into JSON Columns so applications read structured detail without extra Tables.
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.
| Acumatica objects | MySQL objects | How this pairing syncs | |
|---|---|---|---|
| Purchase Orders Procurement documents exchanged with supplier-facing systems. | Databases (Schemas) Top-level namespaces that scope a sync's reads and writes. | Purchase Orders is specific to Acumatica and Databases (Schemas) to MySQL — each maps to any object or custom field on the other side. | |
| Stock Items Inventory master data with quantities shared with external sales channels. | Tables The primary sync target; rows map to records in connected systems. | Stock Items is specific to Acumatica and Tables to MySQL — each maps to any object or custom field on the other side. | |
| Shipments Fulfillment documents read to update tracking in storefronts and CRMs. | Views Read-side projections used as outbound sync sources. | Shipments is specific to Acumatica and Views to MySQL — each maps to any object or custom field on the other side. | |
| Payments Customer payment records reconciled against invoices from payment platforms. | Columns Field-level mapping targets with engine-typed values. | Payments is specific to Acumatica and Columns to MySQL — each maps to any object or custom field on the other side. | |
| Journal Transactions GL entries replicated into reporting databases. | Primary and Unique Keys Match keys for idempotent upserts and conflict handling. | Journal Transactions is specific to Acumatica and Primary and Unique Keys to MySQL — each maps to any object or custom field on the other side. | |
| Projects Project cost and billing structures synced with delivery tools. | JSON Columns Validated semi-structured payloads for nested SaaS data. | Projects is specific to Acumatica and JSON Columns to MySQL — each maps to any object or custom field on the other side. |
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.
DetectionAcumatica notifies Stacksync of record changes through webhook events. Push notifications configurable on data changes, plus polling on LastModifiedDateTime fields.
DeliveryEach detected change is applied to MySQL as a row-level write, with types converted between the two schemas.
DetectionChanges in MySQL are captured at the source via change data capture — no polling loop against its API. Database triggers — Stacksync creates deterministic triggers for internal logging and syncing (requires log_bin_trust_function_creators=ON when.
DeliveryEach detected change is written to Acumatica through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Acumatica–MySQL connection.
Changes in Acumatica or MySQL instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Acumatica or MySQL data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Acumatica or MySQL record.
Track your Acumatica ⇄ MySQL sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Acumatica and MySQL.
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 Acumatica and MySQL 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 Acumatica and MySQL 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 Acumatica and MySQL: authenticate both systems, choose the objects to sync (such as Acumatica's Purchase Orders and Stock Items), map fields visually, and changes propagate both ways in milliseconds — no code required.
Change detection on Acumatica: Push notifications configurable on data changes, plus polling on LastModifiedDateTime fields. On MySQL: Database triggers — Stacksync creates deterministic triggers for internal logging and syncing (requires log_bin_trust_function_creators=ON when binary logging is enabled). Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the MySQL side: Databases (Schemas), Tables, Views, Columns, plus custom fields where MySQL exposes them. On the Acumatica side: Payments, Journal Transactions, Projects, Opportunities and Cases. 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 Acumatica and MySQL: Two-way ERP mirror; Reporting layer; Flexible order payloads. Acumatica Customers and Sales Orders sync to MySQL Tables, and permitted updates in MySQL flow back to Acumatica.
Acumatica: Contract-based REST API (JSON over versioned endpoints), plus SOAP web services and OData access to Generic Inquiries. Authentication: OAuth 2.0 or cookie-based session login with Acumatica credentials. MySQL: SQL wire protocol (MySQL client/server protocol). Authentication: Database credentials entered as a connection string or parameters, with optional SSL root certificate upload and optional SSH tunnel (SSH user + SSH 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 556 integrations available for Acumatica and MySQL.