Migrate from FUJITSU GLOVIA G2 to Infor CloudSuite Corporate

GLOVIA G2 Item records map to Infor CloudSuite Item Master with part numbers, descriptions, unit of measure, cost layers, revision levels, and BOM links preserved. Item type (finished good, raw material, subassembly, phantom) maps to Infor's Item Type field. On-hand quantities, lot/serial numbers, and location assignments transfer from GLOVIA G2's inventory module. We resolve the Item Type and stocking category at migration time based on GLOVIA G2's item classification fields.

Multi-level BOMs, by-products, co-products, and batch production structures in GLOVIA G2 require top-down sequencing to preserve parent-child relationships during migration. We build a dependency graph from the GLOVIA G2 BOM table before any records are inserted into Infor CloudSuite, resolving phantom BOMs and BOM effectivity dates into Infor's revision control structure. Phantom BOMs that exist as GLOVIA G2 assembly-only structures map to Infor phantom items with zero lead time. This sequencing step is the highest-risk phase of any GLOVIA G2 manufacturing migration.

Open and closed work orders migrate with operation sequences, labor hours, material allocations, and inspection results. Work order status maps from GLOVIA G2's workflow status to Infor's Work Order status values (Released, Pending, Complete, Cancelled). Closed work orders carry status history, but closed periods in GLOVIA G2 are write-protected so we migrate closed work orders as historical records with their final status rather than attempting to re-post to Infor's ledger. Routing operations map to Infor work order operations with work center assignments resolved from GLOVIA G2's routing master.

GLOVIA G2 Customer records including ship-to/bill-to addresses, credit limits, payment terms, and contact relationships map to Infor CloudSuite Customer. Where GLOVIA G2's CRM module is co-installed, we also migrate Contact sub-records and associated communication history. Customer dedupe uses the GLOVIA G2 customer number as the external key for initial load, with address normalization applied to match Infor's address format requirements.

GLOVIA G2 Vendor master records (procurement terms, lead times, approved supplier lists, ASN data) map to Infor CloudSuite Supplier. Multi-plant vendor assignments from GLOVIA G2 resolve to Infor's site-specific supplier assignments. We map GLOVIA G2 approved supplier status flags to Infor's supplier approval workflow during migration, flagging any suppliers with expired certifications for manual review before they are set to active status in the destination.

Open Sales Orders migrate line-by-line with pricing, discounts, scheduled ship dates, and order status. GLOVIA G2 custom order fields and workflow statuses require explicit field-level mapping to Infor CloudSuite's Sales Order structure. We migrate only open orders; closed and invoiced orders migrate as historical records. Order totals and tax calculations are verified post-migration against GLOVIA G2's order register before the destination is set to active.

Open Purchase Orders map to Infor CloudSuite Purchase Orders with vendor references, line items, quantities, costs, and promised dates. GLOVIA G2 custom PO fields and approval workflow states require field-level mapping. Received-but-not-invoiced PO lines are flagged as in-transit inventory in Infor's receiving module. Closed POs migrate as historical records.

GLOVIA G2 Chart of Accounts, sub-ledgers, and posting history map to Infor CloudSuite GL. Closed fiscal periods in GLOVIA G2 are write-protected and migrate as locked historical period balances as read-only records in Infor's GL. Open AP/AR sub-ledgers migrate as live Infor records. Custom ledger types added by GLOVIA G2 developers are identified during discovery and mapped to Infor's extended GL segment structure. Account codes and segment structures are reconciled before migration runs against the production period.

On-hand quantities, lot/serial numbers, location assignments, and FIFO or lot costing values transfer from GLOVIA G2's inventory module. Lot tracking attributes (expiration dates, origin codes, certification status) map to Infor's lot master fields. Location assignments from GLOVIA G2's warehouse structure resolve to Infor's warehouse/location hierarchy. We migrate inventory snapshots at a point-in-time agreed with the customer, typically the end of the last open period.

GLOVIA G2 documents stored against items, work orders, and orders are exported via the GLOVIA G2 document management API and reattached to corresponding Infor CloudSuite records. We extract linked files as binary packages and reattach them to the destination records through Infor's document management module. Unsupported attachment formats (legacy proprietary formats no longer supported by GLOVIA G2's current viewer) are flagged for manual retrieval before cutover.

GLOVIA G2 implementations frequently add custom fields and objects via the Bus and Task Developer environment. We identify all non-standard fields during discovery and build explicit mappings for each to Infor CloudSuite's extended field architecture. Custom fields that cannot map to standard Infor fields are held in a migration staging table and delivered as a supplemental data package for the customer to integrate post-migration. The customer chooses whether to deploy these as Infor custom fields, extended data tables, or external reference data.