Two-way sync
Changes in Epicor ERP or Xactly instantly reflect in both systems. No stale data, no manual imports.
Keep Epicor ERP 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.
Xactly holds the customer relationship; Epicor ERP runs the operations and records behind the business. The two overlap wherever the same organizations and transactions matter to both, and when that overlap is bridged by re-keying or overnight batch, each side spends the day working from stale data.
Stacksync syncs Quotas / Targets, Payment Summary (Payable), Products & Customers, Orders in Xactly with Sales orders, Purchase orders, Jobs, Quotes in Epicor ERP field by field, in real time, and in both directions. You decide which system owns which fields; Stacksync keeps every copy consistent and resolves conflicts by rules you set.
Owners, territories, and org structure informed by Epicor ERP stay current in Xactly.
A deal won in Xactly creates or updates the customer in Epicor ERP with clean data, so fulfillment and invoicing start without re-entry.
Invoice and payment state from Epicor ERP shows on the account in Xactly, so reps see balances before promising the next order.
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.
| Epicor ERP objects | Xactly objects | How this pairing syncs | |
|---|---|---|---|
| Jobs Production jobs whose status feeds shop-floor dashboards and delivery-date updates. | 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. | Jobs is specific to Epicor ERP and Transactions (Commission & Bonus) to Xactly — each maps to any object or custom field on the other side. | |
| Quotes Estimates that pair with CRM opportunities during the sales cycle. | 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. | Quotes is specific to Epicor ERP and Participants (Payees) to Xactly — each maps to any object or custom field on the other side. | |
| AR invoices Billing records surfaced in CRM or finance tools for collections visibility. | 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. | AR invoices is specific to Epicor ERP and Positions & Titles to Xactly — each maps to any object or custom field on the other side. | |
| Shipments Fulfillment confirmations synced to customer portals and commerce 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. | Shipments is specific to Epicor ERP and Quotas / Targets to Xactly — each maps to any object or custom field on the other side. | |
| Bills of materials Methods of manufacturing read for costing and planning integrations. | Payment Summary (Payable) Approved payable amounts per participant per period; read as the output that feeds payroll and accounts payable, so effectively read-only. | Bills of materials is specific to Epicor ERP and Payment Summary (Payable) to Xactly — each maps to any object or custom field on the other side. | |
| Customers Master records synced with CRM accounts so sales and the ERP agree on ownership and credit status. | 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. | Customers is specific to Epicor ERP and Products & Customers 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.
DetectionStacksync polls Epicor ERP for changes on an incremental schedule, reading only records changed since the previous pass. Polling on change-date fields.
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 Epicor ERP through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Epicor ERP–Xactly connection.
Changes in Epicor ERP or Xactly instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Epicor ERP 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 Epicor ERP or Xactly record.
Track your Epicor ERP ⇄ Xactly sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Epicor ERP 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 Epicor ERP 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 Epicor ERP 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 Epicor ERP and Xactly: authenticate both systems, choose the objects to sync (such as Epicor ERP's Jobs and Quotes), map fields visually, and changes propagate both ways in milliseconds — no code required.
On the Xactly side: Quotas / Targets, Payment Summary (Payable), Products & Customers, Orders, plus custom fields where Xactly exposes them. On the Epicor ERP side: Sales orders, Purchase orders, Jobs, Quotes. 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 Epicor ERP and Xactly: Where Epicor ERP manages people and org data: keep Xactly aligned; Where Epicor ERP handles order-to-cash: closed-won flows through; Where Epicor ERP is the finance system of record: money status on the account. Owners, territories, and org structure informed by Epicor ERP stay current in Xactly.
Epicor ERP: REST API (OData) over Epicor business objects, plus BAQ (Business Activity Query) endpoints. Authentication: API key combined with basic or token authentication, depending on version and deployment. 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. Epicor ERP: The REST surface wraps Epicor business objects, so API writes pass through the same validation and business logic as the client UI. Stacksync's field mapping accounts for these differences between Epicor ERP 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 533 integrations available for Epicor ERP and Xactly.