Migrate from Global Shop Solutions ERP to Acumatica

Global Shop customer records map directly to Acumatica Customer entities. The customer's primary address and all ship-to locations in Global Shop become separate Location records in Acumatica linked by LocationID. Payment terms, credit limits, and AR clerk assignments carry across as direct fields. Multi-contact customer records in Global Shop require junction object creation in Acumatica's Customer Contacts table.

Global Shop vendors map to Acumatica Vendor records with address, phone, and payment terms preserved. Acumatica's LocationID for vendors handles multi-address vendors. Remit-to addresses in Global Shop map to a separate Location record marked as RemitTo in Acumatica. 1099 configuration values transfer as vendor tax settings.

Global Shop inventory items map 1:1 to Acumatica Inventory Items. Lot and serial number tracking in Global Shop maps to Acumatica's lot/serial class assignments on each item. Multiple unit-of-measure rows in Global Shop (each with its own stocking, ordering, and selling UOM) carry forward as separate Item Units rows in Acumatica's Item Units tab. Item class and item type determine stock versus non-stock behavior.

Global Shop BOMs map to Acumatica BOMs with component lines, quantities per, and bill-and-make quantities preserved. Routing operations with work center assignments and estimated run/setup times in Global Shop map to separate operation lines in Acumatica's Routing tab. BOM revision levels in Global Shop carry forward as revision IDs in Acumatica.

Global Shop work orders — the primary manufacturing record — map to Acumatica Production Orders. The Global Shop job number becomes the Production Order reference number. Material issues, outside processing, and labor postings in Global Shop map to separate material and labor transactions within Acumatica's production tracking. We preserve the open/closed status of each Global Shop work order and set the corresponding production order state in Acumatica.

Global Shop's job cost ledger — actual material, labor, and outside processing costs against a job number — maps to Acumatica Project transactions when the Project Accounting module is active. Each Global Shop job becomes a Project in Acumatica with the same cost code structure. Revenue recognition and billing milestones in Global Shop map to Acumatica's project invoicing and Revenue Recognition features.

Global Shop purchase orders map to Acumatica Purchase Orders with vendor, line items, quantities, and expected dates preserved. PO receipts in Global Shop map to Acumatica's Receipt process linked to the original PO. Landed cost allocations in Global Shop (freight, duty, insurance) require separate landed cost category configuration in Acumatica's Accounts Payable module.

Global Shop sales orders map to Acumatica Sales Orders with customer reference, line items, quantities, and warehouse assignments. Acumatica's Availability Check and Allocation steps correspond to Global Shop's warehouse commitment logic. Tax zone configuration in Global Shop maps to Acumatica's tax zone and tax category assignments per line item.

Time tickets, labor clock entries, and scrap logging from Global Shop's shop floor data collection module map to Acumatica production transactions. Each entry is linked to the corresponding production order, work center, and labor code. Machine clock data in Global Shop maps to separate labor entry lines in Acumatica with the appropriate work type classification.

Acumatica does not have a native SPC inspection record equivalent to Global Shop's quality control tracking. We migrate historical inspection results as a custom object linked to the production order, or as attributes on the production order. Your Acumatica admin defines the inspection template and pass/fail rules post-migration using Acumatica's customizable quality management configuration.

Global Shop estimating data — labor rates, material costs, outside process prices, and overhead factors — maps to Acumatica's Estimates or Quotation module. Quote revision history in Global Shop is preserved as version notes in Acumatica's estimate detail. Markup and margin calculations require re-verification against Acumatica's pricing engine.

Global Shop's GAB editor allows customers to build custom dashboards and screens tied to the Pervasive database schema. These have no direct Acumatica equivalent — the underlying database structures are entirely different. We export GAB screen definitions and SQL queries as a rebuild reference document. Acumatica's report designer and Generic Inquiries serve the same analytical purpose but require a fresh build using Acumatica's schema.

Global Shop GL accounts map to Acumatica Chart of Accounts entries. Account segment structure in Global Shop (typically 4–6 segments for cost center, department, etc.) maps to Acumatica's segmented key configuration. Sub-account assignments from Global Shop carry forward as sub-account values in Acumatica's account structure.

Global Shop user and employee records are resolved by email match against Acumatica user accounts. Shop floor employees who clock time in Global Shop but are not Acumatica users are provisioned as Employee records with inquiry-only access to production views. Role assignments in Global Shop (sales, purchasing, shop) map to Acumatica's screen-level and field-level security roles.