Migrate from Proteus E12ERP to Odoo ERP

Proteus E12ERP Customer records map to Odoo Contact with the company checkbox enabled, preserving name, phone, email, address fields, and any lifecycle or credit-term properties. If the source Customer has a Revenue Center association, we store that in a custom Char field revenue_center_ref__c on the Contact for later cross-reference. The Contact is created before any Sales Order import so the partner_id lookup resolves at import time.

Proteus Vendor records map to Odoo Contact with the Is a Vendor checkbox selected, which activates the Purchase module visibility for that contact. Vendor name, contact details, and payment terms migrate as Contact fields. Vendor code from Proteus becomes the ref field on the Odoo Contact. If the source Vendor has a Revenue Center association, it is stored in revenue_center_ref__c on the Contact for mapping during Purchase Order import.

Proteus Inventory Items with SKU, description, unit cost, and quantity-on-hand map to Odoo Product records of type Stockable (for tracked inventory) or Consumable. Quantity on hand from the source becomes an initial Stock Quant on the destination Warehouse. We flag any Proteus Item that has a non-numeric or duplicate SKU for manual review before import, as Odoo requires a unique default_code per product.

Proteus Revenue Centers represent branches or cost centres — a non-standard ERP concept. Each Revenue Center maps to an Odoo Warehouse record, with the Warehouse's Locations (Internal Locations) representing sub-locations within the branch. If a Revenue Center has sub-branches in the Proteus data, we create corresponding Warehouse Location records. The revenue_center_ref__c on Contacts and Products holds the source Revenue Center key for cross-reference. Odoo Enterprise adds multi-warehouse stock reporting; Community edition supports multi-location with the stock module.

Proteus Sales Orders map to Odoo Sale Order with customer (partner_id) resolved from the Customer mapping, order lines mapped to Order Product lines referencing the Product records imported earlier, and order status mapped from Proteus order state to Odoo state (draft, sale, done). If the Proteus source exposes historical closed orders, we import them as locked Sale Orders in Odoo to preserve the record without allowing edits.

Proteus Purchase Orders map to Odoo Purchase Order with vendor (partner_id) resolved from the Vendor mapping, order lines referencing Products, and status mapped to Odoo Purchase Order state (draft, purchase, done, cancel). Open purchase orders (status = open or partially received) migrate as draft Purchase Orders so the Odoo receiving workflow can execute against them post-migration. Historical closed POs migrate as done/cancelled records as appropriate.

The Proteus Chart of Accounts export provides account codes, names, and types. We map these to Odoo Account records via the standard Odoo COA CSV import format. Account type mapping preserves asset, liability, equity, income, and expense categories. Currency denomination from Proteus maps to the account's currency field. If Proteus uses Indian rupee (INR), the account is created with currency set to INR and Odoo's accounting currency configured accordingly.

Open Accounts Payable records (unpaid vendor invoices) are not explicitly documented as an exportable object in Proteus E12ERP. We cannot guarantee completeness of open-AP data from the delimited export. We flag this gap in the pre-migration audit and advise the customer to export open vendor bills manually from Proteus and import them as Odoo Vendor Bills (account.move with type = out_invoice and partner_id = vendor) post-migration. This step is outside our standard migration scope and is documented as a manual action item.

Open Accounts Receivable records (unpaid customer invoices) are not documented as exportable in Proteus E12ERP. We flag this as a gap in the discovery audit and advise exporting outstanding customer invoices manually from the Proteus AR register. The customer can import these as Odoo Customer Invoices (account.move with type = out_invoice) post-migration. This is documented as a manual action item in the migration handoff package.

If the Proteus export includes product-specific pricing or customer-specific price lists, these map to Odoo Pricelist and Pricelist Item records. We map the Proteus price list entries to Odoo product.pricelist with the applicable rule type (fixed price, percentage, formula). Pricelist assignment to Customers migrates from the Proteus customer-price-list association.

Proteus unit-of-measure definitions (each, kg, meter, etc.) map to Odoo UoM records via the standard Odoo UoM import. UoM category (Length, Weight, Volume) is preserved to satisfy Odoo's UoM category consistency requirement on products. Migrations with non-standard or proprietary UoM definitions in Proteus are flagged for manual mapping during the data audit phase.