Skip to content
Get a quote

Odoo ERP to Epicor Prophet 21 migration

We migrate Partners, Products, Sales Orders, Manufacturing Orders, Bills of Materials, and Inventory from Odoo ERP into Epicor Kinetic with the dependency chain resolved upfront, BoM structures preserved through Epicor Data Management Tool, and every Odoo External ID mapped to an Epicor Key field before cutover.

Short answer

FlitStack AI migrates customer and suppliers, parts, bill of materials, jobs and part tracker / bin quantities from Odoo ERP to Epicor Prophet 21, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 6-10 weeks.

By

Source Odoo ERP
DestinationEpicor Prophet 21
Customer and SupplierPartBill of MaterialsJobPart Tracker / Bin Quantity
Mapped field by field · sample run · one-click rollback

What moves from Odoo ERP to Epicor Prophet 21?

Moving from Odoo ERP to Epicor ERP is a cross-platform structural migration that maps one of the broadest open-source ERP object sets onto one of the deepest mid-market manufacturing ERPs.

Read the full summary

Odoo's PostgreSQL-backed ORM exposes Partners, Products, BoMs, Manufacturing Orders, Sales Orders, and Inventory via XML-RPC or JSON-RPC using External IDs as the import reference. Epicor Kinetic receives this data through its Data Management Tool (DMT) with over 60 import templates and built-in business logic validation. The migration requires a five-phase dependency sequence: master data (Partners, Products, chart of accounts) first, then inventory locations, then BoM structures, then manufacturing orders, then transactional history. Workflows, Odoo Studio customizations, and Odoo.sh CI/CD pipelines do not migrate; we deliver a written inventory of Odoo automations and custom modules for the customer's Epicor partner to rebuild post-cutover.

1:N split

Partner (Contacts/Companies) → Customer and Supplier

Odoo Partner records split into Epicor Customer (for sales-facing contacts) and Supplier (for procurement-facing contacts) based on Odoo's partner_type field.

How it maps

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.

1:1

Product (Items) → Part

Odoo Product records map to Epicor Part master.

How it maps

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.

1:1

Bill of Materials (BoM) → Bill of Materials

Odoo BoM records with type kit, manufactured, or phantom map to Epicor BoM structures with the same bom type designation.

How it maps

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.

1:1

Manufacturing Order (MO) → Job

Odoo Manufacturing Order records map to Epicor Job records.

How it maps

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.

configuration

Stock Move / Inventory Quant → Part Tracker / Bin Quantity

Odoo stock.quant records track on-hand quantities per location and lot/serial.

How it maps

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.

1:1

Sales Order → Order

Odoo sale.order records map to Epicor Order.

How it maps

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.

What moves14 objects
Odoo ERPEpicor Prophet 21
  • PartnerCustomer and Suppliersplit
  • ProductPart1:1
  • Bill of MaterialsBill of Materials1:1
  • Manufacturing OrderJob1:1
  • Stock MovePart Trackertransformed
  • Sales OrderOrder1:1

+ 8 more in the mapping below

How Odoo ERP and Epicor Prophet 21 differ

The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.

DimensionOdoo ERPEpicor Prophet 21
Target company sizeSMB: 1–20 users on Standard, Community edition unlimitedMid-market: 51–5,000+ employees; minimum 10 users required
Manufacturing depthModular MRP with BoM, MO, and workorders in separate appsNative job management, MES, and real-time production monitoring in one platform
Pricing modelPer-user $24.90–$37.40/month on cloud; Community freePer-user $125/month subscription; $50,000+ implementation minimum
Data architecturePostgreSQL with ORM; XML-RPC or JSON-RPC API; External IDs for importsSQL-based with .NET services layer; DMT with CSV/Excel templates for import
Customization approachCode-level (Python modules) plus Odoo Studio for low-codeNo/low-code configuration surfaces; platform services for deeper changes
DeploymentCloud (Odoo Online), self-hosted (PostgreSQL), or Odoo.shCloud or on-premises; single platform across all deployment types
Module dependency modelIndependent apps sharing one database; dependency ordering mattersIntegrated suite; BoM, MO, and inventory share the same data model

What to watch for in a Odoo ERP to Epicor Prophet 21 migration

The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.

high

BoM recursion and multi-level structure mapping requires iterative resolution

Odoo multi-level Bills of Materials with nested subassemblies (BoM referencing another BoM as a component) create recursive structures that Epicor DMT imports handle as flat BoM records.

How we handle it

