Translate Connected Systems Manager, e.net business objects and the OData connector into D365 integration patterns, and build the layered extraction pipeline the migration itself depends on.
The first is migrating the integration estate: everything currently connecting SYSPRO to the world — partner systems, warehouse devices, tax and document services, portals, spreadsheets, downstream reporting — has to be re-established against a different platform with different mechanisms.
Connected Systems Manager is the integration configuration layer, defining how SYSPRO connects to external systems. e.net business objects are the programmable service layer through which external systems interact with SYSPRO logic — the deeper and more widely used surface.
Every integration produces one record, and the record is about the contract rather than the plumbing.
D365 offers several integration mechanisms, and selecting between them is mostly a matter of volume and latency rather than taste.
The gap register names this as its own high-severity work item, and it is worth treating as a distinct exercise rather than as part of the general inventory.
The playbook's reference architecture describes a layered pipeline, and layering it is what makes the migration auditable.
This is where the evidence constraint bites hardest, and where the stance stated in the integration notes has to be followed rather than admired.
The analytics story changes shape in the target, and treating it as a translation exercise is the domain's most reliable way to waste effort.
The three ISV-boundary items from the customisation register have their integration dimension here.
Integration is where the migration's engineering discipline is either established or absent, and both outcomes propagate.