Migrate from iDempiere to Epicor Prophet 21

iDempiere Business Partners cover customers, vendors, and leads in a single record type with a BP Classification flag. We split these into Epicor Customer (IsCustomer=true) and Vendor (IsVendor=true) records. The BP's location tabs map to Epicor ShipTo and PurPoint records. Credit limits and payment terms transfer as CustomerCreditHold and Terms records. The BP's pricing schema maps to Epicor PriceLDisc records. Dedupe uses BP Value as the external reference key in Epicor.

iDempiere's Client > Organization hierarchy maps to Epicor Kinetic's Company > Site structure. The top-level iDempiere Client becomes the Epicor Company, and each child Organization becomes a Site under that Company. We import the full org tree first in Epicor because all subsequent records (Products, Orders, Projects) require a Site reference. Multi-ledger configurations in iDempiere map to Epicor multi-company structures if the customer operates separate legal entities.

iDempiere Products map to Epicor Part records. The iDempiere Product Type (Item vs Service vs Resource) maps to Part's TypeCode. Product costing method transfers to Epicor's Costing Method field. BOM structures migrate to Epicor's BOM (PartMtl) and Routing (PartMtlOperation) records. Product variants and configured products in iDempiere map to Epicor PartRev configurations. Stocking settings and warehouse assignments transfer to PartWhse records with Site-specific stocking locations.

iDempiere Orders (C_Order) with header/line structures migrate to Epicor OrderHed (header) and OrderDtl (lines). Order status, pricing, tax treatment, and GL journal references preserve. Lines link to the correct Part via PartNum and to the correct Customer/Site via ShipToNum. Payment terms and discounts transfer from iDempiere's payment rule fields to Epicor's Terms and LineDiscount fields. Historical closed orders migrate as completed records; open orders migrate as open with the same document status.

iDempiere Invoices map to Epicor InvoiceHed and InvoiceDtl. Both AR and AP invoices are handled separately. Document status, tax treatment, payment terms, and GL journal references preserve. Lines are linked to the parent OrderDtl reference if the invoice originated from an order. Open AR/AP invoice balances transfer as outstanding amounts. Invoice payment allocations migrate to Epicor's Cash Receipt andAP Payment records.

iDempiere payment batches and cash journal entries migrate to Epicor CashHead and associated payment records (ARPmt for receivables, APPmt for payables). Bank statement mappings transfer as BankRec records. Open AP/AR records carry their payment terms and aging bucket assignments. Allocation details preserve across payment-to-invoice matching records.

iDempiere Projects with phases, tasks, milestones, and time entries migrate to Epicor Project and ProjectPhase records. Resource assignments map to ProjectResource records. Project status and WBS structure preserve. Time entries migrate as LaborDtl records linked to the project. Milestone billing in iDempiere maps to Epicor's billing release mechanism. Custom project types defined in iDempiere's Application Dictionary require schema migration before the project data can load.

iDempiere fixed asset registers with depreciation schedules migrate to Epicor FAsset and FAssetBooks. Depreciation method (straight-line, declining balance, units of production) transfers to Epicor's depreciation calculation fields. Insurance mappings and asset book values preserve. Service history tied to each asset transfers to FAssetReg records.

iDempiere's accounting schemas and dimensional GL chart of accounts must be recreated in Epicor Kinetic's Company and Fiscal Year configuration. Account dimension structure (Legal Entity, Business Partner, Product, Location) maps to Epicor's natural account and division/cost center structure. The GL journal header/line model is equivalent between platforms. GL journal entries migrate as Epicor GLJrnHed and GLJrnLine records with full debit/credit and dimension references.

Custom iDempiere windows backed by Application Dictionary tables migrate their underlying table data to Epicor UD tables (UDXX). We export the table schema and data via direct database queries. The visual form layout does not migrate; it must be recreated in Epicor Designer by the customer's Epicor administrator post-migration. This is a scope limitation across all ERP-to-ERP migrations.

iDempiere attachments stored in the database (Lob) or filesystem migrate to Epicor's File Manager and Content table. We run the Migrate Storage Provider plugin in iDempiere before extraction if attachments are split across both storage types. Database blob attachments export to files first. Filesystem attachments copy directly if paths are accessible. Epicor's FileManager and ContentLib handle storage in the cloud or on-premise deployment.

iDempiere users and role-privilege assignments migrate to Epicor UserCode and Employee records. The iDempiere role-privilege matrix maps to Epicor's Role and SecCode records. Multi-org role scoping in iDempiere maps to Epicor's Company/Site security assignments. User provisioning in Epicor requires the customer's admin to create UserCode records with the appropriate access before we assign OwnerId on transactional records.

iDempiere bank accounts and cash journal accounts with currency and GL account mappings migrate to Epicor BankCode and CashFX records. Opening balances transfer as GL journal entries in the Epicor target accounting schema. Currency assignments and exchange rate settings preserve.

iDempiere tax categories, rates, and validity windows migrate to Epicor TaxMaster and TaxJurisdiction records. Tax jurisdiction assignments per location transfer so that correct rates apply post-migration. Tax type (sales tax, VAT, withholding) maps to Epicor TaxType. Tax validity date ranges preserve to maintain retroactive tax treatment on historical records.

iDempiere Point of Sale records migrate to Epicor POS Terminal and TenderType configurations. Cash register configurations and payment type assignments transfer as part of the POS setup. This object is included when the source iDempiere instance uses the POS module; it is excluded otherwise.