Understand the two things that define CloudSuite Industrial — site and entity semantics that vary by tenant, and a Mongoose metadata runtime with no D365 equivalent — and why both must be settled before any extraction design.
Most ERP migrations start with a question about data. A CloudSuite Industrial migration starts with a question about meaning.
The conceptual model sets out the divide in five lines. It is worth reading them slowly, because each row is a workstream.
CSI's defining organisational primitive is the pairing of sites and entities. The problem is not that the pairing is complex. The problem is that its meaning is not fixed by the product.
The second thing that defines CSI is that a great deal of its behaviour is expressed as metadata rather than as code in a repository. The runtime surfaces are:
Topology and runtime are the two defining constructs. There is a third pressure that behaves like one, because it drives as much design as either.
This path is built on Infor's public documentation for CloudSuite Industrial and Mongoose, Microsoft's public documentation for D365, and a reconciled adapter package. Being explicit about the boundary of that evidence is more useful than a confident design built on invented specifics.
The playbook's canonical transformation model has four normalisation steps: topology, costing, runtime and event. Three of them behave as gates that block other work.
The executive summary scores the programme risk plainly, and the shape of that scoring is worth carrying into every steering conversation:
CloudSuite Industrial is a manufacturing ERP on a metadata platform, and both halves of that description generate migration work.