Two-way sync
Changes in Azure Cosmos DB or Microsoft Dynamics GP instantly reflect in both systems. No stale data, no manual imports.
Keep Azure Cosmos DB 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 GL Accounts & Journal Entries, Receivables & Payables Transactions, Company Databases, Customers from Microsoft Dynamics GP into Azure Cosmos DB 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 Azure Cosmos DB sync back into Microsoft Dynamics GP with its validations respected.
Updates in Microsoft Dynamics GP arrive as row changes in Azure Cosmos DB, so jobs and triggers can respond as the business record changes.
Worker and org records stay current in Azure Cosmos DB for provisioning, access, and reporting systems that read from the database.
Choose exactly which tables and fields may flow from Azure Cosmos DB 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.
| Azure Cosmos DB objects | Microsoft Dynamics GP objects | |
|---|---|---|
| Partition keys Determine data distribution and must be included on writes for the sync to route items correctly. | Receivables & Payables Transactions Open and historical AR/AP transactions read for cash and aging reporting. | |
| Change feed entries Ordered record of inserts and updates per partition, consumed for incremental sync. | Company Databases Per-company SQL databases that define the scope of any sync. | |
| Stored procedures and triggers Server-side logic scoped to a partition; relevant when writes must respect existing validation. | Customers Receivables master records (RM tables) synced with CRMs and billing tools. | |
| Databases Top-level namespaces that scope containers and throughput provisioning. | Vendors Payables master records aligned with procurement and AP automation. | |
| Containers The unit of partitioning and throughput; each container maps to a synced collection. | Sales Documents (SOP) Quotes, orders, and invoices created via eConnect from web or CRM orders. | |
| Items (JSON documents) Schema-flexible JSON records read and written during sync; nested structures are flattened or mapped as needed. | Purchase Orders (POP) Procurement documents reconciled with receiving and vendor systems. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Azure Cosmos DB–Microsoft Dynamics GP connection.
Changes in Azure Cosmos DB or Microsoft Dynamics GP instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Azure Cosmos DB 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 Azure Cosmos DB or Microsoft Dynamics GP record.
Track your Azure Cosmos DB ⇄ Microsoft Dynamics GP sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Azure Cosmos DB 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 Azure Cosmos DB 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 Azure Cosmos DB 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 Azure Cosmos DB and Microsoft Dynamics GP: authenticate both systems, choose the objects to sync (such as Azure Cosmos DB's Partition keys and Change feed entries), map fields visually, and changes propagate both ways in milliseconds — no code required.
Common patterns for Azure Cosmos DB 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 Azure Cosmos DB, so jobs and triggers can respond as the business record changes.
Azure Cosmos DB: REST API and SDKs over HTTPS (API for NoSQL, formerly the SQL API); also MongoDB, Cassandra, Gremlin, and Table API surfaces. Authentication: Account keys, resource tokens, or Microsoft Entra ID role-based access. 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.
Azure Cosmos DB: The same account can be exposed through multiple wire-compatible APIs (NoSQL, MongoDB, Cassandra, Gremlin, Table), and the API choice fixes how a connector must speak to it. Microsoft Dynamics GP: Tables follow module prefixes such as RM (receivables), SOP (sales order processing), POP (purchasing), and IV (inventory). Stacksync's field mapping accounts for these differences between Azure Cosmos DB and Microsoft Dynamics GP without custom code.
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Azure Cosmos DB and Microsoft Dynamics GP records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Azure Cosmos DB and Microsoft Dynamics GP connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Azure Cosmos DB–Microsoft Dynamics GP integration in-house.
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 Azure Cosmos DB and Microsoft Dynamics GP.