Migrate from Axelor ERP to Epicor Prophet 21

Axelor Partner is a unified object for customers, suppliers, and prospects with a type field distinguishing each. We partition by Partner.type into Epicor Customer (customer and prospect) and Supplier (vendor) records. Addresses, bank details, and contact persons migrate as related records with the parent Customer or Supplier as the owning entity.

Axelor Products (stocked items and services with BOM support) map to Epicor PartMaster records. Product variants, units of measure, and supplier info migrate as related PartPlant, PartXRef, and PartSup records. Multi-UoM is preserved by mapping Axelor unitOfMeasure to Epicor UOMCode with a UOMClass-based validation check at ingestion.

Axelor Sale Orders and Purchase Orders map to Epicor OrderHed (header) and OrderDtl (line) records. Line items, taxes, discounts, and order status migrate. Axelor's order-to-invoice linking via originId preserves the relationship in Epicor as LinkedOrderNum. Open orders at migration time are flagged and reconciled separately; only confirmed or historical orders migrate while active transactional state is re-entered in Epicor at cutover.

Axelor invoices are multi-currency and multi-company aware. We separate open invoices from historical records: open invoices remain in Axelor for payment processing and are excluded from migration; historical invoices migrate as read-only records into Epicor ARInvoice (customer invoices) or APInvoice (vendor invoices) with invoice lines, tax computation, and payment terms preserved.

Axelor Projects contain Tasks, Milestones, Time Entries, and Invoicing Plans. We extract the full project hierarchy including subtask nesting, assigned users, and billing rates. Project status and custom fields migrate. Epicor Project records support WBS (Work Breakdown Structure) hierarchies that align with Axelor's task nesting model.

Axelor Tasks belong to Projects and carry status, priority, assignees, and custom fields. Subtask inheritance varies by Axelor version; we flatten the hierarchy where Epicor does not support nested task structures and map to LaborDtl for time-tracking entries and ProjPhase for phase-level work breakdown.

Axelor Stock Moves track internal transfers, receipts, and shipments with real-time inventory impact. We extract move lines, warehouses, and lot/serial numbers into Epicor PartTran records. Open moves at migration time are flagged so that the customer can complete or cancel them in Axelor before cutover, then re-enter the resulting inventory adjustments in Epicor.

Axelor's Chart of Accounts, Journals, and Journal Entries with debit/credit lines and analytic accounts map to Epicor GlJournal. Multi-company journals require inter-company entry splitting per company and a custom reference field for post-migration reconciliation. We do not migrate accounting balances as live records; historical journal entries migrate as reference data for audit trail only.

Axelor Employee records include contact info, job title, department, and employment dates. We map to Epicor Employee records and preserve the reporting-line structure via the Supervisor field where Epicor supports it. Epicor Employee is scoped to a single Company; multi-company Axelor deployments map employees to the primary company in Epicor unless separate company codes are provisioned.

Axelor BOMs define product component lists and routing steps for manufacturing. Axelor's BOM versioning is preserved by mapping the active BOM to Epicor PartMtl records linked to the PartMaster, with alternate BOMs stored as BOM records with alternate markers. Routing steps migrate to PartOpr if Epicor MES is in scope. BOM revision control migrates to Epicor's ECO (Engineering Change Order) model.

Axelor stores file attachments against any record via its document management module. We export file metadata (filename, size, record association, and URL path) but file binaries require separate storage handling via SFTP or cloud storage sync to move the actual documents to the destination environment. Attachment metadata is imported as a URL reference in Epicor's External MES or Document Management tables.

Axelor Studio allows creation of entirely custom domain objects stored in the same database with XML model files. We enumerate every non-standard model at scoping time by inspecting the application's XML domain files, pre-create corresponding custom tables or UD fields in Epicor Kinetic, and migrate the records with the same relationship structure. If an Epicor equivalent does not exist, we document the gap and recommend a rebuild approach for the implementation team.