Migrate from FUJITSU GLOVIA G2 to Odoo ERP

GLOVIA G2 Item records (part numbers, descriptions, UM, cost, revision levels) map to Odoo Product records. The Item Type (raw material, finished goods, sub-assembly) maps to Odoo's product type selection. GLOVIA G2's cost layers (standard, average, FIFO) require configuration of Odoo's product cost method on each record. Unit of Measure conversions are preserved; Odoo's UoM model supports multi-step conversion rules that we configure during import.

GLOVIA G2 multi-level BOMs with co-products, by-products, and batch production structures map to Odoo BoM records. Phantom BOMs in GLOVIA G2 map to Odoo's kit BoM type. We sequence BOM migration top-down so that sub-assemblies are created before parent assemblies, satisfying Odoo's BoM line dependency requirements. GLOVIA G2's operation routing sequences map to Odoo's workcenter definitions with cycle time and efficiency factors.

GLOVIA G2 open Work Orders migrate to Odoo Manufacturing Orders with source document references preserved. Closed work order history migrates as read-only manufacturing records with final status, labor hours, and material allocations. GLOVIA G2's inspection results and operation-level labor tracking map to Odoo workcenter time logs. The GLOVIA G2 work order number becomes the External Reference field on the Odoo Manufacturing Order for traceability.

GLOVIA G2 Customer records consolidate ship-to and bill-to addresses, credit limits, payment terms, and contact relationships into one object. Odoo separates these into Company (the business entity) and Contact (individuals linked to the company). We split GLOVIA G2 customer records by parsing address roles, creating one Company record with multiple Contact records for each distinct contact at the customer. Credit limits and payment terms migrate as fields on the Company record.

GLOVIA G2 Vendor records (procurement terms, lead times, ASN data, multi-plant assignments) map to Odoo Vendor Company records with procurement settings. Individual buyer contacts at the vendor map to Odoo Contact records linked to the Vendor Company. Approved supplier list assignments migrate as Vendor on the Odoo Product record.

GLOVIA G2 open Sales Orders migrate line by line to Odoo Sale Order, preserving pricing, discounts, and scheduled ship dates. GLOVIA G2 custom order fields require explicit field-level mapping to Odoo's sale order line fields or extra fields. Order status (confirmed, in-progress, partial) maps to Odoo Sale Order status (Sales Order ->-confirmed-> Done). The GLOVIA G2 sales order number becomes the Client Order Reference on the Odoo record.

Open GLOVIA G2 Purchase Orders migrate to Odoo Purchase Orders with vendor, line items, quantities, and agreed pricing preserved. Scheduled receipt dates map to Odoo's deadline fields. GLOVIA G2 approval workflow states migrate as Odoo purchase order status. Closed purchase orders migrate as historical read-only records. ASN and advanced shipping notice data from GLOVIA G2 vendor records becomes notes on the Odoo incoming shipment.

GLOVIA G2 Chart of Accounts maps to Odoo's account chart with appropriate account types (expense, revenue, asset, liability). Closed fiscal periods in GLOVIA G2 are write-protected and cannot be re-posted; we extract them as read-only historical records with period balance summaries migrated to Odoo's locked fiscal year entries. Open AP and AR from GLOVIA G2 migrate as live Odoo vendor and customer bills. Sub-ledger types added by GLOVIA G2 developers are enumerated and mapped to corresponding Odoo account types.

On-hand quantities, lot and serial numbers, and location assignments from GLOVIA G2's inventory module map to Odoo Stock Quantities and Stock Moves. Lot tracking and FIFO or lot costing values are preserved at the inventory record level as lot name and value notes. GLOVIA G2 multi-plant location assignments map to Odoo's warehouse and location hierarchy. Current on-hand snapshot is imported as an initial Odoo inventory adjustment rather than a set of individual moves.

GLOVIA G2 implementations frequently add custom fields and objects via the development environment (Bus and Task Developer). We identify all non-standard fields during discovery, enumerate their data types and picklist values, and create corresponding Odoo extra fields on the equivalent model during schema setup. Custom objects without a direct Odoo equivalent are mapped to Odoo's generic ir.model.data records or a custom module depending on complexity. Any custom fields that cannot be represented in standard Odoo are documented for the customer's admin to resolve post-migration.