Two-way sync
Changes in MariaDB or Microsoft Dynamics GP instantly reflect in both systems. No stale data, no manual imports.
Keep MariaDB and Microsoft Dynamics GP 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 Inventory Items (IV), GL Accounts & Journal Entries, Receivables & Payables Transactions, Company Databases from Microsoft Dynamics GP into MariaDB and keeps both sides consistent in real time. Whatever Microsoft Dynamics GP 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 Microsoft Dynamics GP with its validations respected.
Updates in Microsoft Dynamics GP 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.
Choose exactly which tables and fields may flow from MariaDB back into Microsoft Dynamics GP, keeping the ERP authoritative.
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.
| MariaDB objects | Microsoft Dynamics GP objects | |
|---|---|---|
| Columns Field-level mapping targets with engine-typed values. | GL Accounts & Journal Entries Financial ledger data replicated to warehouses for consolidated reporting. | |
| Primary and Unique Keys Match keys for idempotent upserts. | Receivables & Payables Transactions Open and historical AR/AP transactions read for cash and aging reporting. | |
| System-Versioned Tables Temporal tables that retain row history natively, useful for auditing synced changes. | Company Databases Per-company SQL databases that define the scope of any sync. | |
| JSON Columns Semi-structured payloads validated with JSON functions. | Customers Receivables master records (RM tables) synced with CRMs and billing tools. | |
| Stored Procedures Server-side logic that can post-process synced rows. | Vendors Payables master records aligned with procurement and AP automation. | |
| Databases (Schemas) Top-level namespaces that scope a sync's reads and writes. | Sales Documents (SOP) Quotes, orders, and invoices created via eConnect from web or CRM orders. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every MariaDB–Microsoft Dynamics GP connection.
Changes in MariaDB or Microsoft Dynamics GP instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever MariaDB or Microsoft Dynamics GP data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single MariaDB or Microsoft Dynamics GP record.
Track your MariaDB ⇄ Microsoft Dynamics GP sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between MariaDB and Microsoft Dynamics GP.
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 MariaDB and Microsoft Dynamics GP 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 MariaDB and Microsoft Dynamics GP 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 MariaDB and Microsoft Dynamics GP: authenticate both systems, choose the objects to sync (such as MariaDB's Columns and Primary and Unique Keys), map fields visually, and changes propagate both ways in milliseconds — no code required.
Change detection on MariaDB: Database triggers — Stacksync creates deterministic triggers for internal logging and syncing. On Microsoft Dynamics GP: SQL Server change tracking or log-based CDC on the company database, or polling on row timestamps. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the MariaDB side: Tables, Views, Columns, Primary and Unique Keys, plus custom fields where MariaDB exposes them. On the Microsoft Dynamics GP side: Inventory Items (IV), GL Accounts & Journal Entries, Receivables & Payables Transactions, Company Databases. 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 MariaDB and Microsoft Dynamics GP: React to ERP changes; Where Microsoft Dynamics GP is the HR system of record: people data for internal systems; Controlled write-back. Updates in Microsoft Dynamics GP arrive as row changes in MariaDB, so jobs and triggers can respond as the business record changes.
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). Microsoft Dynamics GP: SQL Server database access plus the eConnect stored-procedure API; Web Services for GP on some deployments. Authentication: SQL Server credentials or Windows authentication. 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 MariaDB and Microsoft Dynamics GP.