Migrate from Edara to Odoo ERP

Edara's account codes, names, types (asset, liability, equity, revenue, expense), and active/inactive status map 1:1 to Odoo's account.account records. We preserve account_code as a separate field and map Edara's account type to Odoo's account_type selection (asset_receivable, asset_cash, liability_payable, equity, revenue, expense). Odoo's default COA uses a different code structure (4-6 digit ranges) than Edara's; we validate the target COA structure during scoping and either align Edara's codes to Odoo's defaults or configure a custom COA to match Edara's existing account code scheme.

Edara customer records with billing/shipping addresses, contact info, payment terms, and currency assignments map to Odoo res.partner records with type=contact and customer_rank elevated. Edara's customer currency assignment maps to Odoo's property_payment_term_id and property_account_position_id for tax handling. We flag duplicate vendor names and reconcile against open AR balance before committing to prevent duplicate contacts.

Edara vendor master records including addresses, tax IDs, and default payment/purchase terms map to Odoo res.partner with supplier_rank elevated and the appropriate property_account_position_id for tax treatment. Vendor currency defaults migrate alongside purchase terms. We check for name collisions with customer contacts and resolve duplicates before import.

Edara item master records including SKU, description, cost, price, unit of measure, and warehouse assignments map to Odoo product.product records linked to product.template. We preserve unit_of_measure conversions in Odoo's uom.uom model and map Edara's inventory valuation method (standard, average, FIFO) to Odoo's product category valuation_type. Negative stock entries from Edara are flagged for reconciliation before Odoo import.

Open receivables are exported from Edara's aging report with outstanding amount, due date, currency, and customer reference. We create Odoo account.move records of type out_invoice in draft state, preserving the original invoice date, due date, and amount. Currency conversion uses Edara's recorded exchange rates to match Odoo's multi-currency ledger. Reconciled open items are flagged for manual review before posting.

Open payables migrate as Odoo account.move records of type in_invoice in draft state. We export Edara's vendor aging report, preserving vendor reference, open amount, due date, and currency. Vendor bills are linked to the corresponding res.partner supplier record. Any vendor invoices marked as partially paid in Edara carry a residual amount into Odoo for continued reconciliation.

Edara sales orders with line items, quantities, pricing, salesperson attribution, and warehouse assignment map to Odoo sale.order records. On Edara Pro-plan instances, we detect the 30,000-order monthly cap during discovery and stage the export in monthly batches aligned with the billing cycle. We map Edara's order status (draft, confirmed, shipped, invoiced) to Odoo's state field (draft, sale_order, done). Salesperson attribution maps to Odoo's user_id on the order header.

Edara purchase orders with vendor assignments, line items, quantities, pricing, and approval status map to Odoo purchase.order records. PO confirmation status migrates as Odoo state (draft, sent, purchase, done). Linked receipt records in Edara map to Odoo stock.picking records created against the PO. We preserve any special payment terms attached to the PO.

Edara warehouse records, stock levels, and bin locations map to Odoo's stock.warehouse, stock.location, and stock.quant models. Multi-warehouse setups in Edara map directly to Odoo's warehouse structure with corresponding internal locations. Current stock quantities migrate as stock.quant records at the appropriate warehouse location. Negative quant entries from Edara (e.g., from data entry errors or partially reconciled adjustments) are flagged for the customer's inventory manager to resolve before Odoo goes live.

Fixed asset records including acquisition cost, accumulated depreciation, depreciation method, and asset life are only fully exportable from Edara's Ultimate plan. We export the depreciation schedule via Edara's financial reports and map it to Odoo asset.asset (Enterprise) or create manual depreciation journal entries in account.move (Community). Any discrepancy between the Edara asset register and the general ledger trial balance is flagged for the customer's accountant to resolve before the asset ledger is committed to Odoo.

Edara POS register configurations including base register fee, additional register assignments, and salesperson attribution map to Odoo's point_of_sale.config and point_of_sale.session models. Each Edara register becomes an Odoo POS configuration linked to the corresponding warehouse. Salesperson attribution from Edara's register setup maps to Odoo's pos.config.user_ids. We recommend a dry-run POS session in Odoo using one register to validate the cash-flow journal mapping before multi-register cutover.

Edara's multi-currency support (Pro and above) exports exchange rate history alongside transactional data. We import Edara's recorded exchange rates into Odoo's res.currency.rate table so that converted amounts match what Edara reported at the time of each transaction. For open AR/AP documents with multi-currency exposure, we preserve both the foreign currency amount and the functional currency amount in Odoo's account.move line records.