Migrate from Aptean Compiere ERP to Epicor Prophet 21

Aptean Compiere's unified Business Partner entity covers both customers and vendors in a single table (C_BPartner). During migration, we split the source records into Epicor Customer and Supplier tables. Customer records carry the Compiere BP location, tax ID, and credit limit fields. Supplier records carry vendor payment terms and Remit-To address data. BP Group assignments (C_BP_Group) map to Epicor's CustomerType or SupplierType codes, and the IsCustomer / IsVendor flags on the source record determine which Epicor tables receive each row.

Compiere's three-tier System-Client-Organization hierarchy maps to Epicor's Company-Site structure. Each Compiere Organization under the Client becomes an Epicor Site within the target Company. We preserve the Organization name as the Site description and map the AD_Org_ID reference to the Epicor Plant table (Plant table for manufacturing sites or Site for distribution-only sites). Multi-org security boundaries from Compiere (role-based access per Organization) do not carry over; we document the source Org-to-role mapping for the customer's Epicor admin to reconfigure in Epicor's Role and Company-Plant security model.

Compiere Products map to Epicor Part records. The M_Product_ID becomes PartNum; ProductType (Item, Resource, Service, Online) maps to the Epicor PartType field. The source Product Category (M_Product_Category_ID) maps to Part.ClassID and the Epicor PartClass table. Stocked and non-stocked product types carry over as TypeCode values. We preserve the source's UPC/EAN from the product barcode table as the Part.SNMask where applicable.

Compiere multi-level BOMs map to Epicor's manufacturing BOM structure. Stocked BOMs in Compiere become JobMtl entries under a Job record in Epicor; non-stocked BOMs become PartMtl (kit) entries on the Part record. We traverse the Compiere PP_Product_BOM hierarchy up to the configured depth (default 10 levels) and reconstruct the Epicor JobMtl or PartMtl lines in order, setting the QtyPer and BukcetAssemblySeq fields to match the source. Phantom BOMs in Compiere (phantom flag PP_BOMType) map to Epicor JobAsmbl records with the Phantom field set.

Compiere Warehouses map to Epicor Warehouse records. The M_Warehouse_ID and Warehouse Name carry over. Compiere's warehouse-level attributes (including IsInTransit and IsActive flags) migrate to the Epicor Warehouse table fields. We create one Epicor Warehouse per source Compiere warehouse during the import phase.

Compiere Locators support up to five user-defined dimension fields (Aisle, Bin, Rack, Level, Bay) per warehouse. Epicor's bin structure is a two-level Warehouse-Bin hierarchy with no native dimension extensibility. We flatten the five Compiere dimensions into a single BinNum field using a configurable delimiter pattern (e.g., Aisle-Bin-Rack-Level-Bay = A01-B02-R03-L04-B05). The customer selects the delimiter during scoping. We preserve the full five-dimension source values in a custom UD field on the Epicor Bin record so the admin can query by any original dimension after cutover. This is one of the most transformation-intensive mappings in the migration and requires a dedicated data mapping pass.

Compiere Purchase Price Lists map to Epicor PriceLDisc records with PriceLCode pointing to a vendor-specific price code. The source C_BPartner_ID links the price list to the Vendor (Supplier) record in Epicor. Effective dates (M_PriceList_Version.ValidFrom) map to Epicor PricePerCase dates for contract pricing validity. We map M_PriceList line records (M_ProductPrice) to PriceLDisc lines with the correct breakQty and UnitPrice values.

Compiere Sales Price Lists map to Epicor PriceLDisc records with PriceLCode pointing to a customer or general price code. Customer-specific price lists in Compiere (where the price list is assigned to a C_BPartner) become Epicor PriceLDisc records scoped to the customer number. General sales price lists become Epicor PriceLDisc records with no customer restriction. Date-controlled pricing in Compiere (special sales initiatives with effective dates) maps to Epicor's effective and expiration date fields on the PriceLDisc header.