We resolve the nesting hierarchy during the extract phase by expanding the BoM tree in Odoo, ordering the components by dependency level, and importing parent-level Parts before their child subassemblies. Without this ordering step, Epicor rejects subassembly references that do not yet exist as Parts, causing partial BoM imports that require manual correction in Epicor BoM Maintenance.

high

Lot and serial number traceability is not guaranteed across platforms

Odoo's lot/serial number system uses its own naming convention and tracks lot assignment at the stock.quant level.

How we handle it

Epicor tracks lots at the Part Lot table with expiration dates, engineering revisions, and traceability links to receipts and jobs. We migrate lot numbers and their quantities from Odoo stock.quant to Epicor Part Lot records, but Epicor requires a separate receipt transaction to formally receive the lot into the Part Lot registry before it appears in MRP allocations. This means that on-hand lot quantities appear correct in Epicor Part Tracker after migration, but the lot's formal registry record requires a manual receipt or DMT-supplied lot receipt to activate full traceability in Epicor's quality and job modules.

high

Odoo Studio customizations do not map to Epicor configuration

Odoo Studio custom fields, Studio-modified views, and custom report layouts built in Odoo Enterprise are stored as Odoo-specific XML and Python tuples that have no equivalent in Epicor's data model or UI configuration layer.

How we handle it

We document every Odoo Studio customization as a written specification for the customer's Epicor partner, noting the affected model, the custom field definition, and the recommended Epicor UD column or customization approach. The customer should plan a separate Epicor customization phase post-migration rather than expecting these to arrive as migrated artifacts.

medium

Epicor DMT requires staging template development per module

Epicor DMT ships with over 60 import templates, but Odoo's ORM field names do not match Epicor's DMT column headers.

How we handle it

We develop CSV import templates aligned to Odoo's XML-RPC field outputs (search_read return values) mapped to Epicor DMT required fields. Each template must pass Epicor's business rule validation (required fields, data type checks, foreign key lookups) before production use. Template development takes two to four weeks per major module (Part, BoM, Job, Order, Customer) and is performed in a non-production Epicor environment before production migration begins.

medium

Fiscal position and tax rule migration requires destination jurisdiction review

Odoo fiscal positions (which apply different tax or account rules based on customer country, VAT number, or product category) are Odoo-specific automation that has no direct Epicor equivalent.

How we handle it

Epicor uses Tax Maintenance and Tax Connectivity rules for tax assignment. We export Odoo fiscal position definitions as a reference document, but their Epicor equivalents require a finance team or Epicor consultant to configure using Epicor's tax engine, which operates differently from Odoo's rule-based fiscal position model. Companies with multi-jurisdiction tax complexity should plan two to four weeks for post-migration tax configuration review.

How the migration runs

  1. Discovery and source audit

    We audit the source Odoo instance across edition (Community or Enterprise), PostgreSQL version, active modules (CRM, Sales, Inventory, Manufacturing, Accounting, Project), custom fields via ir.model.fields, Odoo Studio modifications, and third-party module dependencies.

    What this step covers

    We identify the Odoo version and flag any ORM changes that affect field names between releases. We extract record counts per object and assess data quality (duplicate Partners, inconsistent BoM structures, incomplete lot traceability). The discovery output is a written migration scope with object-level record counts, a data quality issue register, and an Epicor edition recommendation based on the customer's operational complexity.

  2. Epicor schema provisioning and DMT template development

    We provision the Epicor destination environment in a non-production Epicor tenant or sandbox.

    What this step covers

    We create the Part, Customer, Supplier, BoM, Job, Order, and Project records in Epicor's native configuration tools, mapping Odoo module scope to Epicor functional areas. Parallel to this, we develop DMT CSV templates that translate Odoo's search_read field outputs to Epicor DMT column headers, including all required lookup fields (Part Number, Customer ID, Supplier ID, Job Number, etc.). Each template is validated against Epicor's business rule engine before being approved for production use. Template development typically takes two to four weeks per major module.

  3. Master data migration in dependency order

    We execute the master data migration in strict dependency sequence: (1) Chart of Accounts and fiscal configuration reference (exported for manual Epicor configuration, not API-imported), (2) Customer and Supplier records resolved from Odoo Partners, (3) Part master records resolved from Odoo Products, (4) Part Lot records for lot-controlled parts (for traceability verification), (5) BoM structures with multi-level resolution (parent parts before subassembly children), (6) Inventory locations mapped to Epicor Warehouses and Bins.

    What this step covers

    Each phase emits a row-count reconciliation report and a field-level spot-check of 25-50 records against the Odoo source before the next phase begins.

  4. Transactional data migration and MO-to-Job conversion

    Open Manufacturing Orders from Odoo convert to Epicor Job records using the BoM and routing data established in the master data phase.

    What this step covers

    We map Odoo MO states to Epicor Job status, preserving scheduled start dates, due dates, and workorder operation sequences. Open Sales Orders and Invoices migrate with their current status and outstanding amounts. Inventory on-hand quantities from Odoo stock.quant migrate to Epicor Part Tracker per Bin. We flag any Odoo record with a broken foreign key (e.g., an Order referencing a deleted Partner) in a reconciliation queue for the customer to resolve before re-import.

  5. Sandbox validation and reconciliation

    We run a full migration into the Epicor non-production environment using production-equivalent data volume.

    What this step covers

    The customer's operations lead reconciles record counts, spot-checks BoM explosion accuracy against Odoo source records, verifies lot traceability, and validates that open MOs appear as Epicor Jobs with correct material allocations. The Epicor partner configures tax connectivity rules during this phase with the Odoo fiscal position reference document. Any mapping corrections are applied to the DMT templates before production migration begins.

  6. Production cutover, delta sync, and Odoo Studio handoff

    We freeze Odoo writes during cutover, run a final delta migration of any records modified during the migration window (with a checkpoint timestamp applied at freeze), then mark Epicor as the system of record.

    What this step covers

    We deliver the Odoo Studio customization inventory document to the customer and their Epicor partner for post-migration rebuild planning. We support a two-week hypercare window for reconciliation issues. We do not rebuild Odoo automations (ir.cron jobs, server actions, automated actions) as Epicor workflows inside the migration scope; these are documented for the Epicor partner's separate automation engagement.

