Migrate from Global Shop Solutions ERP to Odoo ERP

Global Shop Solutions Customer master records map to Odoo Res.partner with the customer flag enabled. We migrate name, address, payment terms, credit limits, and open AR invoice balances. In Odoo, contacts attached to the partner carry phone, email, and job title. AR aging buckets are preserved as Odoo open invoice records linked to the partner, and the customer number from GSS becomes the partner's internal reference field.

GSS Vendor master records map to Odoo Res.partner with the vendor flag enabled. Address, contact details, 1099 settings, and payment terms carry forward. Open AP voucher balances and expected payment dates migrate as Odoo open vendor bills. Vendor 3-way AP match configuration in GSS has no direct Odoo equivalent; we document the vendor terms and purchase prepayment settings for the customer's AP team to configure in Odoo.

GSS inventory items map to Odoo product records with the storable product type. On-hand quantities, bin locations, ABC classification, and lead times migrate as Odoo stock.quant records tied to the product and warehouse location. Cost layers (FIFO/LIFO/average) migrate as Odoo valuation layers: we extract the actual unit cost from GSS cost records and set the Odoo product's standard_price to the current layer cost at time of migration. Future FIFO layers are re-derived from receiving transactions after migration.

GSS multi-level BOMs with engineering revisions and routing steps require flattening or nesting during migration. Odoo enforces single-level BOMs at each assembly level; we either split GSS multi-level BOMs into parent and child mrp.bom records with a phantom BOM type for sub-assemblies, or consolidate into a single-level BOM if the customer prefers flat structures. Routing steps with work center assignments become Odoo work orders linked to the mrp.bom. Pending ECO revisions are flagged as draft BOMs for the customer's engineering team to activate post-migration.

GSS routing steps define operation sequences, work centers, setup time, run time, and labor rates per operation. We map each GSS operation to an Odoo work order with a corresponding work center that carries capacity and time efficiency factors. Actual labor hours posted against GSS work orders migrate as Odoo workorder time tracking records linked to the employee who performed the operation. Work order status (released, in-progress, complete) maps to Odoo mrp.workorder state values.

Open and historical sales orders migrate to Odoo sale.order with line items, pricing, due dates, and fulfillment status. Backorder quantities from GSS carry as Odoo sale.order.line records with delivered quantity less than ordered quantity. GSS sales order header fields (order type, customer PO reference, shipping terms) map to Odoo sale.order custom fields we pre-create during schema setup. Closed sales orders archive as Odoo records with state = done for historical reporting.

Open purchase orders migrate to Odoo purchase.order with vendor assignment, line items, expected receipt dates, and landed cost allocations. GSS PO line items with receipt status (pending, partial, complete) map to Odoo's order quantities and incoming moves. Closed POs are archived as Odoo records with state = done. Landed cost allocations from GSS (freight, duty, handling) carry as Odoo valuation layers on received products rather than as PO line items.

GSS work orders link to BOMs and define production schedules with start and end dates, assigned work centers, and labor hour estimates. Completed operations history and actual labor postings migrate as Odoo mrp.workorder time tracking records. Work order component consumption (the materials issued to the job) migrates as Odoo stock moves linked to the production order. Work order status from GSS (released, in-progress, on-hold, complete) maps to Odoo mrp.production state, and the original GSS work order number is preserved in a custom reference field.

GSS chart of accounts with account numbers, descriptions, types, and department distribution flags maps to Odoo account.account records with matching codes and names. We preserve account balances from GSS at the point of migration as Odoo opening entries via account.move, and carry forward department or cost center distribution as Odoo analytic accounts. Inter-company elimination entries from GSS multi-company setup require manual reconfiguration in Odoo's multi-company environment post-migration.

Open GSS AR invoices, credit memos, and cash receipts migrate to Odoo account.move records with move_type = 'out_invoice', 'out_refund', or 'entry' for payments. Customer payment terms and aging buckets map to Odoo's account.payment.term and the partner's credit limit fields. Historical AR aging is preserved as Odoo open invoice records with the original invoice date and due date for collection reporting.

Open GSS AP vouchers, invoice images, and 3-way match status migrate to Odoo account.move records with move_type = 'in_invoice', 'in_refund', or 'entry' for payments. Vendor payment terms and discount eligibility carry forward to Odoo's account.payment.term and product supplierinfo records. Accrued payables from GSS are mapped to Odoo account.move records with appropriate accrual account assignments for the customer's period-end close process.

GSS employee records with demographics, department assignments, pay rates, exempt/non-exempt status, and PTO balances migrate to Odoo hr.employee. Year-to-date earnings and payroll history carry forward as Odoo hr.payslip records with historical status for tax and benefit reporting. GSS timekeeping data tied to work orders maps to Odoo mrp.workorder time tracking records linked to the responsible employee. Note that Odoo requires the hr and manufacturing apps to be installed for full employee-to-workorder labor mapping.

GSS inspection results, SPC data points, non-conformance records, and corrective action logs tied to work orders and inventory lots migrate to Odoo quality.alert and mrp.report records. Odoo's Quality app handles inspection checklists and alerts but does not replicate GSS's full SPC charting and statistical process control. We preserve the inspection data as quality.alert records with a reference to the production lot, and flag for the customer's quality team whether the existing QC workflow requires process redesign in Odoo for ISO/AS9100 compliance.

GSS user-defined fields attached to any object are stored as GAB custom properties with specific data types. We extract every custom property definition and its values from the GSS database or file export and create equivalent Odoo custom fields using ir.model.fields with matching types (char, float, integer, date, selection, many2one). Multi-select custom properties from GSS become Odoo selection or many2many fields depending on the cardinality of values. The customer reviews the custom field list and confirms which ones are still active and required in Odoo.

Documents attached to transactions, work orders, or the item master in GSS may be stored in Box, SharePoint, or the GSS document control module. We export the file metadata (filename, document type, linked entity, date) and map it to Odoo's ir.attachment records pointing to the migrated entity (stock.move, mrp.production, res.partner, etc.). If the customer uses the Odoo Document app, we create the corresponding document records with folder structure mapped from the GSS document taxonomy. Binary file content migrates where it can be extracted from GSS; URLs to externally hosted documents are preserved as link fields.