Migrate from Jeeves ERP to Odoo ERP

Jeeves hierarchical chart of accounts maps directly to Odoo account.account with account.code, name, and user_type fields preserved. Account types (asset, liability, equity, income, expense) map to Odoo's account.account.type selection. We flag any multi-currency account assignments because Odoo handles multi-currency at the company or journal level, not the account level. The first Odoo migration step is always Chart of Accounts because all downstream journal entries and AP/AR records reference account codes.

Jeeves customer master records (contact details, billing and shipping addresses, credit limits, payment terms) map to Odoo res.partner with partner_type = contact. Jeeves customer-specific pricing and discount groups map to Odoo pricelist and product.pricelist.item records. Multi-currency assignments on Jeeves customers migrate to the partner's property_payment_term_id and property_supplier_payment_term_id fields. Billing address is stored as res.partner; shipping address as a child res.partner record with type = delivery.

Jeeves vendor master records map to Odoo res.partner with partner_type = contact and customer_rank = 0, supplier_rank = 1. Supplier-specific fields (payment terms, bank details, lead times) migrate to the partner's property_supplier_payment_term_id and associated contact fields. Multi-currency vendor assignments carry over to Odoo currency configuration on the partner record.

Jeeves Items cover products, materials, and services with BOMs, routing, cost layers, and UoM settings. Odoo enforces a mandatory product.template → product.product structure (template for shared attributes, variants for attribute combinations). Jeeves items without variants map to a single product.product linked to one product.template. Items with BOMs preserve cost layer data in the product.template's standard_price field. We flag any Jeeves items with more than three variant attributes because Odoo's variant generation scales polynomially and requires attention during import sequencing.

Jeeves BOM structures and component lines map to Odoo mrp.bom with mrp.bom.line records for each component. Odoo requires Work Centers (mrp.workcenter) to be provisioned separately before BOM operations can reference them. Multi-level BOMs (BOM referencing another BOM) require careful sequencing because Odoo resolves multi-level explosion at the work order level, not at import time. We import parent-level BOMs first, then child-level BOMs, then validate with Odoo's where_used report.

Jeeves routing definitions with work center assignments, cycle times, and sequence steps map to Odoo mrp.workcenter records and mrp.bom.operation lines on the corresponding mrp.bom. Odoo's operation model uses workcenter_id, name, time_cycle (minutes), and sequence to define the routing. We create work centers during the staging migration and reference them by name in the BOM operation import. Note that Odoo does not have a direct equivalent to Jeeves's granular routing with alternate work centers; we map the primary routing and document alternates for the customer's Odoo admin to configure post-migration.

Jeeves fixed asset records (acquisition cost, depreciation schedule, asset category, asset life, and current book value) migrate to Odoo account.asset. Depreciation methods (straight-line, declining balance, sum-of-years-digits) map to Odoo's depreciation method selection. We flag country-specific tax depreciation rules that Jeeves may enforce and that Odoo implements through localization modules. The customer must select the correct Odoo localization module (l10n chart of accounts package) before fixed asset migration begins.

Outstanding Jeeves payables and receivables migrate as Odoo account.move records of type entry, with debit and credit lines referencing account.move.line and the partner's account receivable (property_account_receivable_id) or account payable (property_account_payable_id). Open invoice amounts, due dates, and payment terms carry over. Closed invoices migrate as historical account.move records with the same structure. Odoo requires the journal to be configured with correct default accounts before AP/AR migration begins.

Jeeves journal entries (date, description, debit/credit lines, account assignments, reversing entry flags) map to Odoo account.move with move_type = entry. Jeeves journal entry numbering schemes migrate to Odoo sequence configurations on the relevant journal. Reversing entries from Jeeves create a new Odoo account.move with reversal_date set. We apply date-based filtering for historical journal entries during planning scope to avoid migrating closed-period entries that would trigger Odoo's lock date restrictions.

Open Jeeves sales orders migrate as Odoo sale.order records in draft or confirmed state depending on the original document status. Line items with product, quantity, unit price, discount, and delivery date map to sale.order.line. We flag orders with partially shipped quantities for manual reconciliation because Odoo's delivery picking flow may differ from Jeeves's fulfillment state tracking. Confirmed orders with pending deliveries land in sale.order confirmed state; draft or pending-approval orders land as sale.order draft for the customer's sales team to confirm.

Open Jeeves purchase orders map to Odoo purchase.order with purchase.order.line records for each line item. Delivery schedules, quantities, and payment terms carry over. Jeeves purchase orders in confirmed or partially received state land as purchase.order confirmed in Odoo; pending approval orders land as draft. We flag purchase orders with complex multi-line discounts because Odoo's taxes-and-discounts model requires the discount to be assigned per line rather than at the header level.

Jeeves project records with associated tasks, milestones, time entries, and expense recordings map to Odoo project.project with project.task child records. Billable time entries migrate as Odoo account.analytic.line records linked to the project. Milestone tracking from Jeeves maps to Odoo project milestones (available in Odoo Enterprise) or project.task stage as a proxy. Non-billable Jeeves project types map to project.project with allow_billable = False.