Migrate from FUJITSU GLOVIA G2 to Microsoft Dynamics 365 Business Central

GLOVIA G2 Item records carry part numbers, descriptions, unit of measure, standard and FIFO costing values, revision levels, and BOM links. We extract every active Item including its associated BOM references, then map to Business Central Item or D365 F&O Released Product depending on the target Dynamics 365 app. Part number maps to Item Number; product type (stock, service, non-stock) is inferred from the GLOVIA G2 item category code. Lot and serial number data transfers to the destination's tracking dimensions table.

GLOVIA G2 supports multi-level BOMs, by-products, co-products, and phantom BOMs. We sequence BOMs top-down to preserve parent-child relationships during migration. Each BOM header and BOM line is exported independently, with the parent BOM header identified before child lines are written to the destination. Phantom BOMs are flagged as such and created as BOM versions with a phantom routing in the destination. Co-product and by-product relationships require costing configuration in Dynamics 365 and are flagged as a separate rebuild step for the customer's manufacturing consultant.

Open and closed Work Orders carry operation sequences, labor hours, material allocations, and inspection results. We migrate the full work order lifecycle including status history. Closed Work Orders transfer with their final output quantities and consumption records; their status is set to Finished in the destination. GLOVIA G2 operation step references map to Routing references in Business Central or Route Operations in D365 F&O. Note that GLOVIA G2 Work Orders in a Released or In-Process state must be matched to a valid BOM version in Dynamics 365 before the Production Order can be created; we validate this during the transform phase.

GLOVIA G2 Customer records include ship-to and bill-to addresses, credit limits, payment terms, and contact relationships. We map the primary Customer contact to a Contact record linked to the Customer in Dynamics 365. Where GLOVIA G2's co-installed CRM layer is active, we also migrate the Contact sub-object and associated communication history. Customer number from GLOVIA G2 maps to the Dynamics 365 Customer No. field with a validation check for numeric or alphanumeric format compatibility.

Vendor master holds procurement terms, lead times, approved supplier lists, and ASN data. We map Vendor records to the Dynamics 365 Vendor entity, preserving multi-plant assignments as vendor addresses linked to the primary vendor record. Payment terms and shipping instructions transfer as-is where the values match Dynamics 365 standard terminology; non-standard GLOVIA G2 payment terms are flagged as a configuration step for the customer's AP team.

Open Sales Orders migrate line-by-line with pricing, discounts, scheduled ship dates, and line status. GLOVIA G2 allows custom order fields and workflow statuses that require explicit field-level mapping to the destination. We hold Sales Orders in a 'Pending' or 'In Progress' status in Dynamics 365 until the related Item, Customer, and Sales Header are confirmed in the destination. Completed and invoiced Sales Orders from GLOVIA G2 are migrated as historical records with an Invoice record in Dynamics 365 rather than open orders.

Open Purchase Orders transfer with vendor references, line items, quantities, and expected receipt dates. Custom purchase order fields from GLOVIA G2 are mapped to the Dynamics 365 Purch. Line custom field extensions or to user-defined fields on the purchase header. Closed Purchase Orders migrate as historical receipt and invoice records linked to the vendor.

GLOVIA G2 stores the Chart of Accounts, sub-ledgers, and posting history. We export fiscal year closes as locked periods and migrate open AP and AR as live records. Closed fiscal periods in GLOVIA G2 are write-protected and cannot be re-posted in Dynamics 365; we extract period balances as read-only historical records and create a corresponding set of archived ledger entries in the destination with a post date in the appropriate closed period. Custom ledger types added by GLOVIA G2 developers are flagged as non-standard and mapped to Dynamics 365 custom G/L Account types with a note for the customer's finance team to validate posting groups.

On-hand quantities, lot and serial numbers, and location assignments are extracted from GLOVIA G2's inventory module. Lot tracking and FIFO or lot costing values are preserved at the record level and transferred to the Dynamics 365 Item Ledger Entry table. Location codes from GLOVIA G2 map to Warehouse entries in Business Central or Inventory Dimensions in D365 F&O. Inventory valuation (average, standard, FIFO) is read from the GLOVIA G2 item costing record and applied as the initial item costing method in Dynamics 365.

GLOVIA G2 stores documents against Items, Work Orders, and Orders. We export linked files via the document management API and reattach them to the corresponding destination records. The migration of attachments is subject to file size limits on the destination API and document storage quotas in Business Central or Azure Blob Storage linked to D365 F&O. Unsupported attachment types (non-standard file encodings, legacy GLOVIA G2-specific document formats) are flagged in the reconciliation report with a recommendation to convert or archive.

GLOVIA G2 implementations frequently add custom fields and objects via the development environment. We identify all non-standard fields and custom entities during discovery and build explicit mappings for each. We pre-create the destination schema in Dynamics 365 before data import, including custom fields with type-mapped Dynamics 365 field types (text, integer, decimal, date, option, Boolean). Where GLOVIA G2 custom fields reference lookup relationships to standard objects, we resolve the foreign key references to the corresponding Dynamics 365 record IDs at migration time.

GLOVIA G2 Routing records hold operation sequences, machine and labor center assignments, setup times, and run times per operation. We migrate Routings as Routing records in Business Central or Route Operations in D365 F&O, linking each routing to the Item it is associated with. Operation sequence numbers and the next operation references transfer as-is. Work centers in Business Central are created to match GLOVIA G2 work center groups before routing records are imported.