How long does a Fujitsu Glovia G2 to Acumatica migration take?

Most Glovia G2 to Acumatica migrations complete in 5–10 business days of clock time for under 50,000 records. Manufacturing-heavy datasets with 200,000+ items, multi-level BOMs, and active production orders typically require 3–6 weeks. The longest planning step is resolving Glovia G2 UDFs into Acumatica custom fields and configuring the Acumatica branch and warehouse structure before data transfer begins, including any required testing.

Will my Glovia G2 workflows and approval routing migrate to Acumatica?

No. FlitStack AI migrates data and schema only. Glovia G2 workflows, approval sequences, email notification templates, and saved list-view configurations are platform-specific and do not transfer. They must be rebuilt in Acumatica using Screen-Based Workflows, Generic Inquiries, and the Report Designer. We export your Glovia G2 workflow definitions as a structured reference document to guide your Acumatica administrator through the rebuild.

What happens to Glovia G2 user-defined fields (UDFs) in Acumatica?

Glovia G2 UDFs have no native Acumatica equivalent. We create them as custom fields by publishing a customization project in Acumatica's Customization Project Editor, registering each field against the correct DAC (Customer, Vendor, Stock Item). UDF values from Glovia G2 are then written to these custom fields during migration. If the customization project is not published before migration, UDF values are silently skipped.

Can I migrate Glovia G2 production orders and BOMs to Acumatica?

Yes. Open Glovia G2 production orders translate to Acumatica Production Orders with the same production order number, item, quantities, work center assignments, and dates. BOMs are mapped recursively — component lines become Acumatica BOMLines, phantom assemblies are linked via the PhantomBOM field, and alternate BOMs are preserved as BOM versions. The production order number is stored in a reference field so traceability is maintained after cutover.

How are Glovia G2 item classes handled in Acumatica?

Glovia G2 item class codes map 1:1 to Acumatica's ItemClassID on the Stock Items screen. Item classes in Acumatica control default posting accounts, tax categories, and landed cost rules. We verify that each Glovia G2 item class's costing and planning settings are represented in Acumatica's item class configuration before migration — lot/serial tracked items require the corresponding LotSerClass to exist in Acumatica first.

Does the migration affect my Glovia G2 account during cutover?

No. FlitStack AI uses scoped read access on Glovia G2 throughout the migration — your team continues to create and update records in Glovia G2 during the process. A delta-pickup window (typically 24–48 hours after the initial run) captures any in-flight records created or modified during the cutover period so Acumatica reflects Glovia G2's final state at go-live and validation.

What happens to Glovia G2 lot and serial number history in Acumatica?

Acumatica tracks lot and serial numbers at the inventory transaction level, recording receipts, issues, and adjustments with timestamps. However, the full transaction audit log from Glovia G2 does not surface as a native timeline in Acumatica. We preserve the complete lot/serial transaction history from Glovia G2 as a CSV attachment on the item record in Acumatica for compliance and audit reference.

FUJITSU GLOVIA G2 to Acumatica Migration — Field-Level Mapping & Rollback

Overview

What this migration involves

Fujitsu Glovia G2 is a discrete manufacturing ERP built around a visual, spreadsheet-like interface with over 70 modular applications covering BOMs, production orders, sales order processing, and financials for automotive, aerospace, and electronics manufacturers. Acumatica is a cloud-native ERP with a unified platform that distributes inventory, manufacturing, financial, and CRM data across configurable branches and warehouses. The migration from Glovia G2 to Acumatica requires translating Glovia's item-class structure into Acumatica's item-class framework, mapping Glovia's production orders and BOMs to Acumatica's production management module, and resolving UDFs that have no native Acumatica equivalent through Acumatica's customization layer. We extract data via Glovia's application adapters and import into Acumatica using Acumatica's import/export framework with validation before commit. Workflows, email notifications, saved searches, and generic inquiries are not migrated — we provide a structured reference export for your Acumatica administrator to rebuild them. The migration is scoped read-only on Glovia G2 throughout the process, so your team keeps working while the transfer runs.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

FUJITSU GLOVIA G2

What's pushing teams away

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.

Choosing

Acumatica

What's pulling them in

Unlimited user licensing lets companies add staff without per-seat billing shocks, making Acumatica cost-predictable at scale.
Flexibility and scalability earn consistent praise — users value a platform that adapts to vertical workflows without forcing a redesign.
Real-time visibility across financials, inventory, and projects gives mid-market businesses a consolidated operational view previously available only in enterprise-tier ERPs.
Cloud-native architecture with automatic updates removes infrastructure management burden from in-house IT teams.
Modular licensing lets companies start with one or two suites (Financials, Distribution) and expand into Manufacturing or CRM incrementally.

