Establish what manufacturing an Acumatica tenant actually runs rather than what it is licensed for, map BOMs, operations and production orders onto the D365 production model, and settle the costing and variance design the posting crosswalk depends on.
This module is different from the others in the path, because the first question is not how to map manufacturing but whether there is any manufacturing to map.
Run the scoping test before any mapping workshop, and run it on transactions rather than configuration.
The source holds a bill of material describing what goes into a finished item. The target holds a BOM carrying the component structure and a BOM version that makes that structure valid for a specific site, a quantity range and a date range.
The target models production capability through routes made of operations, executed by operations resources which are grouped into resource groups and carry capabilities, capacity and cost. That is a richer model than most mid-market estates carry, and richness is only valuable where it is used.
The target separates production reporting into distinct journals, each with its own accounting consequence:
Where standard cost is in use, the rolled cost is recalculated in the target, not migrated. The calculation depends on:
An open production order at cutover carries material consumed, possibly time reported, and no receipt. Its value sits in work in progress and it belongs to neither the old system nor the new one.
Manufacturing scope is a discovery finding, not an input. Until transaction evidence exists, the manufacturing design is a placeholder.
Manufacturing is the area where Acumatica programmes most reliably over-scope, and the source material says so in three separate places. The first deliverable is not a mapping; it is evidence — production orders completed, items actually made, time actually reported, variances actually reviewed.