Skip to content
Database ⇄ ERP

Amazon DynamoDB to Microsoft Dynamics GP integration — real-time, two-way sync

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.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Amazon DynamoDB and Microsoft Dynamics GP

Give your engineers Microsoft Dynamics GP's data in Amazon DynamoDB: read it with normal queries, write back through the sync, and skip the ERP API entirely.

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.

Common use cases

  • 01 Use DynamoDB Streams as a change-data-capture source to push item INSERT, MODIFY, and REMOVE events into a CRM, search index, or operational database in near-real-time.
  • 02 Backfill or migrate records into DynamoDB from another database using BatchWriteItem, then keep the two stores in continuous sync.
  • 03 Push web or CRM orders into Sales Order Processing through eConnect instead of manual entry.
  • 04 Keep item and inventory data aligned with an ecommerce storefront.

Common sync patterns

Where Microsoft Dynamics GP is the HR system of record: people data for internal systems

Worker and org records stay current in Amazon DynamoDB for provisioning, access, and reporting systems that read from the database.

Controlled write-back

Choose exactly which tables and fields may flow from Amazon DynamoDB back into Microsoft Dynamics GP, keeping the ERP authoritative.

Read ERP records with a query

Records from Microsoft Dynamics GP live in Amazon DynamoDB as ordinary tables or collections, joinable with the rest of your data.

What you can sync between Amazon DynamoDB and Microsoft Dynamics GP

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.

How changes propagate between Amazon DynamoDB and Microsoft Dynamics GP

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.

Amazon DynamoDB Microsoft Dynamics GP Sub-second propagation

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.

Microsoft Dynamics GP Amazon DynamoDB Sub-second propagation

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.

Rate-limit considerations

  • Amazon DynamoDB: Throughput is metered in read/write capacity units (provisioned or on-demand): 1 WCU = one 1 KB write per second, 1 RCU = one strongly-consistent 4 KB read per second. Exceeding capacity or the ~3,000 RCU / 1,000 WCU per-partition ceiling returns ProvisionedThroughputExceededException with throttling.
What ships with Amazon DynamoDB ⇄ Microsoft Dynamics GP

Connect Amazon DynamoDB and Microsoft Dynamics GP for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Amazon DynamoDB–Microsoft Dynamics GP connection.

Real-time

Two-way sync

Changes in Amazon DynamoDB or Microsoft Dynamics GP instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Amazon DynamoDB or Microsoft Dynamics GP data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Amazon DynamoDB or Microsoft Dynamics GP record.

Observability

Monitoring

Track your Amazon DynamoDB ⇄ Microsoft Dynamics GP sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Amazon DynamoDB and Microsoft Dynamics GP.

How the Amazon DynamoDB and Microsoft Dynamics GP connectors work

Amazon DynamoDB

Integration surface
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.
Change detection
DynamoDB Streams emit ordered item-level change records (INSERT, MODIFY, REMOVE) with KEYS_ONLY, NEW_IMAGE, OLD_IMAGE, or NEW_AND_OLD_IMAGES views and 24-hour retention, read via shard iterators (or Kinesis Data Streams for longer retention). No native HTTP webhooks.
Capabilities
read · write · CDC
Rate limits
Throughput is metered in read/write capacity units (provisioned or on-demand): 1 WCU = one 1 KB write per second, 1 RCU = one strongly-consistent 4 KB read per second. Exceeding capacity or the ~3,000 RCU / 1,000 WCU per-partition ceiling returns ProvisionedThroughputExceededException with throttling.

Microsoft Dynamics GP

Integration surface
SQL Server database access plus the eConnect stored-procedure API; Web Services for GP on some deployments
Authentication
SQL Server credentials or Windows authentication
Change detection
SQL Server change tracking or log-based CDC on the company database, or polling on row timestamps
Capabilities
read · write · CDC
How it works

How to connect Amazon DynamoDB to Microsoft Dynamics GP — three steps, no code

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.

  1. 01

    Connect your apps

    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.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Amazon DynamoDB connected
    Microsoft Dynamics GP connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Amazon DynamoDB ⇄ Microsoft Dynamics GP
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Amazon DynamoDB Microsoft Dynamics GP
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Amazon DynamoDB and Microsoft Dynamics GP integration FAQ

SECURITY

Security teams trust Stacksync

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.

SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
CSA STAR
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

Related integrations

Every pair below is a real-time, two-way sync. Search all 537 integrations available for Amazon DynamoDB and Microsoft Dynamics GP.

Popular · 8 of 537
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.