Object mapping

How FUJITSU GLOVIA G2 objects map to Acumatica

Each row shows how a FUJITSU GLOVIA G2 object lands in Acumatica, including any object-level transformations, lookup resolution, or schema-design dependencies.

Typical mapping — final map is confirmed during the sample migration step.

FUJITSU GLOVIA G2

Item Master (Item)

maps to

Acumatica

Stock Item / Non-Stock Item

1:1

Fully supported

Glovia G2 items with ItemClass = 'Stock' map to Acumatica Stock Items; non-stocked items (MRO, services) map to Non-Stock Items. The ItemClass field in Glovia G2 drives the decision between Acumatica's two item types. Lot/serial tracked items in Glovia G2 preserve tracking attributes in Acumatica's Lot/Serial classes.

FUJITSU GLOVIA G2

Item Class

maps to

Acumatica

Item Class (ItemClassID)

1:1

Fully supported

Glovia G2's ItemClass code maps 1:1 to Acumatica's ItemClassID on the Stock Items screen. Acumatica item classes control default posting settings, tax categories, and landed cost rules — these defaults are reviewed and confirmed before migration runs during the planning phase.

FUJITSU GLOVIA G2

Bill of Materials (BOM)

maps to

Acumatica

Bill of Materials (BOM)

1:1

Fully supported

Glovia G2 BOMs with header version, component lines, and phantom assembly flags map to Acumatica BOMs. Multi-level BOMs are resolved recursively during migration so Acumatica's BOM explosion view reflects the same structure. BOM units of measure are translated using Acumatica's UOM conversion table.

FUJITSU GLOVIA G2

Work Center / Work Center Group

maps to

Acumatica

Work Center / Work Center Group

1:1

Fully supported

Glovia G2 work centers map to Acumatica Work Centers, and work center groups map to Work Center Groups. Machine and labor hourly rates from Glovia G2 are written to the Work Center's Cost Rate fields in Acumatica for cost accounting purposes.

FUJITSU GLOVIA G2

Production Order

maps to

Acumatica

Production Order

1:1

Fully supported

Glovia G2 production orders (with status, quantities, dates, and operation steps) translate to Acumatica Production Orders. The production order number from Glovia G2 is stored in a custom field on the Acumatica production order so cross-referencing remains possible after cutover.

FUJITSU GLOVIA G2

Customer Master

maps to

Acumatica

Customer

1:1

Fully supported

Glovia G2 customer records map to Acumatica Customers. The customer class code (CustomerClass) maps to Acumatica Customer Class (CustomerClassID), which controls credit limit rules, statement cycle, and AR terms defaults, and affects reporting of accounts receivable aging in the system.

FUJITSU GLOVIA G2

Vendor Master

maps to

Acumatica

Vendor

1:1

Fully supported

Glovia G2 vendor records map to Acumatica Vendors. Payment terms, Tax Zone assignments, and Remit-To addresses from Glovia G2 translate to the corresponding Acumatica vendor fields. GL account assignments for AP are mapped to Acumatica's AP account configuration in the system.

FUJITSU GLOVIA G2

Chart of Accounts

maps to

Acumatica

GL Account

1:1

Fully supported

Glovia G2 GL accounts map to Acumatica GL Accounts using AccountCD as the key identifier. Account type (Asset, Liability, Equity, Revenue, Expense) maps directly to Acumatica's Type field. Subaccounts in Glovia G2 translate to Acumatica's subaccount dimension, which is configurable per ledger.

FUJITSU GLOVIA G2

Sales Order (Open)

maps to

Acumatica

Sales Order

1:1

Fully supported

Open Glovia G2 sales orders map to Acumatica Sales Orders with order type, customer reference, order date, line items, warehouse, branch, and tax amount preserved. Order status in Glovia G2 (Open, Completed, Cancelled) maps to Acumatica's Status field with a status-code value map.

FUJITSU GLOVIA G2

Purchase Order (Open)

maps to

Acumatica

Purchase Order

1:1

Fully supported

Open purchase orders from Glovia G2 translate to Acumatica Purchase Orders, preserving vendor, line items, quantities, promised dates, and branch assignments. Acumatica requires the vendor to exist before the PO is created, so vendor migration runs first in the target system.

FUJITSU GLOVIA G2

