Translate the item master and its business-unit assignments into product masters, released products and sites — and settle units of measure early, because the playbook places them in the very first foundation wave.
Product data is the workstream most often assumed to be simple and most often reloaded. On a PeopleSoft programme there is a specific reason for that, and the source package names it directly: the mapping from inventory item and business-unit assignment to released products and sites carries medium confidence, with the instruction to…
The single most important structural fact in this module is the split between a product and a released product.
The playbook places UnitsOfMeasure in its first foundation wave, alongside currencies and calendars, and separately names a unit-of-measure translation sidecar among its target gotcha controls. Both signals point the same way: units are foundational and they are not a straight copy.
PeopleSoft item classification structures typically serve several purposes at once. The same category tree may drive purchasing behaviour, reporting rollup, and in some estates accounting distribution. That multi-purpose use is efficient in the source and does not transfer.
This is the decision that most affects the target's usability, and it is easy to get wrong in the generous direction.
D365 distinguishes a product master with variants — generated from configuration, colour, size and style dimensions — from a standalone product with no variant structure. The distinction determines how items are numbered, how inventory is tracked, and how orders are entered.
The concept mapping's caution is worth restating in full because it governs the sequencing of this whole module: preserve business-unit and site behaviour only after warehouse and costing design is settled.
Three smaller reference families sit alongside products in the playbook's wave plan and carry a shared gotcha worth knowing before conversion starts.
To close this module honestly, here is the discovery set on which its estate-specific content depends. None of it is in the source package.
Product data on a PeopleSoft programme is straightforward in shape and dependent in sequence. The shape is known; the detail waits on decisions this module does not own.