Migrate from Global Shop Solutions ERP to Dolibarr ERP

Global Shop Solutions Customers map to Dolibarr Third Parties with the Tiers type set to customer. We extract the customer name, billing address, shipping address, primary contact details, payment terms, credit limit, and open AR balance. The customer account number from GSS becomes the code client in Dolibarr. Open invoice balances and aging data map to Dolibarr Third Party properties and are carried as open receivable records in Dolibarr's invoices module.

Global Shop Solutions Vendors map to Dolibarr Third Parties with the Tiers type set to supplier. We extract vendor name, address, contact details, payment terms, 1099 settings, and open AP balance. The vendor account number becomes the code fournisseur in Dolibarr. Open voucher balances and 3-way match status from GSS carry forward as open payable records. Note that Dolibarr's supplier invoice matching is manual unless the stock module is activated to enable receiving-based matching.

Global Shop Solutions inventory items map to Dolibarr Products with type=stockable. We extract on-hand quantity, cost layer (FIFO, LIFO, or average cost), ABC classification, bin location, lead time, and the current unit cost. Multi-company inventory balances are disaggregated per Dolibarr warehouse entity. Items flagged as lot-controlled or serial-numbered in GSS require manual configuration of Dolibarr's lot/serial module post-migration.

Global Shop Solutions multi-level Bills of Materials map to Dolibarr BOM records with component items, quantities per assembly, and operation routing. The Dolibarr BOM module must be activated in the destination instance. Engineering revision control from GSS maps to the BOM revision field in Dolibarr. Pending ECOs (Engineering Change Orders) in GSS are flagged as inactive BOMs pending approval in Dolibarr. If the destination Dolibarr instance does not include the BOM module, we deliver BOM structures as a structured configuration document for manual entry.

Global Shop Solutions Work Orders map to Dolibarr Projects with task-linked production steps representing operations. The GSS work order number becomes the Dolibarr project ref. Work center assignments, labor hour estimates, and actual labor postings from GSS map to project task estimated and real durations. The linked BOM reference is preserved as a project link in Dolibarr. Completed operations history transfers as task status history on the project.

Open and historical sales orders from Global Shop Solutions map to Dolibarr Third Party Proposals (Quotations) or Customer Orders depending on the order status at migration time. Line items with part numbers, quantities, pricing, and due dates migrate directly. Back-order quantities from GSS are preserved as open line items on the Dolibarr order. Fulfillment status is set as the order status in Dolibarr. We do not migrate GSS shop floor scheduling data as Dolibarr lacks a native scheduling engine; scheduling is documented for manual or third-party tooling setup.

Open purchase orders from Global Shop Solutions map to Dolibarr Supplier Proposals (Demandes de prix) or Supplier Orders depending on status. Vendor assignment, line items with part numbers and expected quantities, expected receipt dates, and landed cost allocations carry forward. Closed POs are archived in Dolibarr with status=Closed. Received-but-not-invoiced quantities are tracked as pending receipts against the supplier order.

The GSS chart of accounts migrates to Dolibarr's accounting module only if the accounting module is activated in the destination instance. Account numbers, descriptions, account types, and department distribution flags are extracted and delivered as an account import structure compatible with Dolibarr's CSV import format. If the accounting module is not activated, we deliver the full chart of accounts as a structured configuration document for manual setup. GSS journal entries and posting history are delivered as historical records for the customer's admin to re-enter or import manually after accounting module activation.

Open GSS AR invoices, credit memos, and cash receipts migrate to Dolibarr Customer Invoice records. Invoice number, customer link, invoice date, due date, line items, totals, and payment terms map directly. Aging bucket data from GSS is preserved in Dolibarr's third-party outstanding amounts. Historical AR invoices are migrated as closed invoices for collection and audit reference. Payment history (cash receipts) from GSS maps to Dolibarr payment records linked to the corresponding invoice.

Open GSS AP vouchers, invoice images, and 3-way match status migrate to Dolibarr Supplier Invoice records. Vendor link, invoice number, invoice date, due date, line items, totals, and payment terms carry forward. 3-way match status from GSS is preserved as an invoice property note. Historical AP invoices migrate as closed invoices for audit reference. If the customer activates Dolibarr's stock module, the receiving-based match workflow becomes available for future invoices.

GSS employee records (demographics, department assignment, pay rates, exempt/non-exempt status, PTO balances, and year-to-date earnings) map to Dolibarr Users if the HR module is activated, or to Contacts with a type=employee classification if the HR module is not included. We preserve pay rates and PTO balances as extrafields on the target record. Payroll history and year-to-date earnings are migrated for tax and benefit reporting. Note that Dolibarr's native payroll module covers French/US payroll requirements with jurisdiction-specific configuration; customers with non-standard payroll requirements may need a third-party payroll integration or manual setup.

GSS quality control records—inspection results, SPC data points, non-conformance records, and corrective action logs tied to work orders and inventory lots—have no native Dolibarr equivalent. We map these to a combination of Dolibarr Product extrafields (for lot-level inspection data) and Project task extrafields (for work-order-level non-conformance records). If the customer licenses a third-party QC module from the Dolibarr marketplace, we adapt the mapping accordingly during scoping. The customer must specify the intended QC module or confirm the extrafields approach before migration design begins.

Global Shop Solutions GAB dashboards and proprietary screen definitions do not have a Dolibarr equivalent. We extract the underlying data queries and layout references from GAB screens where accessible, document the data sources and report logic, and deliver an inventory of every custom GAB screen with its purpose and the data objects it references. The customer's admin uses this inventory to rebuild equivalent views using Dolibarr's native reporting tools, ODT reporting templates, or a third-party BI connector. We do not implement the rebuilt screens within migration scope.

GSS user-defined fields attached to any object (Customers, Vendors, Inventory Items, Work Orders, GL Accounts) map to Dolibarr extrafields of equivalent data type (string, integer, decimal, date, select, checkbox). We extract all custom property definitions and their values from GSS, map each to a Dolibarr extrafield on the corresponding object, and include the populated values in the migration load. Extrazcted values are validated against the Dolibarr field type before import.

Documents attached to GSS transactions, work orders, or the item master are exported from Box, SharePoint, or the GSS document control module. We export the file binary and metadata, then re-attach each document to the corresponding Dolibarr record using Dolibarr's native document management (GED). File naming conventions follow the Dolibarr standard of module/object/ref format. Customers using Box or SharePoint integration in GSS must configure the equivalent Dolibarr external storage connector separately post-migration.

GSS multi-company and multi-location data is disaggregated into separate Dolibarr Entity records. Each GSS company code becomes a Dolibarr entity with its own third-party, product, and financial data. Inter-company transaction records (sales between GSS subsidiaries) are flagged in the migration inventory for the customer to review; Dolibarr's entity model does not natively handle inter-company elimination entries unless the accounting module is activated with entity-level journal configuration. We deliver a consolidation matrix document mapping GSS inter-company relationships to Dolibarr entity configurations.