User-Defined Fields (UDFs)

maps to

Acumatica

Custom Fields

1:1

Fully supported

Glovia G2 UDFs attached to item, customer, or vendor records have no native Acumatica equivalent. We create them as Acumatica custom fields by publishing a customization project through Acumatica's Customization Project Editor, assigning the field to the correct DAC and database column.

FUJITSU GLOVIA G2

Warehouse / Site

maps to

Acumatica

Warehouse / Branch

1:1

Fully supported

Glovia G2 sites and warehouse codes map to Acumatica's Warehouse entity, with branch assignment determined by the plant-to-branch mapping established during discovery. Inventory quantities are transferred to the correct Acumatica warehouse location bin for accurate stock tracking across all operations.

FUJITSU GLOVIA G2	Acumatica	Compatibility
Item Master (Item)	Stock Item / Non-Stock Item1:1	Fully supported
Item Class	Item Class (ItemClassID)1:1	Fully supported
Bill of Materials (BOM)	Bill of Materials (BOM)1:1	Fully supported
Work Center / Work Center Group	Work Center / Work Center Group1:1	Fully supported
Production Order	Production Order1:1	Fully supported
Customer Master	Customer1:1	Fully supported
Vendor Master	Vendor1:1	Fully supported
Chart of Accounts	GL Account1:1	Fully supported
Sales Order (Open)	Sales Order1:1	Fully supported
Purchase Order (Open)	Purchase Order1:1	Fully supported
User-Defined Fields (UDFs)	Custom Fields1:1	Fully supported
Warehouse / Site	Warehouse / Branch1:1	Fully supported

Gotchas + challenges

What specifically takes care here

Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.

FUJITSU GLOVIA G2 gotchas

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

Acumatica gotchas

High

API user licenses cap concurrent sessions and request throughput

High

Multi-tenant filtering requires CompanyID awareness

Medium

Custom fields require separate discovery before field mapping

Medium

Notes and attachments use a separate linked table structure

Low

Implementation timelines frequently run 3–9 months end-to-end

FUJITSU GLOVIA G2 gotchas		Acumatica gotchas
Severity	Issue	Severity	Issue
High	GLOVIA G2 rebranded to CrescentOne	High	API user licenses cap concurrent sessions and request throughput
High	Modular configuration creates unique per-instance schemas	High	Multi-tenant filtering requires CompanyID awareness
Medium	On-premise deployments require direct database access	Medium	Custom fields require separate discovery before field mapping
Medium	Historical closed periods are locked at migration time	Medium	Notes and attachments use a separate linked table structure
		Low	Implementation timelines frequently run 3–9 months end-to-end

Pair-specific challenges

UDF translation requires an Acumatica customization project before data lands

Glovia G2 stores user-defined fields as rows in a generic UDF table attached to any master record — text, number, date, and pick-list UDFs are all stored as varchar or typed columns. Acumatica has no generic UDF table; every custom attribute must be registered as a field in a Customization Project, published to the Acumatica instance, and assigned to the correct Data Access Class (DAC) before data can populate it. We create the customization project with all UDF mappings before migration runs. If the project is not published, those field values are silently dropped on import.
Branch and warehouse scoping requires pre-migration setup in Acumatica

Glovia G2 uses site and plant codes to segment inventory and operations, but the branch concept in Acumatica is tied to the GL ledger, tax reporting, and inter-branch inventory transfers. If Glovia G2's multiple sites map to multiple Acumatica branches, each branch must be created and configured (GL ledger assignment, tax agency assignment, address) before inventory data can be written to it. We deliver a branch-setup plan as part of the discovery phase so the Acumatica schema is ready before data transfer begins.
BOM and routing multi-level nesting must be resolved before Acumatica import

Glovia G2 BOMs support phantom assemblies, alternate BOMs per site, and BOM versions tied to effective dates. Acumatica BOMs have a simpler structure with a single active BOM per item at any given time, plus version tracking. We extract all BOM versions from Glovia G2, resolve the active-effective BOM for the migration date, and map component steps to Acumatica's BOMLines with operation sequence numbers. Phantom assemblies are mapped as sub-BOMs linked by the PhantomBOM field in Acumatica's BOMLine.
Lot and serial number history is preserved as an attachment reference, not a native timeline

