Migrate from Finesse ERP to Odoo ERP

Finesse Customer records with address, contact, payment terms, credit limits, and tax IDs map directly to Odoo Res Partner records with customer rank. We preserve credit_limit and property_payment_term fields on the Partner, and flag any customer with an active project in Finesse for pre-migration project linkage in Odoo Project. Multi-address customers in Finesse create separate Partner Address records in Odoo.

Finesse Vendor master data including bank details, W-9 information, and payment terms maps to Odoo Res Partner records with vendor rank. Multi-address vendor records (ship-from locations) are handled by creating separate contact records under the vendor partner with address_type=delivery. We extract any vendor-specific GL accounts (e.g., expense accrual accounts) for Odoo Chart of Accounts mapping.

Finesse GL accounts map to Odoo Account records with type, code, and description. Account types (Asset, Liability, Equity, Revenue, Expense) map directly; the is_analytic_allowed flag is set for accounts eligible for analytic distribution. Active versus inactive status carries over explicitly. Project cost-center segments in Finesse map to Odoo Analytic Account records for manufacturing cost tracking.

Finesse Item master records map to Odoo Product Product. The item type (stockable, consumable, service) maps to Odoo's type field. Finesse unit of measure and costing method (standard, average, FIFO) map to Product UoM and Product Costing Method fields. We extract any landed cost components and extra costs stored at the item level for Odoo landed cost configuration.

Finesse BOMs (multi-level, quantity-based) map to Odoo MRP BoM records. Finesse BOM type (make-to-order, make-to-stock) maps to Odoo BoM type with a note for manual routing configuration if the source used Finesse-specific routing logic. Component line quantities and bom_level sequence preserve multi-level BOM structure in Odoo's parent_id reference. Any phantom BOM logic from Finesse requires Odoo Kit Product configuration.

Finesse routings with work centers, cycle times, and labor rates map to Odoo MRP Work Center records and Routing Workcenter lines. Finesse work center codes become Odoo Work Center names; capacity_per_cycle and time_efficiency carry over. We flag any Finesse routing with operation dependencies that require Odoo's res_config_settings manufacturing configuration for sequence control.

Finesse Projects aggregate jobs, milestones, cost variance, and status under a single header. We split this into Odoo Project (for milestone tracking and task management) and MrpProduction records for manufacturing execution. Project cost variance fields migrate as analytic entries linked to Odoo's Account Analytic lines. Any Finesse project with no manufacturing component stays as a pure Odoo Project record.

Finesse Jobs with start dates, quantity, priority, and cost tracking map to Odoo MrpProduction (manufacturing order). Job status from Finesse maps to Odoo MrpProduction state (draft, confirmed, planned, in_production, done, cancel). Line-level cost entries from Finesse (labor and material postings) become Odoo StockMove records linked to the production order. We preserve original job numbers in the origin field of mrp.production.

Finesse open AP invoices and credit memos migrate as Odoo account.move records with move_type=in_invoice or in_refund. We export line-item detail rather than summary balances to preserve aging accuracy. Vendor references resolve to the mapped Res Partner record; payment terms resolve to Odoo account.payment.term. Any AP record with a dispute or hold flag is flagged for manual review before destination activation.

Finesse open customer invoices and unapplied payments migrate as Odoo account.move records with move_type=out_invoice or out_refund. Full aging detail preserves for Odoo's Account Aged Receivable report. Any AR record with nested dispute, credit hold, or overpayment flags is flagged for pre-activation manual review. Payment terms map to Odoo account.payment.term.

On-hand quantities by location and lot number migrate to Odoo stock.quant records. We flag any negative quantities or quantities below safety stock for pre-migration reconciliation against Odoo's stock.resupply_point thresholds. Finesse location codes map to Odoo stock.location records with location_type (internal, partner, inventory, production). Lot and serial numbers carry over as stock.lot records linked to the quant.

Finesse user-defined fields on master and transaction records export with their definitions and values. We create matching custom fields in Odoo via the Settings > Technical > Custom Fields interface or direct ir.model.fields creation. Field types are mapped: Finesse text becomes char or text, date becomes date, numeric becomes float or monetary, dropdown becomes selection. Custom fields on Finesse Jobs and Projects map to x_ prefixed fields on mrp.production and project.project.