Translating the item master and product-site record into shared and released products
How X3's item master, product-site record, statistical groups, units of measure and product variants are re-expressed in D365's split model of shared product definition and per-legal-entity released product, with the dimension group and item group choices that drives.
What you will be able to do
Describe the X3 item master and product-site record and explain why that split matters for a migration
Explain the difference between X3 product categories, statistical groups and D365 product categories, item groups and item model groups
Map X3 units of measure and packing units to D365 unit conversions on the shared product
Decompose an X3 product estate into D365 product masters, variants and released products using a repeatable method
Identify the data quality issues in X3 unit conversions and product-site records that most often block a product migration load
Introduction
The Sage X3 item master is the central product definition record: it carries the item code, description, base unit of measure, product category, statistical groups, lot and serial tracking flags, weight, dimensions and product-level attributes.
The X3 item master and product-site record
The X3 item master record carries product-level attributes that are independent of any specific site:
Product categories and statistical groups
X3 product categories are hierarchical classifications used for procurement grouping, sales analysis, reporting and sometimes behaviour control (e.g., a category may influence warehouse routing or inspection rules). D365 has multiple category hierarchy types:
Units of measure and packing units
X3 items carry a base unit and multiple alternative units with item-specific conversion factors. The conversion model supports:
Product variants — X3 coded variants versus D365 product dimensions
X3 supports product variants through coded variant combinations. A product designated as a variant product carries a set of dimension axes (typically colour, size, or configuration) and a table of valid combinations. Each combination has its own code, description and — in some implementations — its own barcode, price and stock position.
The decomposition method: turning an X3 product estate into D365 products
The following method produces a structured output from an X3 product estate that can drive the D365 product master data load design:
Product master data as canonical Wave 2
In the canonical 8-wave model, product master data is loaded in Wave 2 — Master data. This wave depends on Wave 1 (master configuration) having delivered:
Knowledge check
Summary
The X3 product estate is richer than it first appears: the item master carries the identity, but the product-site record carries the operational behaviour, and both must be captured.