Glovia G2 tracks lot transaction history (receipts, issues, and adjustments) with timestamps and operators. Acumatica tracks lot and serial numbers at the inventory transaction level, but the transaction audit trail in Acumatica's INItemLot or INSerMaint screens does not natively capture the full Glovia G2 transaction history in a single view. We preserve the complete lot/serial transaction log from Glovia G2 as a CSV attachment on the item record in Acumatica for compliance reference.
Glovia G2 workflows, email templates, and saved searches do not transfer and require manual rebuild

Glovia G2 workflows, screen-level approval routing, email notification templates, and saved list-view configurations are platform-specific constructs that have no equivalent schema in Acumatica. Acumatica uses Screen-Based Workflows, Generic Inquiries, and Report Designer for comparable functions. FlitStack AI exports Glovia G2 workflow definitions and saved-search criteria as reference documents so your Acumatica administrator can rebuild them. This is disclosed upfront during discovery and scoped separately from the data migration and reconciliation.

Migration approach

Six steps for a successful FUJITSU GLOVIA G2 to Acumatica data migration

Audit Glovia G2 chart of accounts, item class hierarchy, and branch structure

We inventory the complete Glovia G2 account structure, item class codes, UDF definitions and their attached records, work center assignments, and open production orders. This audit produces a migration scope document that identifies which entities have no direct Acumatica equivalent (UDFs, legacy sites that will become warehouses) and which require pre-migration setup (Acumatica branches, item classes, lot/serial number classes). No data moves until this document is signed off.
Configure Acumatica branches, warehouses, item classes, and custom fields

Based on the scope document, we create Acumatica branches matching the Glovia G2 site/plant codes, warehouses assigned to each branch, item classes with posting defaults, and a published Customization Project containing all Glovia G2 UDFs as Acumatica custom fields. FlitStack AI delivers the configuration plan with exact screen paths so your Acumatica admin can validate before activation and integration testing.
Sequence master data migration — accounts before items before transactions

Acumatica enforces referential integrity: GL accounts must exist before journal entries, items must exist before sales order lines, and vendors/customers must exist before related transactions. We sequence the migration as GL accounts → item classes and items → customers and vendors → open sales orders and purchase orders → production orders and BOMs → inventory balances. Each layer is validated (record counts, foreign key checks) before the next layer opens.
Run a sample migration with field-level validation on 200–500 records

A representative slice of items, customers, vendors, open orders, and production orders migrates first. We generate a field-level diff comparing each source record to the corresponding Acumatica record, flagging any truncated values, dropped UDFs, or currency rounding differences. The diff report is reviewed by your team before the full migration commits. UDF mapping and BOM resolution are verified at this stage.
Execute full migration with delta pickup and rollback plan

The full data set migrates against Acumatica. A delta-pickup window (typically 24–48 hours after the initial run) captures any records created or modified in Glovia G2 during the cutover period. All migration operations are logged to an audit trail with source record ID, destination record ID, timestamp, and operator. One-click rollback is available for 72 hours post-migration if reconciliation reveals a systemic mapping error.

Platform deep dives

Context on both ends of the pair

FUJITSU GLOVIA G2

Source

Strengths

Highly visual, spreadsheet-like interface that reviewers describe as user-friendly for teams familiar with Excel.
Deep discrete-manufacturing functionality including production planning, scheduling, shop floor control — purpose-built for automotive, aerospace, electronics.
70+ modular ERP components installable alongside existing software, enabling staged adoption rather than big-bang replacement.
Extensive no-code customization — reviewers consistently call out the ability to modify processes without code as a major advantage over SAP Business One and Dynamics 365.
Strong overall recommendation rate on Gartner Peer Insights (100% would recommend across 45 reviews).

Weaknesses

Configuration complexity at scale — reviewers report initial setup is intricate and requires investment in implementation expertise.
Software updates can override custom configurations, forcing teams to reapply customizations after each upgrade.
Vendor responsiveness on support cases reported as slow by some customers — engagement with technical support can be difficult.
Training quality is uneven — multiple reviewers note training could be improved to help users adopt the breadth of capabilities.
Initial migration onto Glovia G2 is described as difficult and time-consuming, particularly for orgs coming off legacy ERPs.

Acumatica

Destination

Strengths

Unlimited named-user licensing eliminates per-seat cost scaling as teams grow.
Modular architecture lets companies deploy Financials first and add Distribution, Manufacturing, or CRM incrementally.
Cloud-native with automatic updates removes infrastructure patching and version management from IT responsibilities.
Flexible customization framework (UDFs, extensions) supports vertical-specific workflows without forking core code.
Multi-tenant architecture with CompanyID isolation enables safe data segregation across subsidiaries.

