Migrate from Omni ERP to Odoo ERP

Omni ERP's Chart of Accounts (flat or segmented) maps to Odoo's account.account model. We preserve COA numbering schemes and segment structures at export time and remap account codes in journal entries and AP/AR during Odoo import. If Omni ERP uses a multi-segment COA (e.g., 1-01-0000), we create the corresponding Odoo account groups (account.group) to maintain the hierarchy. Validation: every journal entry line in Odoo must reference a valid account.id; we run a pre-flight check against the destination COA before posting any entries.

Omni ERP Customer records (with contact hierarchies, addresses, and payment terms) map to Odoo res.partner with the customer flag set. Parent-child relationships migrate as res.partner parent_id references. Payment terms from Omni ERP map to account.payment.term records created or matched during import. We preserve the Omni ERP customer code as partner.ref for dedupe matching on subsequent delta imports.

Omni ERP Vendor records map to Odoo res.partner with the supplier flag set. Vendor payment terms, bank details, and fiscal positions migrate to Odoo's corresponding fields. ACH or wire instructions stored in Omni ERP vendor records map to res.partner bank accounts (res.partner.bank) created during import. Vendor records that share an email domain with customer records are flagged for manual review to prevent duplicate res.partner entries.

Omni ERP Items (with serial/batch tracking, multi-warehouse costing, and BOM associations) map to Odoo product.product records linked to product.template. Serial and batch tracking settings migrate as product.tracking values (serial, lot, or none). Multi-warehouse cost layers from Omni ERP map to Odoo's stock.quant records for current on-hand quantities, with the average or standard cost computed from Omni ERP's costing data. Lot and serial numbers from Omni ERP migrate as stock.lot records with the product_id and company_id set correctly.

Omni ERP BOMs reference finished Items by code string rather than internal ID. We export an Item-code-to-internal-ID mapping alongside the BOM export and apply it during Odoo import by resolving the product.product record via the Item code before creating mrp.bom lines. BOM versioning in Omni ERP is preserved as a custom property string on the mrp.bom record; if the destination Odoo version supports BOM revision control natively, we map to the native revision model. Components without a resolved product reference are held in a line-error queue for manual mapping.

Open vendor invoices from Omni ERP migrate to Odoo account.move records with move_type = 'in_invoice'. Each invoice line references the vendor res.partner, the expense account from the COA mapping, and the AP account (res.partner.property_account_payable_id). Payment state in Odoo is set to 'not_paid' for open invoices and reconciled after payment migration. Odoo's account.move requires a journal_id; we select or create the Vendor Bills journal during setup. Invoices with mismatched amounts or unreconciled tax lines are flagged for AP manager review before posting.

Open customer invoices from Omni ERP migrate to Odoo account.move records with move_type = 'out_invoice'. Each line references the customer res.partner, revenue account from the COA mapping, and the AR account (res.partner.property_account_receivable_id). Multi-currency invoices carry the original currency and amount_currency on the move line; Odoo's foreign currency mechanism applies the captured exchange rate rather than fetching a live rate. Reconciliation records (account.move.line partial or full) are created for any pre-existing payments in Omni ERP.

Historical journal entries from Omni ERP migrate to Odoo account.move with move_type = 'entry'. Multi-currency line items carry the original amount_currency with the exchange rate captured at the Omni ERP transaction date. We store the captured rate in a custom field account_move_line__x_captured_rate__c on the move line and flag currency variance for review if the Odoo rate table differs. Entries are posted in date order; we validate that each entry date falls within an open fiscal year in Odoo's account.fiscal.year table before import. Entries referencing inactive COA accounts are held until the COA mapping is confirmed.

Omni ERP Fixed Asset records (acquisition cost, depreciation schedule, asset category) migrate to Odoo account.asset records if the Odoo Asset Management module (account_asset) is active. Depreciation method is preserved from Omni ERP; if Odoo does not natively replicate the source method, we store it as a custom field on the asset record. Acquisition date, gross value, and accumulated depreciation migrate to separate asset profile lines in Odoo. Assets not yet fully depreciated are migrated as active assets with remaining depreciation schedules.

Omni ERP Departments and Cost Centers are referenced in journal entries and user assignments. We map these to Odoo hr.department for org structure and to account.analytic.account for financial cost-center reporting. If the destination Odoo instance does not have the Accounting Analytic module active, we store department/cost center references in a custom res.partner property or product attribute and flag for the admin to activate the module. Circular department assignments are detected and flagged during the pre-flight audit.

Omni ERP User records (with role assignments and department affiliations) map to Odoo res.users. We map Omni ERP role names to Odoo access rights groups (res.groups). Users whose access scope exceeds Odoo Community's limits are flagged for the admin to provision as Portal or Active users in Odoo Enterprise. Inactive Omni ERP users are migrated as inactive res.users for audit completeness. Owner assignments on records migrate as res.users references resolved by email match.