Odoo ERP Epicor Prophet 21
  1. Connect
  2. Map
  3. Sample
  4. Migrate
  5. Verify
  • Contacts48,210 / 48,210 Done
  • Companies9,134 / 9,134 Done
  • Deals6,377 / 11,920 In progress
Example run
Restore points · Epicor Prophet 21Rollback ready
  1. Before sample runRestore point 01Restore
  2. Before full migrationRestore point 02Restore
  3. After verificationRestore point 03Current
Example

How long it takes, and what drives the quote

6-10 weeksTypical, smaller accounts
12-20 weeksLarge or heavily customised accounts

A quote scales with master data volume, BoM complexity, open manufacturing order count, and inventory location count. Every quote is scoped with you; there is no self-serve pricing.

Get a quote for Odoo ERP to Epicor Prophet 21 →

Why teams move from Odoo ERP to Epicor Prophet 21

  • Odoo caps out at the SMB segment while Epicor begins at the mid-market threshold. Odoo's published user range tops at 20 on Standard, and reviewers on G2 and Capterra consistently note that performance degrades when many modules and heavy customizations run simultaneously at larger scales. Epicor Kinetic targets companies with 51–5,000+ employees and a $10M+ revenue floor, with architecture designed for the multi-site, multi-company complexity that emerges as teams grow past Odoo's ceiling.
  • Epicor's manufacturing depth exceeds Odoo's modular app approach for discrete and mixed-mode production. PeerSpot's comparison attributes Epicor superior job management, analytics, and production planning while noting that Odoo's strength lies in open-source flexibility rather than shop-floor depth. Companies running MRP-heavy operations with workorder routing, MES, and quality management move to Epicor because these are native platform features rather than assembled-from-apps workflows.
  • Odoo's per-module licensing model creates unpredictable cost escalation as teams add apps. Reviewers on G2 and Capterra cite per-module pricing nuances and the discovery of additional app costs as drivers of unexpected invoices. Epicor Kinetic bundles its functional depth under a single per-user subscription, which is more predictable for companies with broad operational scope that would require many Odoo apps at different price points.
  • Odoo version upgrades break custom modules and force ongoing developer contracts. Each Odoo major release revises ORM models, deprecates API methods, and restructures standard modules; custom modules written for one version are not guaranteed to load in the next without code adaptation. Epicor Kinetic maintains API stability across its supported versions and provides configuration surfaces that do not require Python module development, reducing the long-term developer dependency that Odoo customizations create.
  • Companies outgrowing Odoo's community support model move to Epicor's partner ecosystem with more consistent SLA commitments. Odoo's Enterprise support tiers have inconsistent response times per reviewer feedback, while Epicor's certified partner network provides structured implementation, training, and support tiers aligned to mid-market operational SLAs. The transition reflects a shift from open-source community reliance to enterprise-grade partner accountability.

