Migrate from iDempiere to Odoo ERP

iDempiere Business Partners cover customers, vendors, and leads with location tabs (address, contact details, pricing schema) stored as child records. We split these into Odoo Company records (the organizational entity with address) and Contact records (the individual at the company with role, phone, email). The iDempiere BP Credit Limit becomes the Odoo Company credit_limit field; BP Group maps to Odoo Tags on Contact. Credit status and payment terms carry forward. The split resolves the parent-lookup dependency so that Contacts import after Companies.

iDempiere Products with BOM structures, costing data, and category assignments map directly to Odoo Product records. Product type (Item, Service, Resource) maps to Odoo Product Type. iDempiere's Product Category hierarchy becomes Odoo Product Category. BOM lines migrate to Odoo Manufacturing BOMs. Stocking settings, reorder points, and variant configurations carry forward as Odoo product variants linked to attributes.

iDempiere Sales Orders with header/line structures and payment schedules map to Odoo Sale Order. Document status (Draft, CO, VO, CL) maps to Odoo's sale order state. Lines include product, quantity, unit of measure, and price list data. The associated Business Partner reference resolves to the Odoo Company lookup via the Contact-Company split applied earlier. Taxes and discount rules carry forward as Odoo tax and pricelist configurations.

iDempiere Purchase Orders map to Odoo Purchase Order with the same header/line structure. Vendor BP references resolve to the Odoo Contact-Company lookup. Landed cost lines and shipment schedules are preserved as purchase order lines with the same unit price and tax treatment.

iDempiere AR and AP invoices migrate to Odoo account.move records with move_type distinguishing customer invoice (out_invoice), customer credit note (out_refund), vendor bill (in_invoice), and vendor credit note (in_refund). Document status, tax treatment, payment terms, and GL journal line references carry forward. Open AR/AP aging data is preserved as Odoo receivable/payable balances on the contact record.

iDempiere Projects with phases, tasks, time entries, and milestone tracking map to Odoo Project. Phase becomes Odoo Project with child task stages. Resource assignments migrate as Odoo Project members. Custom project types defined in the iDempiere Application Dictionary are flagged separately because the table data migrates but the visual form layout requires manual rebuild in Odoo Studio.

iDempiere Fixed Asset registers with depreciation schedules and insurance mappings migrate to Odoo Asset Management. Depreciation method, book value, and service history carry forward. iDempiere's asset book and depreciation posting schedule reconstruct as Odoo asset lines with move_ids linking to the accounting entries.

iDempiere payment batches, cash journal entries, and bank statement mappings with allocation details migrate to Odoo account.move records posted through the appropriate bank or cash journal. Open AP/AR allocations and aging bucket assignments carry forward. Bank statement reconciliation data (where stored in iDempiere's bank statement matching tables) migrates as Odoo bank reconciliation lines.

iDempiere custom windows registered in the Application Dictionary are backed by database tables. We export the underlying table data and AD registration metadata (column names, data types, constraints). The visual form layout (tab structure, field positioning, display logic) does not migrate and requires reimplementation in Odoo Studio or as Python module XML. We deliver a written inventory of every custom AD window with its table schema and a Studio rebuild recommendation.

iDempiere multiple accounting schemas per Client with dimensional GL dimensions (Legal Entity, Business Partner, Product, Location) require reconstruction in Odoo. Each iDempiere accounting schema becomes an Odoo Company with its own chart of accounts. GL journal lines migrate as Odoo account.move.line records, with dimension tagging reconstructed via Odoo analytic accounts and fiscal positions. We do not migrate historical GL balances as locked periods; we post them as opening entries in the target accounting date range.

iDempiere multi-org structure (Client > Organization) must be recreated before any user or master data import. Each iDempiere Organization maps to an Odoo Company with its own address, chart of accounts, and warehouse assignment. iDempiere Users and role-privilege assignments map to Odoo Users with portal access if applicable. Role-permission records are documented in the handoff inventory; Odoo group-based access control replaces the iDempiere role model.

iDempiere tax categories, rates, validity windows, and jurisdiction assignments per location migrate to Odoo account.tax records with the same effective dates and scope (sale, purchase, none). Tax jurisdiction logic from iDempiere becomes Odoo fiscal positions linked to country or state rules.