Two-way sync
Changes in Microsoft Dynamics 365 Sales or Xactly instantly reflect in both systems. No stale data, no manual imports.
Keep Microsoft Dynamics 365 Sales 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.
Two CRMs in one company is more common than anyone plans for: an acquisition brings its own system, regions or business units standardize differently, or a migration is under way and both are live. In every case, some of the same companies and people exist in both systems, and every day of manual double entry pushes the copies further apart.
Stacksync syncs Contacts, Leads, Opportunities, Quotes in Microsoft Dynamics 365 Sales with Transactions (Commission & Bonus), Participants (Payees), Positions & Titles, Quotas / Targets in Xactly in real time and in both directions, with field-level mapping and matching on identifiers you choose. Update a record in either CRM and the other reflects it within seconds.
When one CRM is replacing the other, run both fully live until cutover, with no snapshot gap and no data freeze.
Where each CRM serves a different team or region, sync just the shared accounts and contacts so handoffs and cross-sell work.
Deal stage and value on shared accounts stay visible from either CRM.
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.
| Microsoft Dynamics 365 Sales objects | Xactly objects | How this pairing syncs | |
|---|---|---|---|
| Orders Confirmed sales; handed off to ERP systems for fulfillment and billing. | 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. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Accounts Company records in Dataverse; the usual anchor for two-way sync with databases and ERPs. | 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. | Accounts is specific to Microsoft Dynamics 365 Sales and Positions & Titles to Xactly — each maps to any object or custom field on the other side. | |
| Contacts Person records linked to accounts; synced with marketing and support systems. | 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. | Contacts is specific to Microsoft Dynamics 365 Sales and Quotas / Targets to Xactly — each maps to any object or custom field on the other side. | |
| Leads Prospect records; written in from enrichment or web forms, read out on qualification. | Payment Summary (Payable) Approved payable amounts per participant per period; read as the output that feeds payroll and accounts payable, so effectively read-only. | Leads is specific to Microsoft Dynamics 365 Sales and Payment Summary (Payable) to Xactly — each maps to any object or custom field on the other side. | |
| Opportunities Deal records with stages and estimated revenue; synced for pipeline reporting and close-triggered workflows. | 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. | Opportunities is specific to Microsoft Dynamics 365 Sales and Products & Customers to Xactly — each maps to any object or custom field on the other side. | |
| Quotes Pricing proposals; often synced with CPQ or ERP pricing data. | 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. | Quotes is specific to Microsoft Dynamics 365 Sales and Credits 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.
DetectionMicrosoft Dynamics 365 Sales notifies Stacksync of record changes through webhook events. Dataverse change tracking with delta tokens, plus registered webhooks on table events.
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 written to Microsoft Dynamics 365 Sales through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Microsoft Dynamics 365 Sales–Xactly connection.
Changes in Microsoft Dynamics 365 Sales or Xactly instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Microsoft Dynamics 365 Sales 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 Microsoft Dynamics 365 Sales or Xactly record.
Track your Microsoft Dynamics 365 Sales ⇄ Xactly sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Microsoft Dynamics 365 Sales 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 Microsoft Dynamics 365 Sales 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 Microsoft Dynamics 365 Sales 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 Microsoft Dynamics 365 Sales and Xactly: authenticate both systems, choose the objects to sync (such as Microsoft Dynamics 365 Sales's Orders and Accounts), map fields visually, and changes propagate both ways in milliseconds — no code required.
On the Microsoft Dynamics 365 Sales side: Contacts, Leads, Opportunities, Quotes, plus custom fields where Microsoft Dynamics 365 Sales exposes them. On the Xactly side: Transactions (Commission & Bonus), Participants (Payees), Positions & Titles, Quotas / Targets. 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 Microsoft Dynamics 365 Sales and Xactly: Migration with a parallel run; Divisional or regional split; Where both track pipeline: deal visibility across systems. When one CRM is replacing the other, run both fully live until cutover, with no snapshot gap and no data freeze.
Microsoft Dynamics 365 Sales: Dataverse Web API (OData v4 REST). Authentication: OAuth 2.0 via Microsoft Entra ID. 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.
Microsoft Dynamics 365 Sales: Alternate keys allow upserts against external identifiers, so integrations do not need to store Dataverse GUIDs to write reliably. 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. Stacksync's field mapping accounts for these differences between Microsoft Dynamics 365 Sales and Xactly 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 454 integrations available for Microsoft Dynamics 365 Sales and Xactly.