Questions, answered

Odoo ERP to Epicor Prophet 21 migration questions

How long does an Odoo ERP to Epicor ERP migration take?

Most migrations land between six and ten weeks for accounts with under 10,000 Partners, 5,000 Products, and 500 open Manufacturing Orders with straightforward single-level BoMs. Migrations with multi-level BoM hierarchies, lot/serial traceability requirements, multi-warehouse inventory, or large transactional histories (over 100,000 stock moves) extend to twelve to twenty weeks because of BoM recursion resolution, DMT template development per module, and tax configuration work. Epicor Kinetic standalone implementation (without migration) typically takes five to ten months per Epicor's own implementation guide, so the migration project adds to that baseline.

Do Odoo Workflows, automations, and Odoo Studio customizations migrate to Epicor?

No. Odoo automations (server actions, automated actions, ir.cron scheduled jobs) and Odoo Studio customizations are Odoo-specific platform artifacts that have no direct Epicor equivalent. Epicor's automation model uses configuration-based rules rather than Python module development. We deliver a written inventory of every active Odoo automation and Odoo Studio modification with its trigger, conditions, actions, and a recommended Epicor configuration approach. The customer's Epicor partner rebuilds these as part of a post-migration optimization engagement. Odoo.sh CI/CD pipelines and custom Python modules similarly do not migrate.

Can we migrate Odoo BoMs with nested subassemblies to Epicor correctly?

Yes, but it requires iterative resolution. We expand the Odoo BoM tree to identify the dependency levels, import parent-level Parts before their child subassemblies, and map the nested BoM lines to Epicor's multi-level BoM structure. A single-level BoM with ten components imports in one pass; a three-level BoM with subassemblies requires the subassembly Parts and their BoMs to import first, then the parent BoM references those subassemblies. We handle this ordering during the extract phase and validate in Epicor BoM Explorer post-import to confirm the explosion matches the Odoo source.

What happens to lot and serial number traceability after migration?

Odoo lot numbers and their assigned quantities migrate to Epicor Part Lot records. However, Epicor requires a formal receipt transaction to activate the lot in its traceability system before it can be allocated to a Job or appear in quality inspections. After migration, we run a post-import receipt procedure that formally receives the migrated lot quantities into Epicor's Part Lot registry so that MRP, job material allocation, and lot traceability work correctly. Companies with strict FDA, aerospace, or automotive traceability requirements should plan a manual lot audit window of two to five days post-migration to verify lot assignment completeness.

Do we lose Odoo financial history and open invoices during migration?

No. We migrate Odoo posted and draft invoices as Epicor AR/AP Invoice records with amounts, dates, payment terms, and line items intact. Open (unpaid) invoices preserve their outstanding balance so that the AR/AP aging reports remain accurate after cutover. We do not migrate the full Odoo accounting ledger (journal entries) because Epicor's general ledger uses a different account structure and fiscal year configuration that requires the customer's finance team to validate against the Odoo chart of accounts. Chart of accounts codes and names migrate as a reference file; fiscal position rules migrate as a specification document for Epicor tax configuration.

What Odoo data does not migrate to Epicor?

Workflows, automations, ir.cron scheduled jobs, Odoo Studio customizations, and custom Python modules do not migrate. The Odoo.sh CI/CD pipeline, custom Odoo apps from the Odoo App Store, and third-party module integrations do not migrate because they are Odoo-specific. Attachments stored as binary blobs in Odoo's PostgreSQL database require extraction and re-upload to Epicor's Document Management. HR-specific fields (emergency contacts, employee categories) that are Odoo-only have no Epicor HR equivalent and require manual re-entry. We deliver a complete data dictionary of every unmigrated Odoo field and artifact so that the customer and Epicor partner can plan the manual re-entry work.

Who performs the Epicor platform implementation alongside the migration?

The Epicor platform implementation (system configuration, user setup, tax connectivity, reporting structure, and workflow rebuild) is performed by an Epicor certified partner, which Epicor requires with a $50,000 minimum implementation fee. FlitStack AI handles the data migration layer: extracting from Odoo, transforming to the Epicor DMT format, and loading via Epicor's native import tools. We coordinate with the customer's Epicor partner during the discovery phase so that the destination Epicor schema is provisioned before migration data arrives, and we hand off the automation and customization inventory to the partner post-cutover for rebuild.

Get a quote

Moving from Odoo ERP to Epicor Prophet 21?

Tell us roughly how many records and objects you have. We scope the mapping and the Epicor Prophet 21 setup with you, then send a quote.

Get a quote