Migrate from Perfecto ERP to Odoo ERP

Perfecto ERP's multi-level hierarchical account structure maps to Odoo account.account records with type (view, receivable, payable, other), code (derived from Perfecto account code), and name preserved. We extract the parent-child hierarchy and create parent accounts before child accounts, using Odoo's parent_id self-referential lookup. Perfecto ERP's account codes longer than Odoo's 64-character limit are truncated from the right with a warning issued during scoping. Account types map from Perfecto's classification (asset, liability, equity, income, expense) to Odoo's internal_type enum.

Perfecto ERP General Ledger transactions map to Odoo account.move (journal entry) and account.move.line records. Each Perfecto ERP transaction becomes a posted account.move with journal lines referencing Odoo account.account IDs resolved during migration. Journal entry numbering is preserved in move_ref or a custom field perfecto_journal_entry__c if the customer requires audit continuity. Date, debit amount, credit amount, and description migrate directly. Odoo requires a date and journal assignment for every move; we set the journal from a scoping-defined default (typically General).

Perfecto ERP customer records map to Odoo res.partner with customer_rank set to a positive value (indicating commercial contact) and the is_company flag enabled. The customer name becomes the partner name; address, contact, and payment terms map to street, city, email, and property_payment_term_id. Any Perfecto ERP End-User Customization Studio fields on the customer record are preserved as Odoo custom fields on res.partner. A separate contact record (individual) is created under the company partner if the Perfecto ERP record contains a primary contact name distinct from the company name.

Perfecto ERP vendor records map to Odoo res.partner with supplier_rank set to a positive value and the is_company flag enabled. Vendor-specific fields such as tax registration number, payment terms, and bank details map to Odoo's property_account_position_id (fiscal position), property_supplier_payment_term_id, and bank_ids respectively. Vendor contact persons are imported as follow-up contact records under the company partner record. The Perfecto ERP vendor payment terms field is resolved against Odoo's account.payment.term lookup table.

Perfecto ERP Items (finished goods, raw materials, services) map to Odoo product.product records. Perfecto ERP item type (good, material, service) determines Odoo's type field (product, consumable, service). Unit of measure from Perfecto ERP maps to Odoo's uom_id and uom_po_id by matching on the Perfecto UOM code against the Odoo uom.uom category. Item cost price from Perfecto ERP sets product.standard_price. The Perfecto ERP item code becomes the product's default_code (barcode). Custom fields added in Perfecto ERP's End-User Customization Studio are preserved as Odoo custom fields on product.product.

Perfecto ERP BOM structures require multi-pass sequencing because component items must land in Odoo before the parent assembly. We run a dependency analysis on the BOM data to identify top-level assemblies, then import subassemblies and components in order before importing the final BOM records. The mrp.bom records reference product.product IDs resolved at migration time. Odoo BOM line records carry the component product, quantity, and unit of measure. We validate the BOM structure post-import by querying mrp.bom.line for orphaned product references and flag any BOMs where a component did not resolve to a destination product ID.

Perfecto ERP employee profiles map to Odoo hr.employee records with name, work email, work phone, department (mapped to hr.department by name match), and job title preserved. Employee-specific fields such as badge or biometric ID, emergency contact, and bank details are imported as Odoo custom fields on hr.employee. We import the employee's assigned role from Perfecto ERP as a custom field role_assignment__c and advise the customer to rebuild Odoo access rights by configuring hr.employee categories and Odoo's access groups post-migration. Employees whose status is inactive or terminated in Perfecto ERP are imported with the active flag disabled.

Perfecto ERP role-based security assignments map to a written Odoo access rights inventory document that the customer's administrator uses to configure Odoo security groups and record rules post-migration. Odoo's security model differs from Perfecto ERP's module-and-field-level permissions; Odoo uses model-level access control lists (ACLs) on ir.model.access and record rules on ir.rule. We extract the Perfecto ERP role-permission matrix during discovery and produce a recommended Odoo group structure (for example, one Odoo group per Perfecto ERP role, with ACLs assigned per module). Active user count and role distribution are included in the inventory document.

Perfecto ERP purchase orders map to Odoo purchase.order and purchase.order.line records. Order date, vendor reference, and currency code migrate directly. Line items reference Odoo product.product IDs resolved during the Items migration phase, with quantity and price copied from Perfecto ERP. Odoo's picking (receipt) records are not auto-generated during migration; we advise the customer to run Odoo's request procurement action post-import if incoming shipment tracking is required. Purchase order totals are validated against Odoo's computed amount_total after import.

Perfecto ERP sales orders map to Odoo sale.order and sale.order.line records. Customer partner is resolved from the customer mapping, product lines reference Odoo product.product IDs, and order date and currency code transfer directly. Delivery address from Perfecto ERP's order header maps to Odoo's partner_shipping_id. Order status from Perfecto ERP (confirmed, shipped, invoiced) is preserved as a custom field source_status__c since Odoo's sale.order workflow states differ. Invoiced orders in Perfecto ERP may also generate Odoo account.move records if the customer requires a full transactional history in Odoo.

Perfecto ERP file attachments linked to records are exported to a neutral file store (local or cloud bucket) during the migration extract phase. The file path and original record association are preserved in a mapping table. Post-import, we relink each attachment to the corresponding Odoo record by matching the original record's external ID to the migrated Odoo record ID. Binary files are uploaded as Odoo ir.attachment records with res_model set to the target Odoo model (res.partner, product.product, etc.) and res_id set to the destination record ID. Files without a resolvable parent record are delivered as a standalone archive.

Perfecto ERP approval workflows define custom approval chains tied to transaction types (purchase orders, expense reports, payment runs). These are extracted as a written configuration inventory during the discovery phase and are not migrated as executable code. Odoo does not have a native generic approval engine in its Community edition; Odoo Enterprise and Odoo Studio provide approval management. We recommend the customer engage an Odoo implementation partner to rebuild approval chains in Odoo Studio or via custom development, and we deliver the inventory document (workflow name, trigger condition, approver chain, threshold amounts) as the handoff artifact.