Migrate from ERP Mark 7 to Epicor Prophet 21

ERP Mark 7 Customer records map to Epicor Customer (CustCnt parent records attached per Customer). We map address, contact details, payment terms, and 1099/W-9 status directly. The customer number from ERP Mark 7 becomes CustNum in Epicor with the original code preserved in the user-defined fields if it differs from the Epicor-assigned sequence. Multi-ship-to configurations in ERP Mark 7 map to Epicor ShipTo records linked to the Customer parent.

ERP Mark 7 Vendor records map to Epicor Vendor (VendCnt child records attached per Vendor). We preserve 1099 settings, W-9 status, payment terms, and bank information. The ERP Mark 7 vendor number becomes VendorNum in Epicor with the original code retained in a user-defined field. Multi-address vendors map to Epicor Vendors with VendCnt contact and address records.

ERP Mark 7 Items (products, raw materials, services) map to Epicor Part records. Item type (inventory vs. non-inventory vs. service) maps to Part.TypeCode. ERP Mark 7 custom fields on Items migrate to Epicor user-defined fields on Part. We flag any non-standard unit-of-measure configurations in ERP Mark 7 for manual review in Epicor Unit of Measure setup before Part import.

ERP Mark 7 COA entries map to Epicor GL Account records. We map account number, name, description, and account type directly. Any non-standard segment configurations (2-segment vs. Epicor's natural account + separate department segments) require a mapping table we build during schema design. The customer confirms the Epicor COA structure before we begin account import.

Open receivables in ERP Mark 7 migrate to Epicor Invoice records with invoice type AR Invoice. We carry through invoice number, customer reference, invoice date, due date, aging bucket, payment method, and outstanding balance. Each invoice creates an open AR record in Epicor with a remaining balance for reconciliation in the current fiscal period. Prepayments and credit memos migrate as separate invoice types.

Open payables in ERP Mark 7 migrate to Epicor AP Invoice records. We carry through vendor reference, invoice date, due date, aging bucket, payment terms, and outstanding balance. The AP Invoice is created in Epicor with the remaining balance open for reconciliation. Prepayments and debit memos migrate as separate AP Invoice types.

ERP Mark 7 Work Orders map to Epicor Job records. ERP Mark 7 links Work Orders to Items (as the part number) and BOMs; we reconstruct the Epicor JobMtl (material requirements) and JobOper (operation steps) records from the ERP Mark 7 work order structure. Custom fields on ERP Mark 7 work orders (machine center, priority flags) map to Epicor Job head user-defined fields and to JobOper user-defined fields. We flag active vs. completed Work Orders separately: active orders migrate as open Jobs; completed orders migrate as closed Job records.

ERP Mark 7 Items with Bill of Materials structures map to Epicor PartBillOfMtl records. Multi-level BOMs (parent, sub-assembly, component) require recursive mapping: we build the parent-to-component relationship and set the MtlBurden for each material line. If ERP Mark 7 uses phantom BOMs or co-products, we map these to Epicor PartBillOfMtl with the appropriate Revision and MtlPartNum references. BOM revision control in Epicor requires a target revision to be active before BOM import.

ERP Mark 7 Item routing steps (if exposed via schema discovery) map to Epicor PartOpr records linked to the Part. Each operation step includes Work Center, labor hours, machine hours, setup time, and operation sequence. If ERP Mark 7 routing data is not accessible via API or database export, we flag this during scoping and the customer works with their Epicor partner to rebuild routing data from source documents.

Historical journal entries from ERP Mark 7 migrate to Epicor GLJrnLine records with fiscal period and fiscal year preserved. We segment historical data into pre-close and post-close batches: closed fiscal periods migrate as locked historical records; the current fiscal year migrates as open with a reconciliation step at cutover. Manufacturing transactions (PartTran records) migrate from ERP Mark 7 transaction history if accessible; PartTran carries part, quantity, warehouse, and plant data and requires a Part to exist in Epicor before PartTran insert.

ERP Mark 7 document attachments (stored as binary files linked to transactions, Items, or Customers) export in their native format and re-attach to the corresponding Epicor records via Epicor's Document Management (EDMS) module. We map the source record type and ID to the Epicor Key1, Key2, Key3 fields for traceability. Large binary attachments are chunked and validated post-upload.

ERP Mark 7 user-defined fields on standard objects (Customer, Vendor, Item, Work Order) map to Epicor user-defined fields on the equivalent table. We discover the full custom property set during the schema audit phase, diff against the standard object definition, and create corresponding Epicor UD columns before record import. Any UD fields that cannot map directly are flagged in the mapping document for manual entry or custom BPM population logic.

ERP Mark 7 User records (name, email, role, department) map to Epicor User records. Role names do not map 1:1 because Epicor uses its own security model with Company, Plant, Warehouse, and Department-based permissions. We match by email and flag roles requiring manual reassignment in Epicor User Security setup. Inactive users migrate with IsActive=false.

ERP Mark 7 Departments map to Epicor Department records. ERP Mark 7 allows nested hierarchies; Epicor uses a flat department structure per Company. We flatten nested ERP Mark 7 departments into Epicor Department records and flag any cost-center reporting dependencies that require reconfiguration post-migration.