Run the classification that decides whether each CloudSuite Industrial site and entity becomes a D365 legal entity, an operational site, or a warehouse — the first irreversible decision on the programme.
Topology is the first irreversible decision on a CloudSuite Industrial migration, and it is the one most likely to be settled by assumption rather than by evidence.
An entity may be statutory, operational, or mixed. Some estates used entities exactly as a legal-entity concept, with one entity per registered company. Others used them to separate divisions or business lines that share a single statutory registration.
D365 is deliberately explicit where CSI was flexible, and the constraints are worth stating precisely because topology decisions are frequently taken on the basis of what people assume the target can be reconfigured to do later.
The knowledge base sets out four migration patterns. In practice they run as a sequence of tests, each producing a decision that is recorded and owned.
Operational site. The default. The site manufactures or plans independently, carries its own inventory parameters, and sits inside a legal entity that was established by the statutory test.
The transfer decision is the clearest illustration of why topology has to be settled first.
An APS site definition carries location identity and planning behaviour together. The location half of that is a topology question and belongs in this module. The planning half is not, and trying to resolve both here produces a topology matrix that nobody in finance can sign.
The output of this module is a single artefact, and the playbook lists it first among the minimum go/no-go evidence: a signed-off site and entity topology matrix.
A CSI entity is a hypothesis about statutory meaning, and a CSI site is a hypothesis about operational meaning. Both hypotheses have to be tested against evidence from finance and operations before either becomes a D365 construct.