Migrate from Open-Prod to Odoo ERP

Open-Prod customer and account records map to Odoo res.partner with partner_type distinction between customer, supplier, and company. Address fields (street, city, country, email, phone) migrate directly. Financial metadata (credit limit, payment terms) from Open-Prod maps to Odoo partner properties fields or to the accounting partner ledger. Company records in Open-Prod that represent vendors map to res.partner with supplier flag enabled. We set is_company = True for company-level records and link individual contacts as children.

Open-Prod item records with product details, pricing, and variant structures map to Odoo product.product variants under a product.template parent. We extract the SKU from Open-Prod item code, map pricing to product.list_price, and flag any variant attributes (size, color, material) for conversion to Odoo's attribute-value variant system. Products marked as storable in Open-Prod become product.product with type = product; services become type = service; consumables become type = consumable.

Open-Prod warehouse stock levels map to Odoo stock.quant records with location_id set to the corresponding warehouse's stock location. Open purchase orders and pending shipments require sequencing: we migrate all closed stock positions first, then import open purchase order lines as stock.move records with state = assigned or waiting. This prevents the stock discrepancy that occurs when a pending receipt inflates on-hand quantities before the PO is received. Lot and serial number tracking migrates to stock.production.lot records linked to the quant.

Open-Prod sales documents and invoices map to Odoo sale.order for orders and account.move (move_type = out_invoice or out_refund) for invoices. Order line items map to sale.order.line with product_id resolved via SKU match. We preserve order date, customer reference, and payment terms. Post-migration invoice numbering must be coordinated with the customer's Odoo partner because Odoo uses sequence-defined invoice prefixes that may conflict with Open-Prod's numbering scheme if the customer has statutory sequence requirements.

Open-Prod purchase orders map to Odoo purchase.order records with vendor_id resolved from the res.partner supplier mapping, order lines mapped to purchase.order.line, and product_id resolved via SKU. PO state (draft, sent, purchase order, done, cancelled) maps directly to Odoo's state field. If Open-Prod tracks landed costs or additional charges on PO lines, these map to Odoo's price_subtotal and taxes as applicable.

Open-Prod project records with tasks and milestones map to Odoo project.project and project.task. Task dependencies from Open-Prod are flagged during extraction and noted in the migration inventory as requiring manual rebuild in Odoo Project because Odoo uses predecessor-successor task dependency tracking that requires the task IDs to exist before the dependency links are created. Milestones from Open-Prod map to Odoo project milestones (if the project milestone app is active) or to a project.task with a milestone-type category field set during scoping.

Open-Prod after-sales service records map to Odoo helpdesk.ticket. Status and priority fields migrate to ticket stage_id and priority respectively. Customer contact links resolve via the res.partner mapping. If the customer activates the Odoo Helpdesk app, ticket teams and SLA policies are configured during the Odoo setup phase. For businesses without a Helpdesk license, service records map to project.task records under a dedicated service project as a fallback configuration.

Open-Prod accounting module entries map to Odoo account.move records of type entry (general journal). Account codes from Open-Prod's chart of accounts map to Odoo account.account records that must be pre-created during the Odoo configuration phase with codes matched to the customer's existing chart. We flag any Open-Prod journal entries that reference accounts not present in Odoo's configured chart as a reconciliation item for the customer's accountant.

Open-Prod custom fields are not confirmed-exportable through a documented public API. We flag custom field migration as out-of-scope pending direct access to the customer's Open-Prod configuration database. If Open-Prod exposes custom field definitions via its database schema or a configuration export, we can build a mapping table and generate Odoo custom fields via the ir.model.fields API before record migration begins. Without schema access, custom field data is not migrated.

Open-Prod attachment storage is not confirmed to have a public export mechanism. We flag attachment migration as out of scope. If Open-Prod stores attachments as files on the filesystem or in a database BLOB column accessible during discovery, we can extract them and link them to the migrated Odoo records via ir.attachment with res_model pointing to the target Odoo model and res_id pointing to the migrated record ID. This requires a case-by-case technical assessment during discovery.