Two-way sync
Changes in Dynamo DB or Xactly instantly reflect in both systems. No stale data, no manual imports.
Keep Dynamo DB and Xactly in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Product and engineering teams constantly need CRM data, and the CRM API is a poor way to get it: rate limits, pagination, custom objects, and integration code that breaks when an admin renames a field. What they actually want is the data in Dynamo DB, where it can be queried and joined like everything else.
Stacksync mirrors Transactions (Commission & Bonus), Participants (Payees), Positions & Titles, Quotas / Targets from Xactly into Tables, Items, Attributes, Partition and Sort Keys in Dynamo DB with real-time, bi-directional sync. Read CRM records with plain queries; write updates from your application and they appear in Xactly with validation intact. Go-to-market teams keep working in the CRM, engineers keep working in the database, and neither has to think about the other.
Back-office apps read and write the synced tables; Stacksync handles the Xactly API, limits, and retries.
Field and stage updates in Xactly arrive as row changes in Dynamo DB, ready to drive jobs and notifications.
Accounts, contacts, and custom objects from Xactly become tables in Dynamo DB you can join with application data directly.
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.
| Dynamo DB objects | Xactly objects | How this pairing syncs | |
|---|---|---|---|
| Tables The top-level containers a sync targets; each table is addressed independently. | Participants (Payees) Sales reps and payees keyed to positions; loaded and updated from HRIS/HCM source data through Connect (write) and read for roster reporting, so read and write. | Tables is specific to Dynamo DB and Participants (Payees) to Xactly — each maps to any object or custom field on the other side. | |
| Items Schemaless records keyed by partition (and optional sort) key, mapped to rows or SaaS objects in syncs. | Positions & Titles Org-hierarchy positions and titles that credits and quotas roll up to; loaded and maintained through Connect (write) and read to resolve the hierarchy, so read and write. | Items is specific to Dynamo DB and Positions & Titles to Xactly — each maps to any object or custom field on the other side. | |
| Attributes Per-item fields, including nested maps and lists, flattened or mapped during sync. | Quotas / Targets Period quota and target values per position or plan; loaded from planning tools through Connect (write) and read for attainment reporting, so read and write. | Attributes is specific to Dynamo DB and Quotas / Targets to Xactly — each maps to any object or custom field on the other side. | |
| Partition and Sort Keys The primary key pair used as the match key for bi-directional sync. | Payment Summary (Payable) Approved payable amounts per participant per period; read as the output that feeds payroll and accounts payable, so effectively read-only. | Partition and Sort Keys is specific to Dynamo DB and Payment Summary (Payable) to Xactly — each maps to any object or custom field on the other side. | |
| Global Secondary Indexes Alternate access paths used when sync queries filter on non-key attributes. | Products & Customers Product and customer/account master used in crediting rules and reporting; loaded and updated from CRM/ERP through Connect (write) and read for lookups, so read and write. | Global Secondary Indexes is specific to Dynamo DB and Products & Customers to Xactly — each maps to any object or custom field on the other side. | |
| DynamoDB Streams Ordered item-level change records consumed for incremental sync. | Orders Sales order and transaction records loaded into Incent as the raw input for crediting and calculation; created and updated through Connect load and ETL steps (write) and read back for reconciliation, so read and write. | DynamoDB Streams is specific to Dynamo DB and Orders to Xactly — 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 Dynamo DB are captured at the source via change data capture — no polling loop against its API. Item-level change streams via DynamoDB Streams or Kinesis Data Streams integration.
DeliveryEach detected change is applied to Xactly as a row-level write, with types converted between the two schemas.
DetectionStacksync polls Xactly for changes on an incremental schedule, reading only records changed since the previous pass. No CDC log for external tools to consume.
DeliveryEach detected change is applied to Dynamo DB as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Dynamo DB–Xactly connection.
Changes in Dynamo DB or Xactly instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Dynamo DB or Xactly data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Dynamo DB or Xactly record.
Track your Dynamo DB ⇄ Xactly sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Dynamo DB and Xactly.
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 Dynamo DB and Xactly 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 Dynamo DB and Xactly 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 Dynamo DB and Xactly: authenticate both systems, choose the objects to sync (such as Dynamo DB's Tables and Items), map fields visually, and changes propagate both ways in milliseconds — no code required.
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 Dynamo DB and Xactly: Internal tools without API code; Trigger workflows from CRM changes; Query the CRM like a database. Back-office apps read and write the synced tables; Stacksync handles the Xactly API, limits, and retries.
Dynamo DB: Proprietary JSON-over-HTTPS API accessed through AWS SDKs; PartiQL supported for SQL-like queries. Authentication: AWS IAM credentials with SigV4 request signing. Xactly: Xactly Connect REST API v2 (JSON), plus ODBC/JDBC drivers over the same ANSI-SQL data model. Incent data is exposed as SQL-queryable objects (for example xactly_order, xactly_credit, xactly_transaction, xactly_payment); data is loaded and extracted through Connect load/query steps and server-side ETL Pipelines. The base host is region/pod-specific (for example https://<pod>.xactlycorp.com). Authentication: OAuth 2.0 via the Xactly Connect API Gateway (bearer tokens issued on behalf of an Xactly Incent user), with HTTP Basic authentication using a dedicated Xactly Connect service-user's credentials also supported for the Connect REST API v2. The connecting user needs Connect/API access plus the relevant object permissions in Incent. Stacksync manages authentication, retries, and rate limits on both sides.
Xactly: Xactly does not publish numeric rate limits; the platform enforces query concurrency and long-query limits, so high-volume loads and extracts run as asynchronous Connect jobs and paged reads rather than row-by-row calls. Dynamo DB: Queries are efficient only along key and index access paths; full-table scans are expensive, which makes stream-based sync preferable to polling. Stacksync's field mapping accounts for these differences between Dynamo DB and Xactly 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 Dynamo DB and Xactly records are not retained after a sync operation.
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 473 integrations available for Dynamo DB and Xactly.