Migrate from FUJITSU GLOVIA G2 to Epicor Prophet 21

GLOVIA G2 Item master records map to Epicor Part. The part number, description, unit of measure, and cost fields transfer directly. Revision levels in GLOVIA G2 correspond to Epicor PartRev records that we create during the Part import. On-hand quantity, lot numbers, and serial numbers migrate from GLOVIA G2 inventory records and land in Epicor PartBin with location-specific rows. If GLOVIA G2 uses lot costing or FIFO valuation, the lot cost values migrate as PartTran records rather than as a simple quantity update.

GLOVIA G2 multi-level BOMs with by-products, co-products, and phantom BOMs map to Epicor PartRev (revision header) and PartMtl (material lines) tables. We sequence BOMs top-down by parent part number to preserve the multi-level structure during migration. Phantom BOMs require explicit PartRev.phantomBOMFlag configuration in Epicor. If GLOVIA G2 BOMs include alternate materials or alternate operations, we create corresponding PartMtl and PartOpr alternate records in Epicor. BOM revision dating from GLOVIA G2 migrates to Epicor PartRev with effective-from and effective-to dates set to preserve the revision history that manufacturing engineering relies on.

GLOVIA G2 Work Orders map to Epicor Jobs (JobHead, JobMtl, JobOper, PartTran). Open work orders migrate with full material allocations, operation sequences, labor hour estimates, and current status. We preserve the operation sequencing by mapping GLOVIA G2 operation steps to Epicor JobOper with the correct OpCode, LaborHrs, and BurdenHrs. Closed work orders migrate as Job records with a Closed status flag and complete PartTran history. Inspection results from GLOVIA G2 attach to Epicor JobOper inspection operation types.

GLOVIA G2 Customer records map to Epicor Customer with ship-to and bill-to addresses preserved as separate address records. Credit limits, payment terms, and sales territory assignments transfer to Epicor Customer fields. Contact sub-records migrate as Epicor Person records linked to the Customer. Where GLOVIA G2 co-installed CRM module is active, we also migrate communication history records as Epicor CustomerLog entries.

GLOVIA G2 Vendor records map to Epicor Supplier with procurement terms, lead times, approved supplier list assignments, and ASN data preserved. Multi-plant vendor assignments from GLOVIA G2 become separate SupplierPP records in Epicor per plant. Vendor contacts migrate as Epicor Person records linked to the Supplier.

Open Sales Orders from GLOVIA G2 migrate line-by-line to Epicor OrderHed (header) and OrderDtl (detail) records. We transfer pricing, discounts, scheduled ship dates, and order statuses. GLOVIA G2 custom order fields map to Epicor OrderHed character fields or UD columns, requiring pre-creation in Epicor before the order import. Released orders versus pending orders in GLOVIA G2 map to Epicor OrderHed.OrderHeld flag to preserve the release status that the warehouse team acts on.

Open Purchase Orders from GLOVIA G2 migrate to Epicor POHeader and PODetail. Vendor, order date, terms, and line items including part number, quantity, unit cost, and due date transfer directly. GLOVIA G2 custom PO fields require pre-creation of Epicor UD columns. Released versus pending status from GLOVIA G2 maps to Epicor POHeader APPROVED flag.

GLOVIA G2 Chart of Accounts structures map to Epicor GL Account with natural account segment preserved and any segment structures (company, division, department) mapped to Epicor's multi-segment account code format. Custom ledger types added by GLOVIA G2 developers require pre-creation of Epicor Ledger records before migration. Sub-ledger associations from GLOVIA G2 map to Epicor GL Account segments.

Open AP and AR sub-ledger records migrate as live Epicor GLJrnDtl entries. Closed fiscal periods in GLOVIA G2 are write-protected and cannot be re-posted; we extract the period balances as read-only historical records in Epicor GLJrnDtl with a closed period flag and deliver a reconciliation report for the customer's finance team to validate before the next fiscal period close. Custom journal entry types from GLOVIA G2 require pre-creation of Epicor Journal Codes.

On-hand quantities by location migrate from GLOVIA G2 to Epicor PartBin with the quantity, cost, and qty Bearing flags preserved. Lot numbers and serial numbers with FIFO or lot costing values transfer to Epicor PartLot records linked to the PartBin. If GLOVIA G2 tracks lot expiration dates, those migrate as PartLot.LotSuffixDate fields. Location assignments from GLOVIA G2 warehouse management module map to Epicor Warehse and Bin records with shelf and location codes preserved.

GLOVIA G2 documents attached to items, work orders, and orders are exported via the Application Adapter file export and reattached to the corresponding Epicor records using Epicor's DocumentReference table. Document revision history and change descriptions transfer as DocumentRev records. We flag any unsupported attachment formats (non-standard GLOVIA G2 document types that Epicor cannot render) for manual retrieval from the GLOVIA G2 file store post-migration.

GLOVIA G2 implementations frequently add custom fields and developer objects via the Bus and Task Developer environment. We identify every non-standard field during discovery and pre-create corresponding Epicor Extended Properties or UD columns before any data load. Custom lookup relationships in GLOVIA G2 (such as a custom field linking an Order to a Project object) require Epicor UD table creation and foreign key configuration in Epicor's database. We deliver a written map of every custom field with its source GLOVIA G2 data type and the target Epicor field definition, for the customer's Epicor admin to review and confirm before import.