Migrate from Freespace ERP to Odoo ERP

Freespace ERP organizes GL accounts around industry-specific modules (manufacturing cost centers, wholesale distribution buckets) rather than a generic chart-of-accounts structure. We enumerate every Freespace account code and its associated cost-center dimension, then map each to an Odoo Account (account.account) record with a corresponding Analytic Account (account.analytic.account) for cost-center and project tracking. Dimension names from Freespace (department, production line, shift) map to Odoo analytic tags or analytic account hierarchies. We flag any Freespace accounts that carry balances but have no clear Odoo equivalent, presenting the customer with a choice to map to a catch-all Expense or Income account or to create a new Odoo account code.

Freespace Customer and Vendor records export via the platform's API with name, contact details, billing address, and payment terms. We preserve these fields 1:1 into Odoo res.partner records with the customer (customer_rank) or supplier (supplier_rank) flag set appropriately. We strip non-alpha ASCII characters from partner names before import because Odoo's res.partner model enforces stricter character validation than Freespace. Payment terms from Freespace appear as picklist values; we map these to Odoo account.payment.term records using a term-code lookup table created during scoping.

Freespace Item masters include SKU, description, unit of measure, standard cost, and sales price. We map these to Odoo product.product records linked to product.template. The Freespace item type (finished good, raw material, subassembly) determines the Odoo product type: Odoo type = 'product' for inventory-tracked items, 'consu' for consumables, 'service' for services. Unit of measure and UoM category map to Odoo's uom.uom model with the relevant category.

Freespace multi-level BoM structures (where subassemblies reference their own child BoMs) require a scoping decision in Odoo: preserve as nested mrp.bom records with type='subassembly', or flatten to a single-level explosion with type='kit'. Odoo's MRP module handles both models but with different planning behavior. We present the customer with a written BoM handling recommendation based on their production order history and Odoo MRP configuration, then execute the chosen strategy during migration. The mrp.bom.line records carry component, quantity, and unit of measure mapped from Freespace BOM components.

Open vendor invoices export from Freespace with document date, due date, total amount, and payment terms. We map these to Odoo account.move records of type='in_invoice' with vendor_id set to the matched res.partner. Payment terms resolve to account.payment.term via the term-code lookup. Freespace invoice line items map to account.move.line records with account_id set from the COA mapping. Open AP credit memos map to account.move with type='in_refund'.

Open customer invoices export from Freespace with document date, due date, amount, and payment terms. We map to Odoo account.move records of type='out_invoice' with partner_id set from the customer mapping. Payment terms resolve via the term-code lookup. Invoice lines map to account.move.line with revenue accounts from the COA mapping. Freespace payment records (partial or full receipts) map to account.payment records linked to the matched account.move.

Freespace production orders export with stage names (user-defined in Freespace), quantities, and material consumption links. The Freespace stage names are arbitrary strings; we map these to Odoo mrp.production state values (draft, confirmed, in_production, done, cancel) or to custom mrp.production.stage records if the customer uses Odoo 16+ stage tracking. The Freespace product, bom_id, and quantity transfer directly. Material consumption lines (Freespace material issues) map to mrp.workorder.record_production_lot or stock.move records in Odoo.

Freespace work orders associated with production orders map to Odoo mrp.workorder records linked to the parent mrp.production. Work center, planned duration, and operation sequence transfer from Freespace. If Freespace tracks time logging per work order, we map these to mrp.workorder time tracking records (duration, user, date). Work order routing dependencies (next operation, predecessor) map to Odoo's operation chaining via workorder dependencies or linked mrp.workorder records.

Freespace compensation records carry effective-dated rows with pay frequency, salary or wage rates, and deduction codes. Retroactive adjustments can produce rows where the effective date is earlier than the record creation date, producing non-sequential ordering. We flag these gaps during extraction and sort compensation rows by effective date before importing, ensuring Odoo receives a chronologically consistent compensation timeline. If Odoo Payroll is not installed, we map compensation data to hr.contract wage fields and flag additional fields for manual entry or custom module build.

Freespace employee profiles include name, department, job title, hire date, employment status, and any custom employee properties added during onboarding. We enumerate active custom field definitions during scoping against Freespace's field management UI, explicitly including them in the export field list. Each employee maps to hr.employee in Odoo with department_id from the analytic account mapping and job_title from the source field. Employment status (active, inactive) maps to active flag in hr.employee.

Freespace allows administrators to add custom properties to standard objects during onboarding; these fields may not appear in the default export templates. We enumerate all active custom field definitions during scoping, explicitly including them in the export field list. Each Freespace custom property becomes an ir.model.fields record in Odoo (created via developer mode or XML-RPC) with the correct field type (char, selection, float, boolean, etc.) before migration begins. Custom fields on Freespace Items, Customers, Vendors, and Employees migrate as Odoo res.partner, product.product, or hr.employee custom fields respectively.

Freespace transaction history includes production orders, material issues, and inventory movements across multiple warehouses or locations. These are often large-volume exports requiring chunking by date range. We sequence entries by posting date, split by stock.location (source and destination) mapped to Odoo stock.location records, and import as stock.move records linked to stock.picking where applicable. If Odoo's inventory history retention settings would purge these records, we advise the customer to adjust stock.scrap and inventory configuration before migration.