Separate what a CloudSuite Industrial item says about enterprise product identity from what the item-site matrix says about local behaviour, and land both in the D365 product master and released-product model.
The CloudSuite Industrial item is one object that answers two different questions, and the migration's first job is to notice that.
D365 separates the product model into layers that the source combined, and the separation is worth stating precisely because it drives the load design.
The matrix is the central artefact. It is a grid: one row per item, one column per site, and in each populated cell the settings that apply to that combination.
The evidence base is unambiguous that costing is the sharpest edge in the matrix, and it is worth understanding why it belongs to product data rather than only to inventory.
D365 offers a product master with product dimensions — configuration, size, colour, style, version — and variants generated from them. The question is whether any source item family should use it.
Storage and tracking dimension groups attach to the released product, and they decide the level at which on-hand is tracked and — critically — the level at which cost is calculated.
The playbook's wave plan places products, sites, warehouses and costing headers together, and explicitly after costing policy approval. The internal ordering within that work matters.
The CloudSuite Industrial item answers two questions at once, and the target answers them at three levels. Enterprise identity goes to the product. Transactable configuration — item groups, model group, tax groups, dimension groups — goes to the released product, once per legal entity.