Migrate from Prowess ERP to Odoo ERP

Prowess ERP Chart of Accounts records migrate to Odoo account.account using account.code as the dedupe key and account.name as the display name. Account types (Asset, Liability, Equity, Revenue, Expense) map from Prowess account classifications. We preserve the full account code hierarchy so that Odoo's account.parent_id self-referential structure reproduces the original COA depth. This is the first import in production because every financial transaction references an account.

Prowess ERP Cost Centre hierarchies are implementation-specific with no canonical reference schema. We inventory the full Cost Centre tree during scoping, then map each Cost Centre to an Odoo analytic.account with the same code and name. Analytic account tags or dimensions in Odoo represent Cost Centre groupings if the customer's Prowess deployment used multi-level hierarchies. Any Cost Centre-specific custom fields in Prowess become analytic.account custom fields in Odoo.

Prowess ERP customer records migrate to Odoo res.partner with partner_type set to contact. GST registration number from Prowess custom fields maps to l10n_in_gstin on the res.partner record. Payment terms, credit limits, and billing addresses transfer as partner property fields. Email, phone, and address fields migrate directly. Any custom customer properties from the Prowess implementation are mapped as res.partner custom fields or property records before import.

Vendor master records from Prowess ERP migrate to res.partner with supplier flag set to True. GST/TIN registration, vendor-specific credit limits, and payment terms transfer as custom fields or partner properties. We flag any vendor-specific tax registration details that require manual confirmation after import because Prowess and Odoo may represent tax registration fields differently depending on the implementation.

Prowess ERP item masters migrate to Odoo product.product and product.template. Standard fields including item code, name, description, unit of measure, and cost price map 1:1. Manufacturing-specific attributes (BOMs, work centres, uom conversions) are flagged for separate BOM import because Odoo requires the product template to exist before the mrp.bom record can reference it. We use product_uom_id from Odoo's uom.uom model for unit-of-measure conversion.

Prowess ERP BOM structures are implementation-specific and do not follow a canonical schema. We inventory BOM data during the schema discovery phase, map each BOM to mrp.bom in Odoo with product_tmpl_id resolved to the imported product.template, and create mrp.bom.line records for each component with qty basis and routing links. If Prowess BOMs include multi-level routing data, we flatten them into separate mrp.workcenter records and link them via mrp.routing_workcenter_line on the BOM.

Outstanding payables and receivables in Prowess ERP require open-balance extraction with invoice number, partner reference, amount, due date, and allocation status. These migrate to Odoo account.move records with move_type=out_invoice (AR) or in_invoice (AP). Open balances are validated against the Prowess trial balance before and after import. Reconciliations are re-established post-migration by the customer's accountant using Odoo's reconciliation engine.

Prowess ERP open purchase orders migrate to Odoo purchase.order with status flags preserved. PO headers and line items transfer with product, quantity, price, and tax mapping. Where Prowess ERP uses custom workflow states not present in Odoo's purchase.order model, we map to the nearest equivalent state (draft, sent, purchase order, done, cancel) and flag records requiring state correction in Odoo before they progress through the approval workflow.

Sales order headers and lines migrate to Odoo sale.order with pricing, discounts, and fulfilment status preserved. Custom fields added by the Prowess ERP implementing partner are mapped as sale.order custom fields or order line extra fields. Back-ordered lines are flagged separately in a reconciliation report for the customer's sales operations team to confirm and action in Odoo post-migration.

Work order sequencing, BOM links, and routing data from Prowess ERP migrate to Odoo mrp.production (production order) and mrp.workorder (work order steps). BOM references are resolved to the imported mrp.bom records, and work centre assignments resolve to mrp.workcenter records created during the BOM import phase. Production order state is mapped from Prowess workflow status. Component reservations are recalculated in Odoo post-import because Odoo may have different stock-reservation logic than Prowess.