Migrate from ManEx to Epicor Prophet 21

ManEx Customer records map directly to Epicor Customer. We extract via direct SQL query (or UI flat-file export if DB access is restricted) and map Customer ID, name, contact details, billing address, shipping address, and account terms to Epicor Customer and CustomerAddress tables. If ManEx stores multiple contacts per Customer, we extract the primary contact as the Epicor ShipTo primary and create Contact records for additional contacts.

ManEx Vendor master data maps to Epicor Vendor. Vendor ID, name, address, payment terms, and PO history are preserved. RMA associations are preserved as Epicor Supplier Shipment records linked to the Vendor. We handle the distinction between vendor suppliers and customer return RMAs separately during scoping so that the supplier relationship is not merged with return processing data.

ManEx GL account codes and types (asset, liability, equity, revenue, expense) map to Epicor GL Account records. We flag any inactive or suspended accounts for the customer to activate or archive post-migration. Account masks are validated against Epicor's segment structure during the schema mapping phase.

ManEx PO records map to Epicor POHeader and POLine tables. Line items tied to BOMs preserve the BOM reference; vendor assignments and receiving status transfer with explicit status flag mapping (open, partial, closed). Partially received POs retain their receiving history in Epicor's POReceipt and PORel records. PO numbers are preserved as Epicor PONum for audit continuity.

ManEx Sales Orders map to Epicor OrderHed and OrderDtl. Multi-price-list pricing requires value-mapping because ManEx price list IDs are not portable to Epicor; we create Epicor price lists during schema setup and map ManEx price list references to the corresponding Epicor PriceLBrk records. Order statuses (open, on-hold, complete, cancelled) map to Epicor OrderRel status fields.

ManEx BOMs with multi-level component structures and routing data require decomposition during migration. Phantom assemblies are identified by a ManEx flag or by BOM level detection and either flattened into single-level BOMs or preserved as Epicor Product Group relationships based on the customer's Epicor configuration choice during scoping. We flag any BOMs with circular references detected during extraction for manual review before migration.

ManEx real-time shop floor data (labor time, machine cycles, material consumption per work order) maps to Epicor LaborDtl for labor tracking and PartTran for material transactions. Timestamps are preserved to maintain the production history audit trail. If ManEx uses the optional Time and Attendance module, time entries map to Epicor LaborDtl tied to the corresponding employee and work order.

ManEx inventory quantities, locations, and lot/serial data extract from the materials management module into Epicor PartBin (on-hand quantities per warehouse location) and PartLot/PartSerial records for traceability. Multiple warehouse locations are mapped to Epicor PlantWhse records. Lot and serial number history preserves the full traceability chain for compliance requirements.

ManEx open payables migrate to Epicor APOpen and APTran with current status, aging buckets, and payment terms preserved. Historical AP transactions require special handling; if ManEx stores them in archived or compressed tables, we extract them to a reporting archive rather than the live AP tables to avoid performance impact on the new Epicor system.

ManEx open receivables migrate to Epicor AROpen and ARTran with customer linkage, invoice status, aging buckets, and payment terms. Historical AR transactions migrate to a reporting archive if the customer requires access; live AR tables receive open items only to maintain clean accounts receivable aging in the new system.

ManEx RMA records represent return or repair states tied to original SOs or POs. Status codes (open, in-progress, closed) require explicit value-mapping because ManEx and Epicor use different state machines for return processing. Open RMAs migrate as Epicor RMAHead records; repair workflow states map to RMARcpt lines with disposition codes (credit, repair, scrap, return-to-stock) explicitly translated.

ManEx Quote records are migrated with a flag noting their known limitation for complex manufacturing BOMs. Multi-level BOM pricing in ManEx quotes may be incomplete or incorrect; we either migrate quote data as-is with a data-quality flag on the QuoteHed record or exclude quote records from migration scope entirely if the customer prefers to avoid propagating potentially incorrect pricing into Epicor. The customer makes this decision during scoping.

Document attachments stored in ManEx's document management module are not accessible via API and may use proprietary formats. We do not migrate attachments directly. We flag their locations during extraction, provide a file inventory with record associations, and deliver a document relocation plan so the customer's admin can copy attachments to Epicor's ShareFile or external document storage and link them to the corresponding records post-migration.