Migrate from Infor M3 to Microsoft Dynamics 365 Business Central

Infor M3 Items (MIT/MMS001) map directly to Dynamics 365 Released Products with costing model, unit of measure, and item model group mapped to D365 cost group and item model group. M3's costing elements (standard, average, or FIFO) map to D365's costing model group. Attribute-controlled items in M3 require explicit item configuration groups at the destination. We export items before any order or inventory load so that product references resolve at import time.

M3 Customer records (CRS) map to Dynamics 365 Customer with address, contact, and payment term data preserved. M3's multi-company customer configuration maps to separate Customer records per legal entity in D365. We resolve the customer-address hierarchy before import so that the default delivery address is correctly assigned on the first import pass.

M3 Customer Orders (ECO/OMS100) map to Microsoft Dynamics 365 Sales Order. Header-level data (order number, customer reference, order date, payment terms) and all order lines migrate with status preserved. We load Orders after Items and Customers so that product numbers and customer accounts resolve at insert time. Open versus closed order status is preserved; invoiced orders migrate as historical records with invoiced flag.

M3 Purchase Orders (POH/MMS200) map to Dynamics 365 Purchase Order. Supplier header and line-item data migrate with status preserved. We load supplier records before Purchase Orders so that vendor account references are satisfied. Invoiced purchase orders migrate as closed historical records; open orders remain open for receipt processing.

M3 BOMs (MOP) have multi-level structures with operations, resources, by-products, and configured variants. We flatten M3's BOM levels and re-hierarchy them at the destination, flagging any attribute-controlled or configured products that require BOM version setup at the destination. BOM routing operations (work centers, machines, labor) map to Dynamics 365 route and operation resources. We export parent BOMs before component BOMs to preserve the parent-child relationship.

M3 Work Orders (SFO/MFO) manage manufacturing operations linked to BOMs and routing definitions. We export Work Orders only after BOMs and Items are loaded and validated at the destination so that BOM references resolve. Work order status, operations, and time entries migrate. Production schedules linked to work orders require routing to be loaded first. We flag any attribute-controlled production orders that need explicit configuration at the destination.

M3 inventory quantities, warehouse locations, and bin data map to Dynamics 365 on-hand quantities per site and warehouse. M3's multi-warehouse structure maps to D365's site-warehouse-bin hierarchy. We map M3 warehouse codes to D365 warehouse IDs and flag any bin-level data that exceeds the destination's location granularity so the customer can decide whether to consolidate or expand the warehouse setup.

M3 Financial Ledgers (GLS/FIN) require chart-of-accounts transformation. M3 uses company-relative account structures; Dynamics 365 uses a dimension-ledger model with MainAccount and financial dimensions (Department, Cost Center, Project). We extract the M3 account structure and company associations, then map to D365 chart of accounts per legal entity. Open AP and AR records require careful sequencing and vendor/customer remapping. We flag any accounts with open depreciation periods on Fixed Assets.

M3 Fixed Asset records include depreciation schedules and asset classifications. We export asset master records and depreciation history, flagging any assets with open depreciation periods that require continuation of the existing depreciation schedule at the destination. Asset classes map to D365 Fixed Asset groups, and the net book value and accumulated depreciation transfer as opening balance entries.

M3's chart of accounts supports multi-company configurations with segment masking per company. We extract the account structure, account groups, and company associations and map them to D365's chart of accounts per legal entity. This requires explicit design decisions on dimension mapping — which M3 segments become D365 financial dimensions versus account segments. The customer and their Dynamics admin define the dimension strategy during scoping.

M3 Distribution Orders (DIO) manage inter-site or inter-company transfers with shipment and receipt information. We export full distribution order details including transfer quantities, source and destination warehouses, and transfer status. The destination's site-warehouse mapping must be established before distribution order import so that transfer locations resolve correctly.

M3 custom fields are independently configured per company and per module, and some are display-only and not exposed in the API. We scan custom field definitions per company before export, filter out inaccessible fields, and preserve a manifest so the customer's Dynamics admin can re-create the omitted fields at the destination. We recommend building custom fields as Extensions in D365 via Visual Studio or Power Apps rather than relying on legacy-style customizations.

M3 organizational units used across finance, HR, and operations modules map to D365 Financial Dimensions for Department and Cost Center. We extract the department and cost center hierarchies and map them to D365's financial dimension framework per legal entity. The dimension values must be configured before ledger migration so that ledger entries carry the correct dimension assignments.

M3 supplier invoice header and line-item data migrate to Dynamics 365 vendor invoice journals. Multi-line documents are preserved with line-level detail, tax information, and payment terms. We flag any invoices with partial payments or credit memos requiring open item matching before migration so that the customer's AP team can resolve discrepancies.