Migrate from Infor M3 to Epicor Prophet 21

M3 Items map to Epicor Part records with Product Code preserved as the Part Number. M3 costing models (costing elements, standard costs, current costs) migrate to Epicor Part standard cost and current cost fields. Any M3 Item with a costing model that references custom fields requires those custom fields to be pre-created in Epicor before the cost layer is loaded, because Epicor validates cost method against the Part's configured cost type. Long descriptions and UOMs migrate directly; lot-controlled items in M3 require Epicor's lot configuration to be set before the Part is available for receipt.

M3 Customer Orders map to Epicor Sales Order records with header and line-level data. Order status from M3 (pending, confirmed, invoiced, closed) maps to Epicor OrderHed and OrderDtl status fields. Header discounts and line-level pricing migrate to Epicor's OrderDtl Discount fields. We preserve the M3 order reference and the original order number as a custom field for audit traceability.

M3 Supplier Orders map to Epicor Purchase Orders. Supplier number maps to Epicor VendorNum; supplier address data migrates to VendorPP addr. Line items map with part number, quantity, unit cost, and due date. Multi-line purchase orders with varying currencies require the Epicor currency code to be set at PO level, and any supplier invoices in M3's MMS005 screen are flagged for AP mapping separately.

M3 BOMs with multi-level structures, operations, resources, and by-products require flattening before Epicor import. We extract the full BOM tree from M3, flatten it to a single level with all sub-assemblies exploded into components, then re-hierarchy in Epicor using JobMtl and JobOper records with the correct sequence numbers. Configured and attribute-controlled products in M3 are flagged for Epicor configured part setup before BOM migration proceeds. By-products map to Epicor JobMtl with negative quantity to indicate co-product status.

M3 Work Orders map to Epicor Job records. The parent BOM reference in M3 is used to establish the JobMtl and JobOper structure in Epicor. Work order status (released, in process, complete) maps to Epicor JobHead JobStatus. Any time entries associated with the work order in M3 migrate to Epicor LaborDtl records with the corresponding employee and date. We resolve the M3 production unit and work center to Epicor ResourceGroup and Resource before labor import.

M3 inventory quantities and locations map to Epicor PartBin records. We map M3 warehouse and bin locations to Epicor's Plant/WarehouseCode/BinNum structure. On-hand quantities, allocated quantities, and safety stock levels migrate to Epicer PartQty records with the correct transaction date. M3 lot and serial number tracking is preserved in Epicor's LotCategory and SerialNumber configurations set per Part.

M3 Chart of Accounts requires explicit mapping to Epicor GL Account structure because the account hierarchy differs between platforms. M3's company-specific accounts (linked to M3's multi-company configuration) map to Epicor's company code context. We extract the full account tree including natural account, cost center, and intercompany segments, and flag any accounts that do not have a direct Epicor equivalent for manual mapping during the account structure setup phase.

M3 general ledger transactions map to Epicor GL Journal records with debit and credit amounts. We migrate open AP and AR records (invoices, credit memos, payments) as Epicor APInvcHed/ARInvcHed records with their respective line items. M3's journal entry batch structure maps to Epicor GLJrnGrp with the appropriate fiscal period and year. Closed periods are migrated as historical records; open periods are migrated with the reconciliation flag for AP/AR aging review before final posting.

M3 Fixed Asset master records migrate to Epicor Asset records with asset classification, acquisition date, original cost, and depreciation schedule. We flag any assets with open depreciation periods for review because Epicor's depreciation method and useful life fields may differ from M3's configuration. Accumulated depreciation history migrates as separate AssetReg records to preserve the fiscal year detail.

M3 organizational units used across finance and operations map to Epicor ResourceGroup and Resource records. Department codes become ResourceGroup codes; cost centers become Resources linked to the corresponding ResourceGroup. We preserve the M3 department hierarchy so that Epicor's cost center reporting reflects the original M3 structure.

M3 custom fields are independently configured per company and per module. We scan each module for accessible custom fields, filter out display-only fields that are not API-exposable, and preserve a manifest of all omitted fields for the customer's admin to re-create in Epicor. We create equivalent Epicor UD fields on the target entity and map the field values during migration. Custom field data types in M3 (date, numeric, text, checkbox) map to Epicor field types with appropriate validation.

M3 inter-site and inter-company distribution orders map to Epicor Transfer Orders with from-plant and to-plant assignments. Shipment and receipt information migrates to Epicor's Transfer Order and Transfer Inventory transactions. If the M3 distribution order includes routing or carrier information, we preserve it as a note on the Epicor Transfer Order for logistics setup.