Compiere uses country-specific AccountingXX.csv (e.g., AccountingUS.csv) as the import basis for the Chart of Accounts. We parse the source CSV, preserving the natural account structure, account type (AccountType column), and default mappings (Account_Default column for mandatory accounts). These import into Epicor's GLAccount table via the Chart of Accounts segment definition (COASeg) and account code structure. Compiere's Accounting Schema framework (multiple accounting standards per organization) maps to Epicor's GLBook table, where each accounting schema becomes a GLBook with the appropriate fiscal calendar and currency settings. This mapping requires the customer to confirm whether they use a single Epicor GLBook (single accounting standard) or multiple GLBooks (multi-GAAP or multi-subsidiary reporting).

Open Accounts Payable records from Compiere (C_Invoice with C_BPartner_ID where IsPaid=N) migrate to Epicor APInvoice header records and APInvoiceDtl lines. The Compiere C_InvoicePaySchedule table (payment schedule) maps to Epicor's terms and due date logic. Open Accounts Receivable records (C_Invoice with IsSOTrx=Y and IsPaid=N) migrate to Epicor ARInvoice header and ARInvoiceDtl lines. We migrate open invoices only; historical closed invoices are scoped separately to avoid Epicor's invoice reconciliation conflicts on closed periods. The migration team coordinates with the customer's finance lead to agree on the open-item cutoff date before this phase runs.

Compiere Product Categories (M_Product_Category) map to Epicor PartClass records. The Product Category's default expense and revenue account references from Compiere map to Epicor's PartClass.Default LaborAccount, BurdenAccount, MaterialBurdenAccount, and OtherAccount fields. Discount structures set globally on the Compiere Product Category inherit into Epicor's PartClass pricing defaults, and the customer reconciles the pricing inheritance model during post-migration configuration.

Compiere's three-tier role security (System, Client, Organization level roles) maps to Epicor's Role and Employee security model. We extract AD_User and AD_Role records and match Compiere users to Epicor Users by email. The source role-per-Organization assignments map to Epicor Plant or Site-level security roles. Users without a matching Epicor employee record go to a reconciliation queue for the customer's Epicor admin to provision before record import. We do not migrate Compiere role permissions as code; we deliver a written role matrix document for the admin to reconfigure in Epicor Security Administration.

Open Sales Orders from Compiere (C_Order with DocStatus in Draft, In Progress, or Completed) migrate to Epicor OrderHed header and OrderDtl lines. Compiere order lines (C_OrderLine) map to Epicor OrderDtl with LineNumber, PartNum, SellingQuantity, UnitPrice, and Tax amounts preserved. The source C_BPartner_Location_ID (ship-to address) maps to the Epicor ShipToNum reference on OrderHed. We do not migrate completed or closed Compiere orders unless the customer explicitly scopes historical order carry-over; Epicor's fiscal period and GL date constraints on historical order import require a separate agreement during scoping.

Open Purchase Orders from Compiere (C_Order with IsSOTrx=N and DocStatus not Closed) migrate to Epicor POHeader and PODetail. The Compiere vendor (C_BPartner_ID as vendor) maps to Epicor's VendorNum reference. PO line quantities and prices carry over from Compiere's C_OrderLine. Line delivery dates from Compiere's DeliveryVia and ShipPer rules map to Epicor's PromiseDate and DueDate fields. We scope open purchase orders only; closed and received-in-full POs are excluded to avoid Epicor's receiving validation conflicts.

Compiere Active Data Dictionary custom fields (columns added via the AD Column table with IsCustom=Y) migrate to Epicor User Defined fields. We audit the Compiere AD_Column and AD_Table metadata to identify every custom column, extract its data type, and create an equivalent Epicor UD field (e.g., Character01, Number01, CheckBox01, or a formal UD Field definition via Epicor's Customization Editor). Compiere custom tables created via the Visual Dictionary Editor map to Epicor UD## tables. We pre-create the Epicor UD schema before any record migration so that parent-record UD field references resolve at import time.