Migrate from Gauss Box ERP to Infor CloudSuite Corporate

Gauss Box stores the account hierarchy within its accounting module using a numeric account code scheme and descriptive names. We map the full account structure to Infor CloudSuite's chart of accounts, preserving account codes as the primary identifier and inactive Gauss Box accounts as inactive in Infor. JOPPD-specific payroll deduction accounts require EU compliance field mapping and customer sign-off before loading. Parent-child account relationships migrate as the Infor account hierarchy tree.

Gauss Box's Contacts module handles both customer and vendor records with an unlimited contact pool. We separate by type using Gauss Box's contact-type classification, map to Infor Customer (sold-to and ship-to) and Supplier records, and preserve any custom Attribute Set fields as Infor extended fields. Inactive customer records are mapped as inactive in Infor with the original Gauss Box status retained for audit. Duplicate detection runs on company name and tax ID before insert.

Gauss Box Items map to Infor CloudSuite Item Master records with SKU preserved as the item number. Units of measure, pricing tiers, and item categories migrate. We flag duplicate SKUs, inconsistent product naming, and inactive items during pre-migration audit, mapping these to a catch-all legacy item record rather than silently dropping them. If Gauss Box uses custom pricing tiers not representable as standard Infor price lists, we map them to extended fields and document the pricing configuration needed in Infor.

Gauss Box Work Orders span the full loop from planning through tracking to invoicing. We map Work Order status to Infor CloudSuite Production Order status (Released, In Process, Complete, Closed), preserve line items with item references and quantities, and carry over assignment data and work center assignments. Work Order planning dates map to Infor scheduled start and due dates. Custom fields added to Work Orders via Attribute Sets are mapped to Infor extended fields with explicit type-conversion rules (date vs. datetime, numeric vs. text).

Gauss Box Projects and Tasks include activity logs, assignees, subtask hierarchies, and timelines. We map project timelines, assignees, and task statuses to Infor CloudSuite Project management objects. Gauss Box activity logs are preserved as comments or notes on the corresponding Infor Project record since Infor does not store a full interaction log equivalent in the same way. Project budgets from Gauss Box map to Infor budget tracking fields if the CloudSuite edition includes project costing.

Gauss Box Employee records include departments, branches, room reservations, and live status. We map employment data including roles, departments, branch assignments, and organizational chart relationships. Effective-dated employment history requires explicit mapping to Infor CloudSuite HCM employee record fields. If the destination is CloudSuite Industrial without HCM, employee records migrate as a custom object with the same field structure.

Gauss Box JOPPD compliance records and payroll data migrate to Infor CloudSuite HCM payroll configuration if the destination includes the HCM module. Time entries from Gauss Box's Log In module (QR-code working-hours tracking) map to Infor Time Management. JOPPD-specific fields require EU compliance mapping; we preserve the original field values in extended fields and document the configuration needed in Infor to re-establish JOPPD compliance reporting. Historical payroll summaries migrate as records rather than recalculated payroll runs.

Gauss Box Equipment records include QR code assignments, assigned users, and warehouse locations. We map equipment records with QR identifiers preserved, assigned user references resolved to Infor Employee records, and location data mapped to Infor site or warehouse records. If Gauss Box equipment is organized by warehouse structure, we map that hierarchy to Infor's inventory organization model.

Gauss Box Documents stores inbound, outbound, and templated documents with custom statuses. We migrate document metadata (type, date, status, related entity) and binary files separately. Document statuses are mapped to Infor document management statuses, and related entity links (to customer, vendor, item, work order) are established as Infor document associations. Templated documents from Gauss Box are flagged as requiring re-creation in Infor's document template layer.

Gauss Box User roles control access levels and feature permissions per module. We map role definitions and user-to-role assignments to Infor CloudSuite role-based security, noting that role semantics differ substantially between platforms and typically require manual review by the customer's Infor administrator post-migration. We deliver a role-equivalence matrix as part of the migration handoff documentation. Active and inactive user status is preserved.