Migrate from Infor M3 to Acumatica

Direct map for standard customer records. Infor M3 stores customer data across MITM3 (customer master) with address, payment terms, and credit limits. Acumatica Customer holds equivalent fields. We map the primary M3 address to the customer address and preserve the M3 customer number in a custom reference field.

Direct map for supplier records. Infor M3 supplier master (MITM3) contains payment terms, bank details, and WHT configuration. Acumatica Vendor carries the same core attributes. M3's tax withholding configuration maps to Acumatica Vendor tax settings; we preserve the M3 supplier number in VendorRefNbr.

Infor M3 item master (MITMAS) holds product definitions, units of measure, lot controls, and costing model linkage. Acumatica's Stock Item covers inventory tracked products; Non-Stock Item covers non-inventory items. The mapping includes UOM conversion rules, the base unit of measure from M3, and item class linkage. Costing type (standard, average, FIFO) maps to Acumatica's valuation method field.

Infor M3's costing model uses a hierarchy of costing elements (material, labor, overhead, discounts) that retrieve from purchase orders or calculate from other elements. Acumatica stores cost as a per-site standard cost or average cost. We extract the final computed cost from M3 and load it as Acumatica's current cost; M3's costing element breakdown is preserved as a custom text field on the item for audit.

M3 PO headers (POOH200) and lines (POE300) map to Acumatica Purchase Order header and detail. Status values (released, on hold, closed) map to Acumatica PO status values. M3's PO approval workflow generates a different status than Acumatica's; we map based on the M3 PO status code. Open POs migrate with their line details, quantities, and agreed prices.

M3 sales order headers (SOOH200) and lines (SOS300) map to Acumatica Sales Order. M3's order types (standard, rush, blanket) map to Acumatica order types. The ship-to address, payment terms from the customer, and line-level discounts carry over. Hold and credit-hold statuses map directly; invoice terms from M3 carry as the order's terms.

M3 inventory transactions (MMS200 for adjustments, MMT100 for transfers) map to Acumatica inventory issues, receipts, and adjustments. Each transaction carries the warehouse code, item, quantity, cost layer, and transaction date. M3's lot numbers map to Acumatica's lot/serial numbers. Transfer transactions generate both an issue and receipt in Acumatica.

Infor M3's Multi-Company (MCM) allows multiple legal entities within one database with cross-company transactions and automatic elimination entries. Acumatica uses separate Branches within a single tenant for multi-entity. We create one Acumatica branch per M3 company, then map M3's elimination entries to Acumatica inter-company journal entries. Your Acumatica admin configures the inter-company elimination account mapping.

Infor M3 custom fields defined in CMS470 (alphanumeric, numeric, date types) attached to items, suppliers, and PO headers/lines map to Acumatica user-defined fields defined per Data Access Class. We read the field definition (type, length, decimal places) and create a matching UDF in the Acumatica Customization Project. The custom field group in M3 translates to the DAC scope in Acumatica.

Infor M3 production orders (PDS200) with routing operations (PDS600) and bill of materials (BOM) map to Acumatica's production orders and bills of materials. M3 work center definitions map to Acumatica's work centers. Operation sequences, labor and machine times, and resource calendars carry over. Formula-controlled items in M3 map to Acumatica's formula BOM type.

Infor M3 warehouses and locations (MITLOC) map to Acumatica warehouses and location codes. M3's zone configurations (bulk, picking, staging) map to Acumatica location types. Bin-level location addresses carry as location labels. M3 warehouse parameters (lead times, replenishment settings) map to Acumatica warehouse attributes.

Infor M3 AP invoices (AP200) map to Acumatica Bills. M3 invoice types (regular, credit memo, prepayment) map to Bill types. Hold status, approval status, and terms carry over. M3's tax breakdown (including withholding tax) maps to Acumatica's tax amount and tax zone fields. Retainage amounts are preserved as a custom field if used in M3.

M3 AR invoices map to Acumatica AR invoices. The customer number, invoice date, due date, terms, and tax amounts map directly. M3 payment status (open, paid, disputed) maps to Acumatica status. Credit hold from M3 sets the customer on credit hold in Acumatica.

Infor M3 journal entries map to Acumatica journal transactions. Account numbers map by account code; M3's company/department dimension maps to Acumatica's branch/department dimension. M3's posting date, reference number, and description carry over. Multi-company journal entries in M3 generate inter-company entries that map as described in the MCM mapping above.

Infor M3 lot-controlled items (MMS100) with batch attributes, expiration dates, and genealogy map to Acumatica's lot classes. M3 lot traceability (which production order generated which lot) maps to Acumatica's lot genealogy. Attribute fields in M3 lot records carry as custom lot attributes in Acumatica.