Migrate from Odoo ERP to Epicor Prophet 21

Odoo Partner records split into Epicor Customer (for sales-facing contacts) and Supplier (for procurement-facing contacts) based on Odoo's partner_type field. Partner categories map to Epicor Customer or Supplier type codes. Email, phone, and address fields migrate directly; the country/state hierarchy maps to Epicor's territory and state/province fields. Multi-company Odoo partners (where one partner belongs to multiple Odoo companies) require Epicor Company records to be provisioned first so that the customer can assign Customer records to the correct legal entity.

Odoo Product records map to Epicor Part master. The Odoo product type (stockable, consumable, service) maps to the Epicor Part Type field (Stocked, Non-Stocked, Service). The Odoo default_code or barcode becomes the Epicor Part Number; list_price and standard_cost map to the Epicor standard cost and sales price fields. Product variants in Odoo (via attribute combinations) map to Epicor Part Revisions with configuration codes, though multi-variant products may require manual disambiguation in Epicor's Revisions module.

Odoo BoM records with type kit, manufactured, or phantom map to Epicor BoM structures with the same bom type designation. Odoo BoM lines (product + quantity + unit of measure) map to Epicor BoM materials with the same component Part numbers and quantity-per relationships. Multi-level BoM hierarchies (nested subassemblies) resolve as Epicor multi-level BoMs with the parent-part revision number referencing each sub-assembly's revision. Phantom BoMs in Odoo flatten at the Epicor MRP level as configured.

Odoo Manufacturing Order records map to Epicor Job records. The Odoo MoType (manufacture, subcontract, kit) maps to Epicor Job Type. Odoo MO states (draft, confirmed, in progress, done) map to Epicor Job status fields. The linked BoM in Odoo references the corresponding Epicor Part and BoM revision, allowing Epicor Job to pull materials from the mapped BoM. Workorder sequences in Odoo map to Epicor Job Operations with sequence, work center, and cycle time information. Odoo MO dates (scheduled start, deadline) migrate as Epicor Job start and due dates.

Odoo stock.quant records track on-hand quantities per location and lot/serial. We map Odoo stock locations to Epicor Warehouses and Bin locations, resolving the location hierarchy (warehouse > location > shelf) into Epicor's Site > Warehouse > Bin structure. Current on-hand quantities from Odoo stock.quant migrate to Epicor Part Tracker records per Part and Bin. Lot and serial number traceability migrates to Epicor Part Lot records if Odoo uses lot management; manual verification of lot assignments is required post-import because lot naming conventions may differ between platforms.

Odoo sale.order records map to Epicor Order. Order lines (product + quantity + price) map to Epicor OrderDtl with the mapped Part numbers. The Odoo order state (draft, sale, done, cancelled) maps to Epicor OrderHed status and OrderDtl status. The linked Odoo Partner (customer) resolves to the Epicor Customer record established in the master data phase. Fiscal positions from Odoo that affect tax computation map to Epicor Tax connectivity rules, but country-specific tax group rules require explicit configuration in Epicor Tax Maintenance post-import.

Odoo account.move records with move_type out_invoice, out_refund, in_invoice, in_refund map to Epicor AR Invoice and AP Invoice records respectively. The invoice number, date, due date, and amount migrate to Epicor InvoiceHed and InvoiceDtl. Posted invoices in Odoo are non-editable and migrate as locked records in Epicor; any corrections require credit memos in Epicor per standard accounting practice. Open (unpaid) invoices migrate with their payment terms and outstanding amounts so that the AR/AP aging reports remain accurate.

Odoo account.account records map to Epicor GL Account with account code, name, and account type. Country-specific tax groups and fiscal position rules from Odoo require explicit configuration in Epicor's Tax Maintenance and Fiscal Year Setup rather than direct data migration, because fiscal rules are jurisdiction-specific and need destination-system validation. We provide the Odoo chart of accounts as a reference file for the Epicor partner's configuration work.

Odoo project.project records map to Epicor Project. The project stage pipeline and task hierarchy migrate as Epicor WBS (Work Breakdown Structure) elements under the Project. Project manager assignment links to the Epicor User record resolved by email match. Odoo project-level billing rates migrate as Epicor Project Billing rates if the customer uses project accounting in Epicor.

Odoo project.task records map to Epicor Project Tasks under the corresponding WBS element. The task stage, assignee, deadline, and parent_id (sub-task hierarchy) migrate to Epicor with task sequence preserved. Custom stage names from Odoo Studio map to Epicor Project Task Status values, which the customer's project manager configures post-import.

Odoo hr.employee records map to Epicor Employee. We resolve Odoo employee email to the Epicor User record for User-linked employees. Odoo employee categories, emergency contacts, and HR-specific fields that are Odoo-specific do not have direct Epicor equivalents and are preserved in a custom reference file for the HR administrator to re-enter in Epicor HR module. Employee status (active, inactive) migrates to Epicor Employee status.

Odoo custom fields defined via ir.model.fields or Odoo Studio require a different approach in Epicor. We document each custom field (name, ttype, selection options, stored or computed) as a specification for Epicor's UD (User-Defined) field or Epicor Customization approach. Epicor does not use the same custom field extension model as Odoo Studio; fields require Epicor partner involvement to implement as UD columns or customizations rather than being migrated as self-service extensions.

Odoo account.tax records with scope (sale/purchase), tax_type (percent, fixed, group), and country-specific fiscal positions map to Epicor Tax Maintenance. Tax names and rates migrate as a reference; the Epicor tax connectivity rules (linking tax codes to customers, suppliers, and products) require manual configuration by the customer's Epicor partner or finance team because fiscal rules are jurisdiction-specific and cannot be blindly transferred between platforms without compliance review.

Odoo ir.attachment records store files as binary in PostgreSQL or as external URLs. We migrate file attachments that are accessible via public URL by registering them as Epicor Document Management entries linked to the relevant Part, Job, Order, or Customer record. Large binary attachments stored directly in Odoo's database require extraction and hosting on a file server or cloud storage, with the URL registered in Epicor's Document table. We flag attachments exceeding 25 MB for manual re-upload post-migration.