Migrate your FUJITSU GLOVIA G2 data
Modular discrete manufacturing ERP with 70+ optional modules, sold by CrescentOne since Fujitsu's spin-off. Designed for automotive, aerospace, and electronics shops that need deep BOM and shop-floor control rather than a turnkey solution.
In its favor
Why people choose FUJITSU GLOVIA G2
The signal that keeps FUJITSU GLOVIA G2 on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Over 70 optional modules means manufacturers pay only for the functionality they need—processes like batch production, eKanban, and co-product costing are available without forcing a full-stack implementation.
Deep BOM and routing support handles engineer-to-order and make-to-order environments that generic ERP systems cannot model without heavy customization.
Fujitsu's backing gave it credibility with automotive Tier 1 and aerospace OEMs who require a vendor with long-term financial stability and global support coverage.
The spreadsheet-like grid interface matches how manufacturing planners and schedulers actually work, reducing training time for teams already fluent in Excel.
Cloud-to-on-premise portability means manufacturers can start with lower upfront capital before committing to a full on-premises deployment.
High total cost of ownership including software licenses, implementation services, and ongoing support contracts exceeds what smaller discrete manufacturers can sustain long-term.
The rebranding from Fujitsu Glovia to CrescentOne under Constellation Software created uncertainty about product roadmap continuity and support quality.
Implementation complexity—configuring 70+ modules, custom fields, and integrations—routinely exceeds initial project timelines and budgets.
Limited third-party integration ecosystem compared to SAP or Epicor; some customers report difficulty connecting modern SaaS tools to GLOVIA G2's on-premises instances.
Steep learning curve for new employees; the visual workflow interface, while familiar to power users, requires significant training investment for new hires.
Reasons to switch
Why people leave FUJITSU GLOVIA G2
The recurring reasons buyers give for replacing FUJITSU GLOVIA G2. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where FUJITSU GLOVIA G2 fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
FUJITSU GLOVIA G2 pricing overview
GLOVIA G2 uses tiered per-user pricing with add-on fees for advanced modules such as warehouse management, advanced manufacturing, and CPQ. Cloud subscription and on-premise perpetual license options are both available; cloud reduces upfront infrastructure cost but carries ongoing subscription fees.
Starter
Tier 1 of 3
Not publicly listed; request a quote
What's included
Need help selecting your ERP?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on FUJITSU GLOVIA G2's schedule — see our quote-based pricing →
What gets migrated
FUJITSU GLOVIA G2 object support
Object-by-object support for FUJITSU GLOVIA G2 migrations. Per-pair details surface during scoping.
Items / Products
Fully supportedItem master is a core GLOVIA G2 object with rich attributes: part numbers, descriptions, UM, cost, BOM links, revision levels. We extract the full item record including all active BOMs and routing assignments. Custom item properties added during implementation are mapped individually.
Bill of Materials (BOMs)
Fully supportedGLOVIA G2 supports multi-level BOMs, by-products, co-products, and batch production structures. We sequence BOMs top-down to preserve parent-child relationships during migration. Phantom BOMs and BOM effectivity dates are preserved as-is.
Work Orders / Production Orders
Fully supportedOpen and closed work orders carry operation sequences, labor hours, material allocations, and inspection results. We migrate the full work order lifecycle including status history, but closed orders land as read-only historical records in most destinations.
Customers / Accounts
Fully supportedCustomer records include ship-to/bill-to addresses, credit limits, payment terms, and contact relationships. Where CRM is co-installed, we also migrate the Contact sub-object and associated communication history.
Vendors / Suppliers
Fully supportedVendor master holds procurement terms, lead times, approved supplier lists, and ASN data. We map vendor records to the destination's supplier object, preserving multi-plant assignments.
Sales Orders / Purchase Orders
Mapping requiredOpen orders are migrated line-by-line with pricing, discounts, and scheduled ship dates. GLOVIA G2 allows custom order fields and workflow statuses that require field-level mapping to the destination schema. Historical closed orders are migrated as invoice references.
General Ledger / Journal Entries
Fully supportedGLOVIA G2 stores Chart of Accounts, sub-ledgers, and posting history. We export fiscal year closes as locked periods and migrate open AP/AR as live records. Custom ledger types added by developers are flagged for manual review.
Inventory / Stock
Fully supportedOn-hand quantities, lot/serial numbers, and location assignments are extracted from GLOVIA G2's inventory module. Lot tracking and FIFO/lot costing values are preserved at record level.
Documents / Attachments
Mapping requiredGLOVIA 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. Unsupported attachment types are bundled into a ZIP delivered alongside the migration.
Custom Objects / Developer Fields
Mapping requiredGLOVIA G2 implementations frequently add custom fields and objects via the development environment. We identify all non-standard fields during discovery and build explicit mappings for each, defaulting unmapped custom fields to a catch-all custom properties object.
IoT / Machine Data
Not in this platformIoT sensor readings and machine integration logs are high-volume telemetry streams not suited for ERP record migration. These are out of scope for standard GLOVIA G2 migrations.
RPA Configurations
Not in this platformRobotic Process Automation workflows configured within GLOVIA G2 are platform-specific and non-portable. These are excluded from data migration scope.
| Object | Support | Notes |
|---|---|---|
| Items / Products | Fully supported | Item master is a core GLOVIA G2 object with rich attributes: part numbers, descriptions, UM, cost, BOM links, revision levels. We extract the full item record including all active BOMs and routing assignments. Custom item properties added during implementation are mapped individually. |
| Bill of Materials (BOMs) | Fully supported | GLOVIA G2 supports multi-level BOMs, by-products, co-products, and batch production structures. We sequence BOMs top-down to preserve parent-child relationships during migration. Phantom BOMs and BOM effectivity dates are preserved as-is. |
| Work Orders / Production Orders | Fully supported | 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, but closed orders land as read-only historical records in most destinations. |
| Customers / Accounts | Fully supported | Customer records include ship-to/bill-to addresses, credit limits, payment terms, and contact relationships. Where CRM is co-installed, we also migrate the Contact sub-object and associated communication history. |
| Vendors / Suppliers | Fully supported | Vendor master holds procurement terms, lead times, approved supplier lists, and ASN data. We map vendor records to the destination's supplier object, preserving multi-plant assignments. |
| Sales Orders / Purchase Orders | Mapping required | Open orders are migrated line-by-line with pricing, discounts, and scheduled ship dates. GLOVIA G2 allows custom order fields and workflow statuses that require field-level mapping to the destination schema. Historical closed orders are migrated as invoice references. |
| General Ledger / Journal Entries | Fully supported | GLOVIA G2 stores Chart of Accounts, sub-ledgers, and posting history. We export fiscal year closes as locked periods and migrate open AP/AR as live records. Custom ledger types added by developers are flagged for manual review. |
| Inventory / Stock | Fully supported | On-hand quantities, lot/serial numbers, and location assignments are extracted from GLOVIA G2's inventory module. Lot tracking and FIFO/lot costing values are preserved at record level. |
| Documents / Attachments | Mapping required | 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. Unsupported attachment types are bundled into a ZIP delivered alongside the migration. |
| Custom Objects / Developer Fields | Mapping required | GLOVIA G2 implementations frequently add custom fields and objects via the development environment. We identify all non-standard fields during discovery and build explicit mappings for each, defaulting unmapped custom fields to a catch-all custom properties object. |
| IoT / Machine Data | Not in this platform | IoT sensor readings and machine integration logs are high-volume telemetry streams not suited for ERP record migration. These are out of scope for standard GLOVIA G2 migrations. |
| RPA Configurations | Not in this platform | Robotic Process Automation workflows configured within GLOVIA G2 are platform-specific and non-portable. These are excluded from data migration scope. |
Gotchas
What to watch for in FUJITSU GLOVIA G2 migrations
Issues we've hit on past FUJITSU GLOVIA G2 migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
GLOVIA G2 rebranded to CrescentOne
Modular configuration creates unique per-instance schemas
On-premise deployments require direct database access
Historical closed periods are locked at migration time
| Severity | Issue |
|---|---|
| High | GLOVIA G2 rebranded to CrescentOne |
| High | Modular configuration creates unique per-instance schemas |
| Medium | On-premise deployments require direct database access |
| Medium | Historical closed periods are locked at migration time |
Leaving FUJITSU GLOVIA G2?
Where FUJITSU GLOVIA G2 customers move next
6 destinations FUJITSU GLOVIA G2 can migrate to.
How a FUJITSU GLOVIA G2 migration works
Four steps, FUJITSU GLOVIA G2-specific
Connect
Not publicly documented; varies by deployment into FUJITSU GLOVIA G2. Scopes limited to read-only on the data we move.
Map
We translate FUJITSU GLOVIA G2-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate FUJITSU GLOVIA G2 quirks before production.
Migrate
Full migration with FUJITSU GLOVIA G2 rate-limit handling. Rollback available throughout.
FAQ
FUJITSU GLOVIA G2 migration FAQ
Answers to the questions buyers ask most during FUJITSU GLOVIA G2 migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your FUJITSU GLOVIA G2 migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationReady when you are
Migrate FUJITSU GLOVIA G2.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your FUJITSU GLOVIA G2 setup and destination — written quote back within a business day.