Migrate from Infor XA to Infor CloudSuite Corporate

GL account definitions in Infor XA (chart of accounts with account codes, descriptions, and posting controls) map directly to CloudSuite financial structure. The XA Enterprise Financials migration tool (documented in XA 9.1 release notes) preserves legacy chart-of-accounts and GL account assignment rules during transition to the EGL model, and we incorporate that output into the CloudSuite chart-of-accounts load. Account rules, macro aliases, and allocation definitions require explicit mapping to CloudSuite financial setup sequences.

Item master records in XA carry extensive manufacturing attributes including stocking codes, cost methods, warehouse assignments, and user-defined fields via CMS470. We map Item records to CloudSuite Item Master and flag any user-defined alphanumeric, numeric, or date fields that require custom field creation in CloudSuite before import. The BaseUOMCode and stocking category fields map to CloudSuite unit of measure and item type settings.

BOMs in XA support multi-level, phantom, and substitute item structures. Migration requires recursive BOM explosion to flatten nested hierarchies into CloudSuite's BOM table format. We preserve effective dates, revision levels, and BOM type (multi-level, phantom, substitute) as separate fields, and flag any BOM structures that exceed CloudSuite's nesting depth limits for manual review.

Routings define operation sequences, work centers, and labor or machine standards tied to production. We extract routing definitions from XA and map them to CloudSuite Routing, flagging work center code mappings that require CloudSuite resource group configuration. Operation-level labor and machine time standards migrate as routing operation detail records.

Work orders in XA drive shop floor control and link to routing, labor posting, and costing. We extract open and historical work orders, map their statuses and operation sequences, and preserve associated material and labor transactions as work order detail records. Closed work orders with historical costing data migrate as completed records with cost accumulation preserved.

PO headers and lines in XA carry supplier assignments, terms, and delivery schedules. We map header-level fields and line-item details including quantity, price, delivery date, and status. Open purchase orders migrate as active CloudSuite POs; closed POs migrate as historical records. Any purchase agreement custom fields require CloudSuite custom field pre-creation before import.

Outstanding payables and receivables carry customer or supplier references, invoice numbers, due dates, and amounts. We extract open documents and map them to CloudSuite AP/AR modules, flagging any XA-specific payment terms codes that need CloudSuite terms code mapping. Before migration, all unpaid invoices, vouchers, and journals must be posted in XA to ensure CloudSuite receives accurate open balance data.

Sales orders in XA link to pricing, availability checking, and inventory allocation. We map order headers, line items, delivery addresses, and any order-specific discounts or special terms. Open orders migrate as active CloudSuite Sales Orders; historical orders migrate as completed records. Order-status codes from XA map to CloudSuite order status values through a pre-configured translation table.

Time entries, labor posting, and operation completions recorded in XA's shop floor module tie to work orders and employees. We extract these records to reconstruct labor cost histories in CloudSuite as production transaction detail. Employee references from XA map to CloudSuite worker or employee records, which must be provisioned in CloudSuite before shop floor data import.

XA user accounts and IBM i security profiles define access rights and default accounting entities. We extract user records and map them to CloudSuite role-based access model, noting any custom security configurations that require manual CloudSuite role design. Active users are provisioned as CloudSuite users; inactive XA users are held in a reconciliation queue for admin review.

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 CloudSuite custom field definitions, which must be created in CloudSuite before any data import begins. We pre-create all required custom fields in CloudSuite and generate a field-level mapping spreadsheet for customer validation during the sandbox migration phase.