Sage X3 to Twenty CRM integration — real-time, two-way sync

Yes. Stacksync provides a managed, real-time two-way integration between Sage X3 and Twenty CRM: authenticate both systems, choose the objects to sync (such as Sage X3's Sales Orders and Purchase Orders), map fields visually, and changes propagate both ways in milliseconds — no code required.

Change detection on Sage X3: Scheduled polling; no general webhook surface on the classic web services layer. On Twenty CRM: Webhooks on record create, update, and delete events, or polling on record update timestamps. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.

On the Twenty CRM side: Notes, Custom Objects, Attachments, Workspace Members, plus custom fields where Twenty CRM exposes them. On the Sage X3 side: Deliveries, Business Partners (Customers and Suppliers), Products, Sales Orders. 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 Sage X3 and Twenty CRM: Where Sage X3 handles order-to-cash: closed-won flows through; Where Sage X3 is the finance system of record: money status on the account; One customer master. A deal won in Twenty CRM creates or updates the customer in Sage X3 with clean data, so fulfillment and invoicing start without re-entry.

Sage X3: SOAP and REST web services published from X3 business objects; direct SQL access to the underlying database on-prem. Authentication: Dedicated web-service user credentials (Basic auth) against configured connection pools. Twenty CRM: GraphQL and REST APIs. Authentication: API key. Stacksync manages authentication, retries, and rate limits on both sides.