Two-way sync
Changes in Microsoft Dynamics GP or Plex ERP instantly reflect in both systems. No stale data, no manual imports.
Keep Microsoft Dynamics GP and Plex 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.
Companies run two ERPs for structural reasons: a two-tier setup with subsidiaries on lighter systems, an acquisition that brought its own stack, a split by function or region, or a migration that will take quarters. In all of these, some of the same organizations, people, and transactions exist in both systems, and keeping them aligned by hand is a standing tax on the back office.
Stacksync syncs Receivables & Payables Transactions, Company Databases, Customers, Vendors in Microsoft Dynamics GP with Sales orders, Purchase orders, Customers, Suppliers in Plex ERP bi-directionally and in real time, with field-level mapping across the two data models and conflict rules you define. A record changed in either system is reflected in the other within seconds, not at the next interface run.
When one system is replacing the other, run both fully live during the transition and cut over without a data freeze.
Where both systems keep records of the same customers, suppliers, or organizations, a correction in either updates the other.
Where one system is the people or finance suite and the other runs operations, the records both sides depend on, such as organizations, cost centers, and reference data, stay in agreement.
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.
| Microsoft Dynamics GP objects | Plex ERP objects | How this pairing syncs | |
|---|---|---|---|
| Customers Receivables master records (RM tables) synced with CRMs and billing tools. | Customers Account records kept consistent with the sales team's CRM | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| GL Accounts & Journal Entries Financial ledger data replicated to warehouses for consolidated reporting. | Production jobs Shop-floor work records combining ERP and MES data for output reporting | GL Accounts & Journal Entries is specific to Microsoft Dynamics GP and Production jobs to Plex ERP — each maps to any object or custom field on the other side. | |
| Receivables & Payables Transactions Open and historical AR/AP transactions read for cash and aging reporting. | Sales orders Demand records written in from e-commerce or EDI channels and read out for fulfillment status | Receivables & Payables Transactions is specific to Microsoft Dynamics GP and Sales orders to Plex ERP — each maps to any object or custom field on the other side. | |
| Company Databases Per-company SQL databases that define the scope of any sync. | Purchase orders Procurement records mirrored to accounting and planning systems | Company Databases is specific to Microsoft Dynamics GP and Purchase orders to Plex ERP — each maps to any object or custom field on the other side. | |
| Vendors Payables master records aligned with procurement and AP automation. | Suppliers Vendor records aligned with procurement and AP tools | Vendors is specific to Microsoft Dynamics GP and Suppliers to Plex ERP — each maps to any object or custom field on the other side. | |
| Sales Documents (SOP) Quotes, orders, and invoices created via eConnect from web or CRM orders. | Shipments Outbound logistics records synced to trading partners and tracking systems | Sales Documents (SOP) is specific to Microsoft Dynamics GP and Shipments to Plex ERP — 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.
DetectionChanges in Microsoft Dynamics GP are captured at the source via change data capture — no polling loop against its API. SQL Server change tracking or log-based CDC on the company database, or polling on row timestamps.
DeliveryEach detected change is written to Plex ERP through its API, with automatic retries and rate-limit backoff.
DetectionStacksync polls Plex ERP for changes on an incremental schedule, reading only records changed since the previous pass. Polling.
DeliveryEach detected change is applied to Microsoft Dynamics GP as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Microsoft Dynamics GP–Plex ERP connection.
Changes in Microsoft Dynamics GP or Plex ERP instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Microsoft Dynamics GP or Plex ERP data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Microsoft Dynamics GP or Plex ERP record.
Track your Microsoft Dynamics GP ⇄ Plex ERP sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Microsoft Dynamics GP and Plex ERP.
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 Microsoft Dynamics GP and Plex ERP 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 Microsoft Dynamics GP and Plex 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.
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 Microsoft Dynamics GP and Plex ERP: authenticate both systems, choose the objects to sync (such as Microsoft Dynamics GP's Customers and GL Accounts & Journal Entries), map fields visually, and changes propagate both ways in milliseconds — no code required.
Change detection on Microsoft Dynamics GP: SQL Server change tracking or log-based CDC on the company database, or polling on row timestamps. On Plex ERP: Polling; no general-purpose change webhooks. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Microsoft Dynamics GP side: Receivables & Payables Transactions, Company Databases, Customers, Vendors, plus custom fields where Microsoft Dynamics GP exposes them. On the Plex ERP side: Sales orders, Purchase orders, Customers, Suppliers. 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 Microsoft Dynamics GP and Plex ERP: Migration in parallel; Shared master data; Split by function. When one system is replacing the other, run both fully live during the transition and cut over without a data freeze.
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. Plex ERP: REST APIs plus legacy SOAP web services. Authentication: API keys issued through the Plex Developer Portal. 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 504 integrations available for Microsoft Dynamics GP and Plex ERP.