How to split a QAD item master into D365 products and released products while preserving the planning, quality and regulatory attributes that other workstreams depend on.
The product master is where several workstreams meet. Manufacturing needs bills of material and routes attached to it. Inventory needs dimension groups and valuation behaviour. Quality needs specifications and inspection triggers. Compliance needs regulator-facing identifiers. Planning needs coverage and lead-time policy.
D365 separates a product into two layers, and the separation is useful rather than bureaucratic.
Split the source item master before designing anything. Each group has a different destination and a different owner.
Three group types determine how the product behaves, and all three are difficult to change once transactions exist.
Preserve source item identifiers unless there is a compelling reason not to. The reasons a programme might want to renumber are real — inconsistent legacy conventions, codes that encode obsolete meaning, entity-specific codes for the same physical item — but the cost is usually underestimated because the consumers are external.
Where an estate runs EQMS, a substantial part of the quality data model lives outside the ERP item master — specifications with version and approval history, test methods, sampling plans, supplier approval status, and the audit trail over all of it.
Units of measure and conversions. Nothing loads without these. Product dimension, storage and tracking groups. Structural, and referenced by every product. Item model groups and item groups. Finance-owned, agreed with the controller, referenced by every released product. Products and product masters. The shared definitions.
The item-to-product translation is structurally well understood and rated high confidence. The work is in the attributes: split the source master into identity, units of measure, planning, inventory and valuation, quality and regulatory groups, and route each to its correct destination with a named owner.