Migrate from iXERP Standard to Epicor Prophet 21

iXERP Customer records map to Epicor Customer Maintenance with the customer code, name, address, and financial balances transferred as opening balances or on-account credits. Epicor's Customer form includes Bill-To and Ship-To locations; we split iXERP's single-address customer into these two contexts where applicable. Any duplicate customer names are flagged in the pre-flight reconciliation queue.

iXERP Vendor records map to Epicor Supplier Maintenance with supplier code, name, address, and payment terms. Vendor-specific tax registration numbers and currency codes transfer to Epicor Supplier attributes. We validate currency alignment against Epicor's multi-currency configuration during scoping.

iXERP Items with stock SKUs, non-stock items, and services map to Epicor Part Master. The iXERP Item Code becomes Epicor Part Number; cost prices, selling prices, and stock-on-hand quantities transfer to Epicor's on-hand quantity fields by Plant and Warehouse. Serial and batch tracking fields migrate where configured. BOMs and routings that exist as separate iXERP records map to Epicor Bill of Materials and Job Routing tables during a subsequent phase.

iXERP Sales Orders map to Epicor OrderHed (header) and OrderDtl (line) records. Header fields including order number, customer reference, order date, and terms migrate; line items map with part number, quantity, unit price, and discount. Open orders and historical orders migrate together; fulfilment status fields from iXERP map to Epicor's OrderRel release records. If iXERP uses multi-release sales orders, each release becomes a separate OrderRel against the same OrderDtl.

iXERP Purchase Orders map to Epicor POHeader and POLine records. Vendor reference, PO date, terms, and line items carry across with quantity ordered, received-to-date, and unit cost preserved. Epicor's two-line purchase order structure (release lines vs. demand lines) requires a mapping design decision during scoping if iXERP holds blanket PO releases.

iXERP Issues (AR) and Receipts (AP) Invoices migrate to Epicor InvcHead and InvcDtl. Multi-line detail, tax codes, and payment status map to Epicor equivalents, but the invoice numbering sequences differ between systems and must be reconciled. Closed and paid invoices migrate as historical records; open invoices require additional attention to ensure outstanding balances appear correctly in Epicor's AR Aging after migration. Invoice type naming conventions between iXERP and Epicor must be agreed during mapping design.

The iXERP general ledger structure with account codes, names, types, and tax codes maps to Epicor GL Account records. We map account types to Epicor account categories (Asset, Liability, Equity, Revenue, Expense), preserve account codes as the natural account identifier, and carry forward the current period balances as Epicor GL Account Balances. If iXERP uses cost centres within accounts, we evaluate whether these map to Epicor Reference codes or separate accounts during scoping.

iXERP bank and cash account balances transfer to Epicor BankAcct records with opening balances and reconciliation data preserved where dates permit. Transaction history migrates as GL Journal records if scoped; we flag gaps in historical bank transaction detail during the pre-flight audit.

iXERP Projects map to Epicor Project records with project headers, milestone dates, assigned resources, and task hierarchies preserved. Project-level custom fields from iXERP transfer to Epicor Project User Defined fields. If iXERP Projects use billing schedules, these map to Epicor Project Billing.

iXERP Tasks attached to Projects migrate to Epicor Project Tasks with assignees, status, planned hours, and actual hours carried across. The task-to-project parent relationship is preserved via Epicor's Project/Phase/Task hierarchy. Time entries associated with tasks transfer as Project Labour bookings where Epicor's Project Billing module is active.

iXERP HR Employee records map to Epicor Employee Basic records with personal details, job roles, departments, and compensation fields. Effective-dated fields require careful handling; we map hire date, job title, and department to Epicor Employee data, and flag any compensation or benefits fields that require manual entry or extended field configuration. This is a mapping rather than a full migration because Epicor's HR module scope varies by edition.

iXERP inventory transactions (stock movements, adjustments, and transfers) map to Epicor PartTran records. Historical transaction volume can be large; we scope migrations by date range and flag any truncation required due to destination data retention or performance constraints. Epicor's PartTran requires a valid Part Number and Warehouse/Plant context that must be resolved from iXERP's stock location fields during the transform phase.

iXERP HelpDesk tickets with customer references, agents, status, and conversation history map to Epicor Service Management tickets. Ticket headers and associated conversation threads migrate; agent assignments and custom ticket fields transfer to Epicor Service Case records. If Epicor Service module is not active in the destination, tickets map to a generic Case object configured during schema design.

iXERP custom fields across CRM, project, and HR modules are detected during profiling and mapped to Epicor User Defined Fields on the matching objects. We pre-create the UDF schema in Epicor before any data import, matching iXERP field types to Epicor data types (text, number, date, logical, list). Custom field naming follows Epicor conventions with a UDF prefix. Any iXERP custom fields without a clear Epicor target are stored as extended attributes in a dedicated migration audit table for the customer's admin to assign post-migration.