Two-way sync
Changes in AWS Aurora PostgreSQL or Xactly instantly reflect in both systems. No stale data, no manual imports.
Keep AWS Aurora PostgreSQL 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 AWS Aurora PostgreSQL, where it can be queried and joined like everything else.
Stacksync mirrors Transactions (Commission & Bonus), Participants (Payees), Positions & Titles, Quotas / Targets from Xactly into Views and materialized views, Foreign keys, Replication slots and publications, Databases and schemas in AWS Aurora PostgreSQL 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 AWS Aurora PostgreSQL, ready to drive jobs and notifications.
Accounts, contacts, and custom objects from Xactly become tables in AWS Aurora PostgreSQL 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.
| AWS Aurora PostgreSQL objects | Xactly objects | How this pairing syncs | |
|---|---|---|---|
| Views and materialized views Usable as read-only sources for filtered or precomputed sync datasets. | Payment Summary (Payable) Approved payable amounts per participant per period; read as the output that feeds payroll and accounts payable, so effectively read-only. | Views and materialized views is specific to AWS Aurora PostgreSQL and Payment Summary (Payable) to Xactly — each maps to any object or custom field on the other side. | |
| Foreign keys Relationship metadata that syncs can translate into object references elsewhere. | 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. | Foreign keys is specific to AWS Aurora PostgreSQL and Products & Customers to Xactly — each maps to any object or custom field on the other side. | |
| Replication slots and publications The logical replication objects that power log-based CDC. | 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. | Replication slots and publications is specific to AWS Aurora PostgreSQL and Orders to Xactly — each maps to any object or custom field on the other side. | |
| Databases and schemas PostgreSQL's two-level namespace scopes which tables a sync connection targets. | Credits Crediting records that tie an order to a participant and position; system-calculated credits are read, while manual and adjustment credits are loaded through Connect, so read and write. | Databases and schemas is specific to AWS Aurora PostgreSQL and Credits to Xactly — each maps to any object or custom field on the other side. | |
| Tables The core sync unit; rows are matched across systems by primary key. | Transactions (Commission & Bonus) Calculated commission and bonus line items produced by Incent's calculation engine; read as the output of comp runs for reporting and downstream payout, so effectively read-only results. | Tables is specific to AWS Aurora PostgreSQL and Transactions (Commission & Bonus) to Xactly — each maps to any object or custom field on the other side. | |
| Rows Inserted, updated, and deleted in both directions during bi-directional syncs. | 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. | Rows is specific to AWS Aurora PostgreSQL and Participants (Payees) 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 AWS Aurora PostgreSQL are captured at the source via change data capture — no polling loop against its API. Log-based CDC via PostgreSQL logical replication (WAL decoding through replication slots), with timestamp polling as a fallback.
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 AWS Aurora PostgreSQL as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every AWS Aurora PostgreSQL–Xactly connection.
Changes in AWS Aurora PostgreSQL or Xactly instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever AWS Aurora PostgreSQL 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 AWS Aurora PostgreSQL or Xactly record.
Track your AWS Aurora PostgreSQL ⇄ Xactly sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between AWS Aurora PostgreSQL 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 AWS Aurora PostgreSQL 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 AWS Aurora PostgreSQL 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 AWS Aurora PostgreSQL and Xactly: authenticate both systems, choose the objects to sync (such as AWS Aurora PostgreSQL's Views and materialized views and Foreign keys), 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 AWS Aurora PostgreSQL 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.
AWS Aurora PostgreSQL: SQL wire protocol (PostgreSQL-compatible), standard Postgres drivers and JDBC. Authentication: Database credentials, optionally AWS IAM database authentication, over TLS. 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: Connect exposes Incent's data as ANSI-SQL-queryable objects (for example xactly_order, xactly_credit, xactly_transaction, xactly_payment) reachable over the Connect REST API v2 or ODBC/JDBC drivers, using the same SQL model for both query and load. AWS Aurora PostgreSQL: Aurora's storage layer replicates data six ways across three Availability Zones and is shared by up to 15 read replicas. Stacksync's field mapping accounts for these differences between AWS Aurora PostgreSQL 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 AWS Aurora PostgreSQL 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 475 integrations available for AWS Aurora PostgreSQL and Xactly.