Migrate from PrismERP to Odoo ERP

PrismERP Customer Master stores personal details, company data, contacts, addresses, and banking information in a centralized record. We migrate Customer records to Odoo res.partner with commercial partner record set for company-level data and contact records for individual points of contact. The customer_rank and supplier_rank fields on res.partner determine the record's role in Odoo's partner system. All addresses (delivery, invoice, other) migrate as separate res.partner records linked by type and parent_id.

Vendor Master mirrors the Customer Master structure in PrismERP. We migrate Vendor records to Odoo res.partner with supplier_rank set, preserving payment terms, fiscal position mappings, and banking information from the vendor record. Vendor-specific pricing and purchase agreements map to Odoo's Purchase module if the customer licenses it.

PrismERP's Chart of Accounts may include multi-level segment dimensions (company, region, department, product line) baked into the account code structure. We cannot auto-map these structures. We generate a segment mapping worksheet during discovery, have the customer define how each PrismERP dimension maps to Odoo's account code or to separate analytic account segments, and apply the mapping as a transform step. Closed-period historical accounts migrate as read-only audit records; the migration window is scoped explicitly with the customer to avoid inflating Odoo with decade-long transaction history.

PrismERP open Accounts Receivable vouchers represent live invoice balances with status, outstanding amounts, and due dates. We migrate open AR vouchers as Odoo account.move records of type 'out_invoice' with line items mapped to the correct receivable account. Voucher status (open, partial, closed) determines whether the Odoo invoice is in draft, posted, or reconciled state. Customer linkage resolves via the res.partner mapping established in the Customer Master step.

PrismERP open Accounts Payable vouchers migrate as Odoo account.move records of type 'in_invoice' (vendor bill) with line items mapped to the correct payable account. Outstanding amounts, due dates, and voucher status carry forward as Odoo invoice state and payment registry entries. Vendor linkage resolves via the Vendor Master mapping.

PrismERP Items include product definitions, pricing tiers, stock levels, and warehouse assignments. We migrate item master records as Odoo product.product with product.template for shared product attributes. Current stock quantities per warehouse map to Odoo's quant records. BOM associations (Bill of Materials for manufactured items) migrate as mrp.bom records referencing the product template. Variant attributes (size, color, etc.) map to Odoo's attribute and product variant system.

PrismERP Purchase Orders from the SDM module migrate to Odoo purchase.order with PO headers, line items, quantities, agreed prices, and vendor assignments. Approval status maps to Odoo's PO state (draft, sent, purchase order, done, cancel). We map PrismERP PO lines to Odoo purchase.order.line with product, quantity, and price resolved against the vendor and product mappings.

PrismERP Sales Orders migrate to Odoo sale.order with full line-item detail, pricing, customer linkage, and lifecycle status from order through fulfillment. Delivery and invoice document linkages migrate as separate records. Order status maps to Odoo's sale.order state (draft, sent, sales order, done, cancel). Customer address assignments for delivery and invoicing resolve via the customer partner mapping.

PrismERP Production Planning & Control orders reference BOMs and routing steps. The structure varies by manufacturing configuration (make-to-order versus repetitive). We map the production order as a header referencing the migrated mrp.bom record, with components resolved against the product mapping and work orders created from the routing steps mapped to Odoo mrp.workcenter resources. Production order status migrates to Odoo state (draft, confirmed, in progress, done). Customers on a make-to-order configuration should confirm BOM completeness before migration.

The Human Capital Management module is the highest-rated module in PrismERP user reviews. Employee records include personal data, employment details, department assignments, and compensation history. We migrate Employee records to Odoo hr.employee with department linkage resolving via the Department/Cost Center mapping. The HR module (hr) must be installed in Odoo before this import. Salary and compensation details migrate as hr.contract records if the Payroll module is licensed.

Organizational hierarchy is stored independently in PrismERP and linked to employees, accounts, and projects. We preserve the department structure and map cost center assignments to Odoo's hr.department hierarchy. In Odoo, departments also drive analytic account assignments for manufacturing and project costing, so the department mapping feeds both the HR module and the accounting/analytic mapping defined during Chart of Accounts scoping.

PrismERP's Project System module stores project definitions, WBS elements, time entries, and budget assignments. Project structures vary significantly by industry configuration. We migrate project headers as Odoo project.project and WBS elements as project.task records with parent_id hierarchy to preserve the work breakdown structure. Time entries migrate as project.task records with timesheet data in the Odoo timesheet app if licensed. Budget assignments require mapping to Odoo's analytic account or to the project-specific budget module.