Two-way sync
Changes in Amazon DynamoDB or Microsoft Dynamics GP instantly reflect in both systems. No stale data, no manual imports.
Keep Amazon DynamoDB 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 Sales Documents (SOP), Purchase Orders (POP), Inventory Items (IV), GL Accounts & Journal Entries from Microsoft Dynamics GP into Amazon DynamoDB 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 Amazon DynamoDB sync back into Microsoft Dynamics GP with its validations respected.
Worker and org records stay current in Amazon DynamoDB for provisioning, access, and reporting systems that read from the database.
Choose exactly which tables and fields may flow from Amazon DynamoDB back into Microsoft Dynamics GP, keeping the ERP authoritative.
Records from Microsoft Dynamics GP live in Amazon DynamoDB as ordinary tables or collections, joinable with the rest of your data.
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.
| Amazon DynamoDB objects | Microsoft Dynamics GP objects | How this pairing syncs | |
|---|---|---|---|
| Items Individual schemaless records (attributes up to 400 KB each); read with GetItem, Query, and Scan and written with PutItem or BatchWriteItem, so write is supported here. | Receivables & Payables Transactions Open and historical AR/AP transactions read for cash and aging reporting. | Items is specific to Amazon DynamoDB and Receivables & Payables Transactions to Microsoft Dynamics GP — each maps to any object or custom field on the other side. | |
| Global secondary indexes (GSIs) Alternate key projections that let you Query by non-key attributes without a full table Scan; read-only views maintained automatically by DynamoDB. | Company Databases Per-company SQL databases that define the scope of any sync. | Global secondary indexes (GSIs) is specific to Amazon DynamoDB and Company Databases to Microsoft Dynamics GP — each maps to any object or custom field on the other side. | |
| Local secondary indexes (LSIs) Extra sort keys within the same partition key, defined at table creation; queried like the base table for alternate access patterns. | Customers Receivables master records (RM tables) synced with CRMs and billing tools. | Local secondary indexes (LSIs) is specific to Amazon DynamoDB and Customers to Microsoft Dynamics GP — each maps to any object or custom field on the other side. | |
| DynamoDB Streams Ordered item-level change records (INSERT, MODIFY, REMOVE) with old/new image views and 24-hour retention; the native change-data-capture source Stacksync reads for near-real-time sync. | Vendors Payables master records aligned with procurement and AP automation. | DynamoDB Streams is specific to Amazon DynamoDB and Vendors to Microsoft Dynamics GP — each maps to any object or custom field on the other side. | |
| Global Tables Multi-region, active-active replicas of a table kept in sync by DynamoDB; each region is read and written locally with last-writer-wins conflict resolution. | Sales Documents (SOP) Quotes, orders, and invoices created via eConnect from web or CRM orders. | Global Tables is specific to Amazon DynamoDB and Sales Documents (SOP) to Microsoft Dynamics GP — each maps to any object or custom field on the other side. | |
| Time to Live (TTL) Per-item expiry timestamps; DynamoDB deletes expired items in the background and emits a Streams REMOVE record for each deletion. | Purchase Orders (POP) Procurement documents reconciled with receiving and vendor systems. | Time to Live (TTL) is specific to Amazon DynamoDB and Purchase Orders (POP) to Microsoft Dynamics GP — 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 Amazon DynamoDB are captured at the source via change data capture — no polling loop against its API. DynamoDB Streams emit ordered item-level change records (INSERT, MODIFY, REMOVE) with KEYS_ONLY, NEW_IMAGE, OLD_IMAGE, or NEW_AND_OLD_IMAGES views.
DeliveryEach detected change is applied to Microsoft Dynamics GP as a row-level write, with types converted between the two schemas.
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 applied to Amazon DynamoDB as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Amazon DynamoDB–Microsoft Dynamics GP connection.
Changes in Amazon DynamoDB or Microsoft Dynamics GP instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Amazon DynamoDB 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 Amazon DynamoDB or Microsoft Dynamics GP record.
Track your Amazon DynamoDB ⇄ Microsoft Dynamics GP sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Amazon DynamoDB 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 Amazon DynamoDB 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 Amazon DynamoDB 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 Amazon DynamoDB and Microsoft Dynamics GP: authenticate both systems, choose the objects to sync (such as Amazon DynamoDB's Items and Global secondary indexes (GSIs)), map fields visually, and changes propagate both ways in milliseconds — no code required.
On the Amazon DynamoDB side: Items, Global secondary indexes (GSIs), Local secondary indexes (LSIs), DynamoDB Streams, plus custom fields where Amazon DynamoDB exposes them. On the Microsoft Dynamics GP side: Sales Documents (SOP), Purchase Orders (POP), Inventory Items (IV), GL Accounts & Journal Entries. 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 Amazon DynamoDB and Microsoft Dynamics GP: Where Microsoft Dynamics GP is the HR system of record: people data for internal systems; Controlled write-back; Read ERP records with a query. Worker and org records stay current in Amazon DynamoDB for provisioning, access, and reporting systems that read from the database.
Amazon DynamoDB: AWS SDK / low-level HTTPS JSON API at dynamodb.<region>.amazonaws.com (PutItem, GetItem, UpdateItem, DeleteItem, Query, Scan, BatchWriteItem, TransactWriteItems), plus PartiQL (ExecuteStatement) for SQL-style access and DynamoDB Streams for change capture. Authentication: AWS Signature Version 4 (SigV4) signed requests using an IAM access key ID and secret key, or temporary STS credentials from an assumed IAM role; IAM policies scope access down to table and item level. 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.
Amazon DynamoDB: Data is accessed through the AWS SDK JSON API (PutItem, GetItem, UpdateItem, DeleteItem, Query, Scan) and, optionally, PartiQL (ExecuteStatement) for SQL-compatible reads and writes. Microsoft Dynamics GP: Microsoft has announced the end of the Dynamics GP product lifecycle, which makes sync-out and migration integrations a common requirement. Stacksync's field mapping accounts for these differences between Amazon DynamoDB and Microsoft Dynamics GP without custom code.
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 537 integrations available for Amazon DynamoDB and Microsoft Dynamics GP.