Migrate from Guardian Software to Dolibarr ERP

Guardian customer records map directly to Dolibarr ThirdParty (societe) entries. Address, contact details, customer classification, and payment terms transfer as typed fields. Dolibarr groups customers and suppliers under the same ThirdParty object with a Tiers type flag; we set the flag to Customer during import. The customer code from Guardian becomes the ref (reference) field in Dolibarr and serves as the dedupe key.

Guardian production orders map to Dolibarr sales orders (Commande client) for customer-facing orders or to the production module's work orders where that module is enabled. Order status, quantities, scheduled dates, and work centre assignments transfer. Dolibarr's production module is community-contributed and may not be active in all deployments; we verify its availability during schema design and configure it before production orders are imported if the module is present.

Guardian material inventory splits into Dolibarr Product (the item definition) and Stock (the warehouse quantity). Alloys, raw materials, and finished castings are created as Dolibarr Products with the correct type (Stockable, Service, or Product). Inventory balances, reorder points, and unit-of-measure conversions are written to llx_product_stock. Bin and location data from Guardian maps to Dolibarr warehouse location fields if configured.

Guardian inspection results, non-conformance reports, and certificates of conformance do not have a native Dolibarr equivalent. We map quality disposition codes to custom fields on the relevant Product record (e.g., quality_status, last_inspection_date, cert_number) and link conformance certificates as Dolibarr documents attached to the Product. Complex NCR histories with multi-level dispositions may require a dedicated custom object or a project-linked approach.

Guardian equipment master records (machines, furnaces, tooling) with maintenance schedules, depreciation data, and location assignments map to Dolibarr Asset. Asset category, serial number, acquisition date, and depreciation method transfer directly. Dolibarr's asset module handles fixed-asset tracking and depreciation posting to the GL.

Guardian work centre routing with step sequences, labor hours, and machine hours has no direct Dolibarr equivalent outside the community production module. We map routing steps to Dolibarr Project tasks (for sequencing and time tracking) or to Bill of Materials lines where the production module is active. Complex multi-step routing with parallel work centres may require post-migration manual recreation in Dolibarr's production module. We flag this gap during scoping.

Engineering drawings, batch sheets, and compliance certificates stored as file attachments in Guardian export alongside their parent records and are re-associated in Dolibarr via its document management (GED) module. We preserve filename and upload date. Dolibarr's document storage path is configurable via dolibarr_main_data_root.

Guardian user accounts with role-based access control map to Dolibarr User records matched by email. Role names and permission sets vary between platforms; we map the most common role equivalencies (Admin, Production Manager, Quality Inspector) but recommend a post-migration access review against Dolibarr's permission module to align with the destination's permission model.

Guardian account codes and cost-centre structures for financial integration map to Dolibarr Chart of Accounts (llx_accounting_account). Foundry-specific cost pools such as scrap cost, rework cost, and tool-wear require explicit account-code mapping to ensure GL continuity in Dolibarr. We build an account-code crosswalk during discovery, mapping each Guardian cost pool to a Dolibarr account code in the same fiscal structure.

Guardian user-defined fields on standard objects for foundry-specific tracking (alloy grade codes, melt identities, lot numbers) are extracted with their data types and picklist values. We recreate them as Dolibarr Extra Fields (champs extras) on the corresponding Dolibarr object. Complex formula fields from Guardian may require manual re-creation as Dolibarrcalculated fields or report objects.

Historical journal entries for cost accounting and period closes transfer as Dolibarr accounting entries (llx_accounting_accounting). Entry headers and line items with account references, debit and credit amounts, and dates migrate. Reversing entries and adjustment flags are preserved where the destination schema supports them. Period-close status from Guardian does not carry over and must be re-established in Dolibarr.

Open and closed PO headers with line items, quantities, prices, and vendor assignments map to Dolibarr supplier orders (Commande fournisseur). Vendor cross-references from Guardian are remapped to match Dolibarr's ThirdParty vendor records using the vendor account code as the matching key. PO status (open, received, closed) transfers to Dolibarr's order status values.