Migrate from Guardian Software to Odoo ERP

Guardian Customer records (with address, contact details, and customer type classification) map directly to Odoo Contacts. Customer type from Guardian (e.g., foundries, pattern shops, heat treaters) maps to Odoo's Industry field or a custom contact property. We use the customer name and address as the dedupe key during import. The import runs before any related Production Orders to satisfy the Partner_id lookup.

Guardian Production Orders (order status, quantity, schedule dates, work center routing) map to Odoo Manufacturing Orders. The Guardian order number becomes the Manufacturing Order reference. Guardian production-stage values map to Odoo MO stage states (draft, confirmed, in_production, done, cancel). Where Guardian uses custom status codes not in Odoo's default stage set, we create custom Manufacturing specific attributes or add a status mapping column during import.

Guardian material records (raw materials, alloys, finished castings with location and bin tracking) map to Odoo Products with Inventory valuation configured on the product form. Unit of measure conversions from Guardian carry over as Odoo Units of Measure with theUoM/Product UoM ratio set. Reorder points migrate as Odoo Reordering Rules on the product's procurement tab.

Guardian Inspection Results, NCRs (non-conformance reports), and Certificates of Conformance map to a combination of Odoo Quality Alert (for non-conformances) and Quality Check (for inspection results). Quality codes and disposition statuses from Guardian require mapping to Odoo's quality point reasons. Attachment-based CoCs from Guardian migrate as Odoo document attachments linked to the relevant Quality Alert or MO. This mapping is complex for foundries with industry-specific disposition codes; we flag any codes without Odoo equivalents for customer review before import.

Guardian Equipment records (machines, furnaces, tooling with maintenance schedules, depreciation, and location) map to Odoo Asset Management assets. Guardian maintenance schedule intervals carry over as Odoo Maintenance Requests with the same recurrence interval. Depreciation data migrates to Odoo's Asset depreciation lines. Location assignment from Guardian maps to Odoo's asset location field.

Guardian Routing structures (step-by-step production routing through work centers with labor and machine hours) map to Odoo Work Centers (capacity and time efficiency settings) and Routings (the ordered list of operations). Guardian step sequence maps to Odoo Routing operation sequence. Step count and cycle time per step from Guardian validate against Odoo's operation duration fields; foundry process types (green sand, no-bake, die casting) may require custom work center categories if the standard setup does not capture the thermal or mechanical constraint data.

Guardian user accounts with role-based access map to Odoo Users with Groups. Guardian role names and permission sets vary widely; we map to the closest Odoo default groups (Sales, Manufacturing, Inventory, Accounting) and recommend a post-migration access review to align Odoo group assignments with the foundry's actual permission requirements. Multi-company Guardian deployments require separate Odoo company setup.

Guardian account codes and cost-center structures require mapping to Odoo's Chart of Accounts. Foundry-specific cost pools (scrap cost, rework cost, tool wear, retire pool) are the highest-risk mapping because they do not have standard Odoo equivalents. We create dedicated expense and cost-of-production accounts for each foundry cost pool and document the mapping in a written account-code matrix. GL continuity in Odoo depends on this mapping being validated before any journal entries post.

Guardian documents (engineering drawings, batch sheets, compliance certificates stored as file attachments) migrate as Odoo IrAttachment records linked to their parent record (MO, Product, Quality Alert, Asset) via the res_model and res_id foreign keys. Filename and file content preserve during import. Large attachment volumes may require batched import to stay within Odoo's attachment storage limits.

Guardian historical journal entries for cost accounting and period closes map to Odoo Account Move records. Entry headers and line items (account, debit, credit, analytic account) migrate with reversing entries and adjustment flags preserved where Odoo supports them. Period/year mapping validates against the Odoo fiscal year lock date; entries outside the fiscal year require the lock date to be temporarily opened or posted manually after migration.

Guardian PO headers with line items, quantities, prices, and vendor assignments map to Odoo Purchase Orders. Vendor cross-references from Guardian remap to Odoo's vendor master (res.partner with supplier flag). Open POs migrate with state preserved; closed POs migrate as locked or posted records. PO history for reporting purposes migrates in full.

Guardian user-defined fields on standard objects migrate as Odoo custom fields created via Odoo Studio or the ir.model.fields API. Custom field data types from Guardian (text, number, date, picklist) map to equivalent Odoo field types (char, float, datetime, selection). Picklist values migrate as selection option strings. Complex Guardian formula fields may require Odoo computed field development in Python as a post-migration customization task.