How Sage X3's integration estate — import/export templates, SOAP and REST web services, Syracuse REST APIs, EDI, Sage Integration Cloud, and direct SQL/Oracle extraction — maps to D365 data entities, DMF, OData, custom services, business events, Dataverse, dual-write and Azure Integration Services; the reporting move from Crystal Reports to Electronic Reporting, Power BI and Fabric; and the extraction strategy for the migration itself.
A Sage X3 deployment's integration estate typically spans six distinct technology layers simultaneously: SOAP web-service pools established when X3 first exposed a service layer, Syracuse REST APIs added with the modern web platform, import/export templates that drive recurring batch interfaces, EDI connections to trading partners, Sage…
SOAP pools are Sage X3's longer-established integration surface, providing OAuth2-capable service endpoints that expose X3 objects with full transactional validation. When an external system calls a SOAP pool to create or update an X3 object, the same business rules fire as if a user had performed the operation through the Syracuse…
D365 data entities are the primary integration surface. A data entity is a denormalised view over physical tables, exposing a business-meaningful record — a purchase order header with all required header fields from multiple physical tables, for example. Data entities support three integration modes:
The following table maps each X3 integration surface to its D365 replacement, with an effort classification and ownership assignment.
Crystal Reports remains a current, in-scope customisation surface at Sage X3 v12. Sage's prerequisites documentation lists Crystal Reports Designer CR2016, CR2020, and CR2025 as supported client components. This is not a legacy artefact — it is an active workstream with production reports running daily.
Sage X3 organisations commonly run their analytics and reporting stack directly against the X3 database. This includes:
The migration engine itself must extract data from Sage X3 to feed the Bronze tier of the medallion pipeline. The extraction strategy is volume-driven:
D365 OData services are subject to platform throttling. The standard limit is approximately 1,000 concurrent OData requests per five minutes per tenant. This limit applies to all consumers sharing the tenant — the migration engine, ongoing integrations, and user-driven operations combined.
The Sage X3 integration estate is broader and more technically diverse than most programmes estimate at the start of Discovery. Six technology layers — SOAP, REST, import/export templates, EDI, Integration Cloud, and direct SQL — must all be inventoried, classified, and re-platformed against D365's structurally different integration…