Migrate from Infor XA to Microsoft Dynamics 365 Business Central

XA GL accounts in the chart of accounts export cleanly as structured account codes with descriptions and posting controls. We map XA account numbers directly to Business Central G/L Account No. or F&SCM MainAccount entities. Account type (balance sheet, income statement, statistical) and posting group assignments are resolved during configuration against the destination chart of accounts template before import begins.

Item master records in XA carry stocking codes, cost methods (FIFO, standard, average), warehouse assignments, and unit of measure conversions. We map XA item numbers to Business Central Item No. or F&SCM Product number, preserving stocking type, inventory posting group, and cost method. Any user-defined fields from XA CMS470 map to custom fields on the destination Item entity. Unit of measure conversions are extracted from XA's UOM master and mapped to Business Central's Unit of Measure table or F&SCM's product dimension settings.

XA BOMs support multi-level, phantom, and substitute item structures with effective dates and expiration dates. Migration requires recursive BOM explosion to flatten nested hierarchies into the destination BOM lines table. We extract XA BOM parent-item relationships, child items, quantities per, scrap percentages, and operation references, then create Business Central BOM Header and BOM Component records or F&SCM BOM Master and BOM Lines with the appropriate version validity periods.

X routing definitions define operation sequences, work centers, labor and machine standards, and queue and setup times tied to production. We map XA work center codes to Business Central Work Centre or F&SCM Operations Resource entities, preserving operation sequence, run time, setup time, and route group assignments. Work center capacity (hours per day, efficiency, queue time) requires explicit mapping against the destination calendar configuration.

Open and released work orders in XA drive shop floor control and link to routings, labor posting, and costing. We extract work order headers, status, item, quantity, and operation-level data, then create Business Central Production Orders (firm or released status) or F&SCM Production Orders with linked route and BOM. Historical work orders (closed, invoiced) migrate to the history tables with their costing data intact. Status mapping requires XA work order status codes translated to Business Central Firm, Planned, or Released status values.

PO headers and lines in XA carry supplier number, terms, delivery schedules, and line item details including quantity ordered, price, and due date. We map header-level fields (PO number, supplier, terms, ship-to location) and line-level fields (item number, quantity, unit cost, scheduled delivery date) to Business Central or F&SCM Purchase Order entities. Blanket orders and contracts migrate as blanket Purchase Orders with release lines. Any purchase agreement pricing tied to supplier item numbers is preserved in vendor catalog mappings.

Sales orders in XA link to pricing, availability checking, and inventory allocation. We map order headers, line items with quantities and prices, delivery addresses, and order-specific discounts or special terms to Business Central Sales Order or F&SCM Sales Order entities. Ship-to addresses map to Business Central Ship-to Address or F&SCM Delivery Addresses. Order statuses (open, shipped, invoiced, held) map to destination document status codes with the original status preserved as a custom field for reconciliation.

Outstanding payables and receivables in XA carry customer or vendor number, invoice number, due date, and open amount. We extract open AP and AR documents and map them to Business Central Vendor and Customer Ledger Entries or F&SCM open vendor and customer transactions. Original invoice numbers, due dates, payment terms, and amounts migrate with the open document preserved. We flag any XA invoices with mismatched vendor addresses or partial payments for customer review before import.

Time entries, labor posting, and operation completions recorded in XA's shop floor module tie to work orders and employee records. We extract labor hours by work order, operation, and employee, then map to Business Central Production Journal entries or F&SCM Production Journal lines. Time card data migrates as posted journal entries rather than open records, preserving labor cost distribution against the original routing operation.

XA user accounts and IBM i security profiles define access rights and default accounting entities. We extract user IDs, names, and role assignments from the XA security file and map them to Business Central User entities and Permission Sets or F&SCM Security Roles. Any XA custom permissions tied to site-specific RPG programs are flagged as non-migratable and documented for replacement in the new ERP's standard permission model.

XA supports user-defined fields on items, suppliers, and purchase agreement headers via CMS470. These alphanumeric, numeric, or date fields require explicit field-level mapping to Business Central custom fields or F&SCM extension fields, with data type conversion applied during the extract phase. Custom field values stored as separate XA files rather than columns in the main item table require separate file extraction and join on the item key.

XA stores document references and scanned attachments within the IBM i IFS file system rather than as database records. Standard migration extracts cover database objects only. We coordinate a parallel IFS file copy task with the customer, map XA file reference records to a destination SharePoint document library or Dataverse attachment, and validate that IFS file naming conventions match the XA file reference records before the migration window closes.