Migrate from Freedom ERP to Odoo ERP

Freedom ERP customer records map to Odoo res.partner with partner_type=contact and customer_rank set to distinguish from vendor records. We extract name, phone, email, GST number, billing and shipping address, payment terms, and credit limit from the Sales module. The res.partner record is created before any sales order or open AR import so that the customer reference is satisfied at insert time. GSTIN migrates to the l10n_in_gstin field if the Odoo instance has the India - GST module installed.

Freedom ERP vendor records map to Odoo res.partner with partner_type=supplier and supplier_rank set. We extract vendor name, contact info, tax registration, payment terms, and any linked purchase order or GRN history. The vendor record is created before open AP import so that the supplier reference is satisfied on invoice records.

Freedom ERP items—raw materials, intermediates, and finished goods—map to Odoo product.product with product_tmpl records generated from item masters. We extract item code, name, UoM, cost price, sales price, product type (stockable/consumable/service), and warehouse assignment. The item must exist in Odoo before any BOM or production order that references it can be imported. Multi-UoM handling (e.g., pieces per kg) maps to Odoo's unit of measure categories and conversion rules.

Freedom ERP BOMs with multi-level component structures, phantom assemblies, and co-products require full tree reconstruction before migration. We extract the complete BOM hierarchy from Freedom's production tables, compute component quantities and scrap rates per operation, and map to Odoo's mrp.bom with bom_line records. Odoo's bom_type field (normal/kit/subassembly) maps to Freedom's manufacturing mode (discrete/process/kit). This step adds a planning day to the migration scope but prevents incorrect production costing downstream.

Freedom ERP account records map to Odoo account.account with account_type, account_group, and GST/S-tax mapping preserved. The full COA structure—parent groups, cost center assignments, and tax reconciliation accounts—migrates before any open AP/AR or journal entry import. Odoo's l10n_in chart of templates (India-localized) provides the base structure; custom Freedom accounts are mapped to the closest standard type or created as custom accounts per the customer's COA design.

Outstanding payables and receivables from Freedom ERP migrate as Odoo account.move records (type=out_invoice for AR, in_invoice for AP). We extract invoice number, date, partner reference, line items, tax amounts, and due date. Reconciliation is preserved by setting the matched partner and open amount so that Odoo's partial reconciliation handles split payments. Closed invoices are not migrated unless the customer specifically requests historical invoice import; moving only open balances keeps the initial dataset manageable.

Freedom ERP production orders link to BOMs, work centers, and scheduling dates, with schema variation between discrete and process manufacturing modes. We extract work orders with their routing, operation sequences, and component consumption records, then map to Odoo mrp.production with bom_id, product_qty, and date_planned_start preserved. Routing operations migrate to Odoo's mrp.routing.workcenter structure. Closed production orders may be migrated as historical records or omitted based on the customer's reporting needs.

Freedom ERP employee records map to Odoo hr.employee with personal details, department, designation, date of joining, and org hierarchy preserved. We extract all active and inactive employee records and map department names to Odoo hr.department lookups. Employee status (active/inactive) migrates as the active flag in Odoo. These records are required before any payroll payrun import so that the employee reference is satisfied.

Freedom ERP payroll data—salary components, deductions, and payrun history—maps to Odoo hr.payslip and hr.payslip.line records. We extract payrun summaries and individual earning records per employee, map Freedom salary structure rules to Odoo's salary rule system (which requires configuration by the customer's HR admin or a local Odoo payroll partner), and import current-year open payslips. Historical closed pay periods migrate as payslip records with state=done. Post-migration Odoo payroll configuration for India-specific ESI/PF/Gratuity compliance is scoped separately as it requires HR partner involvement.

Freedom ERP QC inspection records link to production lots and item batches. We extract inspection results, defect logs, and custom inspection criteria fields and map them to Odoo's quality module (quality.alert for non-conformance, quality.check for inspection records). Custom QC criteria fields that have no Odoo standard equivalent are stored as text notes on the alert record for manual review post-migration.

Equipment and machine maintenance logs from Freedom ERP include work orders, spare parts consumed, and technician assignments. We export maintenance history and map to Odoo maintenance.request records with equipment_id, maintenance_type, and assigned technician preserved. Spare parts consumed migrate as maintenance request line notes; a full spare parts inventory mapping would require a separate inventory migration scope.

Freedom ERP project definitions, milestones, tasks, and resource assignments map to Odoo project.project and project.task records. We extract task dependencies, assignees, and milestone dates. Project billing integration (timesheet vs milestones) requires Odoo project app configuration and is noted as a post-migration configuration step.