Migrate from ManEx to Infor CloudSuite Corporate

ManEx Customer records (contact details, account assignments, address data, payment terms) map to Infor CloudSuite Industrial Customer Master. We extract via direct SQL query on the ManEx database or flat-file export, clean address fields to match Infor's address structure, and resolve the Customer's currency and tax jurisdiction codes to Infor equivalents. Customer is loaded before any Sales Order or AR data because of foreign-key dependencies in the Infor Migration Utility sequence.

ManEx Vendor master data with PO history and RMA associations maps to Infor CloudSuite Industrial Supplier. The vendor-supplier relationship is preserved as a distinct entity to avoid merging suppliers with customers, which are separate objects in Infor. We map ManEx vendor codes to Infor Supplier numbers and preserve any vendor-specific payment terms or RMA contact information as Supplier notes.

ManEx GL accounts (asset, liability, equity, revenue, expense types) map to Infor CloudSuite Industrial GL Account Master. We map each account code and type to the destination chart of accounts, flagging any inactive or suspended ManEx accounts for the customer's Infor administrator to activate post-migration. Account code length and hierarchy must be validated against Infor's account structure before import.

ManEx PO records (line items tied to BOMs, vendor assignments, receiving status) map to Infor CloudSuite Industrial Purchase Order. We preserve the full PO lifecycle including partially received orders, mapping ManEx receiving status flags to Infor PO receipt status. PO header must be loaded before PO lines due to header-level foreign keys in the Infor Migration Utility.

ManEx Sales Order records (pricing, customer linkage, fulfillment status, multi-price-list assignments) map to Infor CloudSuite Industrial Sales Order. Multi-price-list pricing requires value-mapping because ManEx price list IDs are not portable across ERP systems; we resolve the active price list at migration time and map it to Infor's price book structure. SO header is loaded before line items and before any related Invoice records.

ManEx multi-level BOM structures map to Infor CloudSuite Industrial BOM with routing data. Complex multi-level BOMs with phantom assemblies require decomposition during staging: we flatten single-level BOMs for import and document the original hierarchy so the customer's Infor administrator can rebuild parent-level BOMs post-migration if routing continuity is required. Component quantities, scrap factors, and work center assignments are mapped to Infor's BOM lines and routing operations.

ManEx real-time shop floor data (labor time, machine cycles, material consumption per work order) maps to Infor CloudSuite Industrial Work Order transactions. Timestamps are preserved to maintain production history continuity, and material consumption records are linked to the corresponding Infor inventory transactions. Shop floor transactions reference Work Order numbers that must exist in Infor before the transaction import phase begins.

ManEx inventory quantities, locations, lot/serial data, and on-hand quantities map to Infor CloudSuite Industrial Inventory. We handle multiple warehouse locations, lot traceability, and serial number records, mapping ManEx warehouse codes to Infor site and subinventory codes. On-hand quantities are loaded after the Item Master is populated to satisfy foreign-key requirements.

Open payables and receivables map to Infor CloudSuite Industrial AP and AR transactions with current status, aging buckets, and payment terms. Historical ledger transactions require special handling because ManEx may store them in archived or compressed tables; we extract as many periods as the customer elects to migrate and flag any gaps. Open items are loaded before closed items to maintain aging accuracy.

ManEx RMA records tied to original SOs or POs map to Infor CloudSuite Industrial RMA. RMA status codes (open, in-progress, closed) require explicit value-mapping because the state machine differs between ManEx and Infor. We preserve the link to the originating PO or SO as a reference field so the customer's returns team can trace the original transaction in Infor.

ManEx Time and Attendance entries from the optional module tie to employees and work orders. If the destination Infor CloudSuite environment includes Infor HCM or a separate timekeeping module, we map time entries to the corresponding employee records and flag any labor classification codes requiring Infor work class setup. If no Infor time module is present, we export time data as a flat file for the customer's HR administrator to reconcile.

ManEx Quote records with known BOM pricing limitations are migrated with a quality flag. The ManEx quoting module's failure on complex multi-level BOM pricing means a subset of quote records may contain incorrect or incomplete pricing. We migrate quotes as-is with a flag noting its known limitation and recommend the customer's Infor administrator review high-value quotes before using them as templates or converting them to Sales Orders.