Migrate from ProcessWare ERP to Odoo ERP

ProcessWare Customer records (including full contact details, account hierarchies, and sales history from the CRM component) map to Odoo res.partner records with partner_type set to 'contact' or 'company' based on whether the record represents an individual or organization. The ProcessWare CRM lifecycle stage migrates to a custom partner_tag or custom field in Odoo because Odoo's standard partner model does not include a lifecycle stage property.

ProcessWare Formulation Recipes (compound hierarchies, ingredient ratios, version history, and IFRA classification) require a multi-part mapping: the recipe header migrates to a custom formulation table, and each ingredient line migrates to an mrp.bom.line with the Odoo product variant resolved by SKU or name match. Version history is preserved as sequential bom records with a custom version field, or consolidated into a single active BOM with version notes in a custom field. IFRA compliance classifications migrate to a custom field (x_ifra_classification) and the associated regulatory classification migrates to ir.attachment linked to the BOM.

ProcessWare multi-level BOMs (where sub-assemblies may themselves contain other formulations as ingredients) map to Odoo mrp.bom records with type='kit' or type='manufacture' depending on routing requirements. We resolve the nested BOM structure by creating parent BOMs after all child BOMs exist, using the ProcessWare recipe-to-BOM mapping as the lookup key. Recursive BOM resolution is performed during the transform phase to flatten or preserve hierarchy based on the customer's Odoo configuration preference.

ProcessWare Production Orders (tied to specific formulations, planned quantities, scheduling constraints, and facility routing) map to Odoo mrp.production records. The mrp.bom reference is resolved from the formulation mapping, and the bill of material lines become components on the production order. Scheduling constraints from ProcessWare migrate to mrp.production date fields and workstation assignments if Odoo's workshop floor control (mrp.workcenter) is configured.

ProcessWare Quality Records (test results, QC documentation, passing criteria, inspector assignments linked to production batches and raw material lots) map to Odoo quality.check records attached to mrp.production or stock.production.lot. Test result values and passing criteria migrate as quality.point thresholds configured in Odoo's Quality app. QC documents migrate as ir.attachment records linked to the production lot or the quality check.

ProcessWare Supply Chain Transactions (purchase orders, receipts, outbound shipments with traceability to production batches) map to Odoo's stock.picking, purchase.order, and stock.move records. Inbound receipts become stock.picking with type='incoming', outbound shipments become stock.picking with type='outgoing', and purchase orders become purchase.order linked to the corresponding picking. The production batch traceability chain migrates to stock.move lines with lot_number and location_dest_id resolved from ProcessWare's batch linkage data.

ProcessWare Vendor Records (supplier profiles, certification status, material qualifications, performance history) map to Odoo res.partner with partner_type='supplier' and fields from the vendor's qualification and certification records migrated to custom partner fields or the Odoo Accounting app's vendor data model. Certification expiry dates migrate to custom date fields for compliance tracking.

ProcessWare Regulatory Compliance Documents (IFRA compliance data, SDS documents, allergen declarations tied to formulations) require a custom compliance model in Odoo because Odoo does not have a native IFRA compliance object. We map SDS documents as ir.attachment linked to the product (product.product or product.template) and create a custom x_compliance_record model for IFRA classifications, allergen declarations, and regulatory expiry dates. The customer must configure this custom model in Odoo during the setup phase before compliance document migration begins.

ProcessWare custom fields (confirmed accessible via Keka HRMS API read/write operations) map to Odoo custom fields created via Settings > Technical > Database Structure > Fields. We extract the field label, data type, and options from ProcessWare's custom field registry during discovery and pre-create the corresponding Odoo fields before any data migration phase. Custom field semantics (e.g., whether a field is formula-driven or user-entered) cannot always be inferred and are documented for the customer's admin to validate post-migration.

ProcessWare attachments (supporting documents linked to formulations, quality records, and transactions) migrate as ir.attachment records in Odoo linked via res_model and res_id to the target object (mrp.bom, mrp.production, stock.picking, or res.partner). We extract file content, filename, and mime type from ProcessWare's file storage and reattach to the corresponding Odoo record. Legacy file formats are documented and converted to Odoo-supported formats (PDF, PNG, JPEG) where necessary; files with unsupported binary formats are archived and referenced in the migration inventory.