Weaknesses

Steep learning curve and complex initial setup create significant onboarding friction.
Report Designer is widely cited as unintuitive and difficult to use for non-developers.
Feature gaps require customizations or third-party add-ons, adding implementation cost and complexity.
Implementation timelines frequently exceed initial estimates, especially for multi-module deployments.
API rate limits and concurrent session caps are tied to license tier, creating throughput constraints for bulk data operations.

	FUJITSU GLOVIA G2 Source	Acumatica Destination
Strengths	Highly visual, spreadsheet-like interface that reviewers describe as user-friendly for teams familiar with Excel. Deep discrete-manufacturing functionality including production planning, scheduling, shop floor control — purpose-built for automotive, aerospace, electronics. 70+ modular ERP components installable alongside existing software, enabling staged adoption rather than big-bang replacement. Extensive no-code customization — reviewers consistently call out the ability to modify processes without code as a major advantage over SAP Business One and Dynamics 365. Strong overall recommendation rate on Gartner Peer Insights (100% would recommend across 45 reviews).	Unlimited named-user licensing eliminates per-seat cost scaling as teams grow. Modular architecture lets companies deploy Financials first and add Distribution, Manufacturing, or CRM incrementally. Cloud-native with automatic updates removes infrastructure patching and version management from IT responsibilities. Flexible customization framework (UDFs, extensions) supports vertical-specific workflows without forking core code. Multi-tenant architecture with CompanyID isolation enables safe data segregation across subsidiaries.
Weaknesses	Configuration complexity at scale — reviewers report initial setup is intricate and requires investment in implementation expertise. Software updates can override custom configurations, forcing teams to reapply customizations after each upgrade. Vendor responsiveness on support cases reported as slow by some customers — engagement with technical support can be difficult. Training quality is uneven — multiple reviewers note training could be improved to help users adopt the breadth of capabilities. Initial migration onto Glovia G2 is described as difficult and time-consuming, particularly for orgs coming off legacy ERPs.	Steep learning curve and complex initial setup create significant onboarding friction. Report Designer is widely cited as unintuitive and difficult to use for non-developers. Feature gaps require customizations or third-party add-ons, adding implementation cost and complexity. Implementation timelines frequently exceed initial estimates, especially for multi-module deployments. API rate limits and concurrent session caps are tied to license tier, creating throughput constraints for bulk data operations.

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

Migrate from FUJITSU GLOVIA G2 to Acumatica

What this migration involves

Field-level fidelity

Schema-aware mapping

Relationships preserved

Full activity history

Attachments & notes

Two sides of the same decision

FUJITSU GLOVIA G2

Acumatica

How FUJITSU GLOVIA G2 objects map to Acumatica

What specifically takes care here

Six steps for a successful FUJITSU GLOVIA G2 to Acumatica data migration

Context on both ends of the pair

How hard is this migration?

Estimate your FUJITSU GLOVIA G2 to Acumatica migration cost

What are you migrating?

Frequently asked questions about FUJITSU GLOVIA G2 to Acumatica data migrations

Can't find your answer?

Related migrations to explore

Move from FUJITSU GLOVIA G2.
Land in Acumatica, intact.

Migrate from FUJITSU GLOVIA G2 to Acumatica

What this migration involves

Field-level fidelity

Schema-aware mapping

Relationships preserved

Full activity history

Attachments & notes

Two sides of the same decision

FUJITSU GLOVIA G2

Acumatica

How FUJITSU GLOVIA G2 objects map to Acumatica

What specifically takes care here

Six steps for a successful FUJITSU GLOVIA G2 to Acumatica data migration

Context on both ends of the pair

How hard is this migration?

Estimate your FUJITSU GLOVIA G2 to Acumatica migration cost

Frequently asked questions about FUJITSU GLOVIA G2 to Acumatica data migrations

Can't find your answer?

How long does a Fujitsu Glovia G2 to Acumatica migration take?

Will my Glovia G2 workflows and approval routing migrate to Acumatica?

What happens to Glovia G2 user-defined fields (UDFs) in Acumatica?

Can I migrate Glovia G2 production orders and BOMs to Acumatica?

How are Glovia G2 item classes handled in Acumatica?

Does the migration affect my Glovia G2 account during cutover?

What happens to Glovia G2 lot and serial number history in Acumatica?

Related migrations to explore

Move from FUJITSU GLOVIA G2. Land in Acumatica, intact.

Move from FUJITSU GLOVIA G2.
Land in Acumatica, intact.