Migrate from Focus ERP to Odoo ERP

Focus ERP's account structures with parent-child hierarchies and account types export cleanly via the database layer. We preserve account codes and descriptions exactly, including any segment columns used for cost-center reporting. Odoo's account.account model accepts the same hierarchical structure, and we set the account type (receivable, payable, asset, expense, revenue) using Odoo's standard type taxonomy. Multi-company account scopes are preserved as Odoo shared or company-specific accounts depending on the destination Odoo plan.

Focus ERP customer master records migrate to Odoo res.partner with vendor=False. We map billing address to partner address fields, payment terms to property_payment_term_id, and tax registration numbers to vat. The name-and-address combination serves as the deduplication key for multi-company Focus ERP instances. Customer-specific pricing rules stored as custom fields in Focus ERP are preserved as Odoo product.pricelist rules against the customer partner group.

Focus ERP vendor master records map to Odoo res.partner with vendor=True. We carry forward payment terms, bank details stored in Focus ERP's vendor record, and tax registration numbers into the Odoo partner record. For vendors with multiple purchasing contacts, we create child contact records under the vendor partner. Multi-company vendor assignments in Focus ERP are preserved as tags on the Odoo partner record.

Outstanding payable and receivable records from Focus ERP carry invoice numbers, due dates, outstanding amounts, and full payment histories. We extract each open item and create draft vendor bills or customer invoices in Odoo, linked to the resolved vendor or customer partner. Partial payments, credit memos, and misaligned invoice dates require explicit customer confirmation before we commit the load because Odoo's reconciliation process handles these differently than Focus ERP's payment tracking.

Focus ERP item masters with SKUs, descriptions, cost prices, selling prices, and current stock levels migrate to Odoo product.product. We translate Focus ERP item type values to Odoo's storable, consumable, and service product types during the transform step. Min/max replenishment rules configured in Focus ERP are extracted as numeric custom fields and re-implemented as Odoo procurement rules or route configurations post-migration. Serial and lot tracking settings migrate where the source data is populated.

Open and historical purchase orders map to Odoo's purchase.order model with purchase.order.line children. Line-level tax codes and discount percentages vary by Focus ERP country configuration and require explicit value mapping against the destination Odoo company's fiscal position before load. We preserve the original PO number, order date, and expected delivery date. Closed PO statuses map to Odoo's purchase order states (purchase, done, cancel).

Focus ERP sales orders migrate to Odoo sale.order with sale.order.line children. Similar to purchase orders, line-level tax codes and discount percentages are configuration-dependent and require explicit mapping against the destination Odoo fiscal position. Sales order status from Focus ERP maps to Odoo's sale.order states (sale_order, done, cancel). Historical SO totals are preserved for financial reconciliation against the migrated invoice history.

Focus ERP field-service and job-tracking records carry custom status workflows, technician assignments, and job-percentage progress fields. We capture the original status values, assigned technician names, and progress percentages as custom fields on whatever Odoo app the customer selects: project.task for job management, maintenance.equipment for asset servicing, or fsm.order for field service routes. We flag the custom status-to-Odoo-status mapping for customer confirmation during scoping.

Focus ERP asset registers include acquisition dates, original depreciation methods, and book values. We extract the original depreciation method, acquisition cost, and accumulated depreciation as custom fields on Odoo's account.asset model. Odoo recalculates the future depreciation schedule based on its own fiscal year settings, which may differ from Focus ERP's company fiscal year configuration. We document the original depreciation run and residual value for the customer's accountant to verify after migration.

Focus ERP user accounts and role permissions export from the user table, but role naming conventions differ between Focus ERP versions and Odoo's internal permission model. We extract role assignments as user-level permissions and rebuild equivalent Odoo access groups (accounting group, inventory group, field service group, etc.) post-migration in Odoo Settings. The customer's admin validates group membership against the exported permission list.

Custom fields added via Focus ERP's form builder are stored in extended database tables. We extract these as key-value pairs attached to the corresponding Odoo object using Odoo Studio or direct XML-RPC field creation. Field type compatibility varies: numeric and text fields map directly, but picklist fields require Odoo selection field creation, and relational fields require pre-creation of the destination model before the data import phase.