Migrate from FUJITSU GLOVIA G2 to Dolibarr ERP

GLOVIA G2 Item master records (part numbers, descriptions, UM, cost, revision levels) map to Dolibarr Product. The source item_type (M=mfg, P=purchased, S=stock) maps to Dolibarr type (0=product, 1=service). We extract cost from the Item Cost record and assign to Dolibarr's cost_price field; sell_price migrates from the Item Price table. Lot and serial number tracking migrates if Dolibarr's lot serial module is activated.

Multi-level GLOVIA G2 BOMs (parent assemblies, components, by-products, co-products) map to Dolibarr BOM records with multi-level explosion done at migration time. We sequence BOMs top-down to preserve parent-child relationships; phantom BOMs flatten into their parent. If Dolibarr's manufacturing module is not activated, BOMs are exported as a structured CSV attached to the Product record and documented for manual configuration. Phantom and negative-quantity BOM lines require explicit notes in the migration map.

Open GLOVIA G2 Work Orders map to Dolibarr Project records with type=0 (internal project) when the manufacturing module is inactive. Closed work orders migrate as historical records with status=closed and operation history preserved as notes. Work order operation sequences, labor hours, and material allocations are exported as line-level detail and attached as structured notes to the Project because Dolibarr's manufacturing module does not natively replicate the full work-order routing found in GLOVIA G2. Customers requiring full work-order fidelity should evaluate Dolibarr's MRP module scope during scoping.

GLOVIA G2 Customer records (ship-to, bill-to addresses, credit limits, payment terms) map to Dolibarr Third Party with code prefix CUST. The customer name maps to nom, addresses map to address fields, and payment terms map to cond_reglement and mode_reglement. Credit limits migrate as references and are noted as manual thresholds to configure post-migration. Contact sub-records migrate as Dolibarr Contact objects linked via fk_soc.

GLOVIA G2 Vendor records (procurement terms, lead times, approved supplier lists) map to Dolibarr Third Party with code prefix SUPP. Multi-plant vendor assignments are stored as multiple Third Party records with a shared supplier group reference. ASN data migrates as notes on the Third Party record because Dolibarr does not have a native ASN module.

Open GLOVIA G2 Sales Orders migrate to Dolibarr Order with line items mapped from order detail records. Pricing, discounts, and scheduled ship dates transfer directly. GLOVIA G2 custom order fields map to Dolibarr extrafields where configured, or to structured notes for manual entry. Order status from GLOVIA G2 (DRAFT, OPEN, SHIPPED, CLOSED) maps to Dolibarr status (0,1,2,3). Closed orders migrate as historical records; cancellation reasons preserve as notes.

Open GLOVIA G2 Purchase Orders map to Dolibarr Supplier Order with vendor resolved via the Third Party mapping. Line pricing, lead times, and delivery schedules transfer. GLOVIA G2 blanket PO structures split into individual Dolibarr Supplier Order lines at migration time. Closed POs migrate as historical records only; no re-posting is performed.

GLOVIA G2 Chart of Accounts structures migrate to Dolibarr Accounting. Account numbers, descriptions, and account types (A=asset, L=liability, R=revenue, E=expense) map directly. Sub-ledger control accounts link to the corresponding Third Party and Product records via fk_pcg_version. Closed fiscal period balances migrate as read-only period summary records; actual journal entry detail migrates only for open periods because locked periods cannot be re-posted in GLOVIA G2.

Open AP and AR from GLOVIA G2 sub-ledgers migrate as Dolibarr Supplier Invoices and Customer Invoices respectively, with amounts, due dates, and payment terms preserved. Historical journal entries for open periods migrate as General Ledger entries; locked-period entries export as read-only reference records. Payment history migrates as payment records attached to the corresponding invoice.

On-hand quantities, warehouse locations, and lot/serial assignments migrate to Dolibarr Stock. FIFO and lot costing values preserve at the stock record level. Multi-warehouse configurations map to multiple warehouse records in Dolibarr with quantity allocated per warehouse. Inventory valuation migrates as a stock movement reference for audit.

GLOVIA G2 documents attached to Items, Work Orders, and Orders export via the Application Adapter file export or direct database retrieval. We reattach files to the corresponding Dolibarr records using the document management API. Unsupported attachment types (non-file-based attachments, links to external systems) are listed in the migration gap document for manual re-association.

Every non-standard GLOVIA G2 field added via Bus and Task Developer is identified during discovery and documented. We create corresponding Dolibarr extrafields (text, int, datetime, select, checkbox types matched to GLOVIA G2 field types) in the appropriate Dolibarr module before migration. Complex GLOVIA G2 developer objects with cross-references map to Dolibarr Projects with structured data attached as notes when no native equivalent exists.

GLOVIA G2 users referenced on records (Orders, Work Orders, Contacts) map to Dolibarr User by login name or email match. We resolve fk_user_author and fk_user_modif references at migration time. Any GLOVIA G2 user without a matching Dolibarr User goes to a reconciliation queue for the customer's admin to provision before record import completes.