Migrate from Epicor Eclipse to Epicor Prophet 21

Eclipse stores customer records in the CUSTOMER file with ship-to addresses in SHIP.TO, contacts in CONTACT, and classifications in CUSTOMER.CLASS, all stored as UniVerse dynamic arrays. We extract via the Eclipse REST API or direct file parsing, normalize multi-value address structures into Epicor ERP's standard address schema, and map customer-specific pricing classes and credit limits to CustomerPricesch熊 and CreditLimit fields. The customer number from Eclipse becomes the Epicor ERP CustomerID as the dedupe key.

Eclipse vendor records (SUPPLIER file) include PO history, rebate terms, EDI capabilities, and multi-value buying codes. We extract the vendor master, transform vendor-specific classifications into Epicor ERP Vendor records, and preserve EDI capability flags in custom vendor fields. VENDOR.PRODUCT cross-references map to the Epicor ERP PartVendors table with vendor part numbers preserved.

Eclipse Part records (PRODUCT file) contain dynamic attributes, substitute/replacement chains, and warehouse-specific stocking data stored as dynamic arrays. We flatten these into Epicor ERP Part records, mapping unit-of-measure definitions from UOM, product groups from PRODUCT.GROUP, and part classifications. User-defined dictionary fields that were added via UniBASIC are flagged for manual mapping in Epicor ERP's UD field framework.

Eclipse tracks on-hand, allocated, and on-order quantities per warehouse per part using multi-value fields in the INVENTORY file. We extract warehouse-level quantities, map bin and location data to Epicor ERP's warehouse management schema, and validate that on-hand values reconcile to Eclipse's inventory valuation report. Lot and serial number tracking data migrates to PartLot and PartBin tables with full traceability dates.

Open sales orders from Eclipse's ORDER file link to customer, part, pricing, and warehouse records. We extract order headers and line detail, preserving order-specific discounts, notes, and sales person assignments. Order dates, due dates, and ship dates transfer to Epicor ERP SalesOrderHed and SalesOrderDtl. Partially shipped orders require careful line-level status mapping to preserve fulfillment state in the destination.

Eclipse purchase orders include vendor terms, line items, and receiving status. We extract open POs, map them to Epicor ERP PO records, and flag partially-received orders that require line-level receipt handling in the destination. PO approval workflow configurations in Eclipse do not migrate; we document the approval chain for reconstruction in Epicor ERP.

Open quotes from Eclipse's quote file migrate to Epicor ERP QuoteHed and QuoteDtl with full line detail, pricing, and configuration data. Closed quote statistics (win/loss rates, average deal size) summarize into a migration report rather than individual records. Eclipse stores quote lines with configuration chains that require careful field-by-field mapping to Epicor ERP's quote schema.

Eclipse account structures use non-standard numbering and can embed divisions and cost centers in the same field. We extract account masters, segment them per Epicor ERP's chart of accounts structure (Company-Division-Department-Account-SubAccount), and map external account references. Historical account balances transfer to Epicor ERP's GLJrnDtl with the appropriate fiscal period assignments.

Outstanding invoices (AR) and vouchers (AP) are extracted with full aging data, customer/vendor references, and payment terms. We preserve open invoice totals, aging buckets, and apply-to information for reconciliation in Epicor ERP. Lockbox payments and partial payment history migrate as PaymentDtl records attached to the original invoice.

Eclipse customer classifications and pricing assignments map to Epicor ERP CustomerPriceGroup records. Price Break schedules attached to customer classes migrate to PriceLst records with effective dates preserved. This mapping is required before Customer records insert so that pricing group references are satisfied.

Eclipse product categories and classifications (PRODUCT.GROUP file) map directly to Epicor ERP ProductGroup records. The category hierarchy transfers with parent-group references preserved, and each group's default stocking warehouse assignments migrate to the ProductGroup record.

Tax jurisdiction assignments and rates tied to customer ship-to locations in Eclipse's tax master extract to Epicor ERP TaxRegion and TaxConn records. Any tax calculation logic embedded in custom UniBASIC programs is flagged for redeployment as BPMs in Epicor ERP, because tax engine configuration does not migrate as code.

Eclipse stores document images and attachments in file repositories (DOCUMENT file, Document Imaging module). We extract document references and metadata, mapping file paths and image records to Epicor ERP's attachment framework. Image files themselves require separate file transfer rather than API insertion and are flagged as a distinct step in the migration approach.

Eclipse user records include role assignments, warehouse access, and salesperson links. We extract the user master, map to Epicor ERP UserAccount records with role preservation, and flag inactive accounts for admin review before cutover. Salesperson assignments from Eclipse migrate to Epicor ERP SalesRep records linked to UserAccount.