Re-home eConnect, service-based architecture, legacy web services and Integration Manager onto data entities, custom services and business events, and rebuild the SmartList and SQL reporting layer on Fabric without preserving the source model.
Integration in a GP estate has an unusual property: the source side is often simpler than programmes expect, and the target side is more different than they expect.
The routing rule is stated compactly in the source material: entity-shaped contracts usually land on OData or the data management framework; method-shaped behaviour lands on custom services or workflows.
The customisation inventory lists four integration-oriented surfaces, all with medium preservation potential — noticeably better than the five low-preservation development surfaces.
The migration data path is a separate design from the ongoing integration estate, and the source material describes it directly.
The reporting mapping targets Fabric with a Lakehouse or Warehouse plus a Power BI semantic model, and paginated reporting where a fixed-format output is genuinely required.
Integration contracts have owners outside the programme more often than any other surface. External vendors, customer-facing services, partner systems, and other internal teams with their own release cycles.
Supported by the source material: the routing rule by contract shape, the four integration surfaces with their preservation ratings, the read-only SQL extraction architecture, the medallion structure, and the discard disposition for the SQL reporting layer.
Classify contracts by shape, not by source technology. Entity-shaped goes to entities and packages; method-shaped goes to custom services; event-shaped goes to business events. eConnect pre- and post-logic hides business rules, including account-selection rules that belong in the posting crosswalk.