Migrate from Infor VISUAL to Epicor Prophet 21

VISUAL Work Orders map to Epicor Job records. The Work Order header fields (WONum, Status, Priority, ScheduledStart, ScheduledEnd) map to JobHead fields (JobNum, JobClosed, TopicID1, StartDate, DueDate). Material lines attach to JobMtl with the operation sequence number preserved so that Epicor's material release scheduling respects the original VISUAL operation-to-material dependency. We reconstruct the linkage by joining on Work Order header and operation sequence number during the transform phase before inserting into JobMtl.

VISUAL Routings map to Epicor JobOper records. Operation sequence, work center, setup time, run time, and resource requirements transfer as JobOper rows with OpCode, EstSetHours, EstProdHours, and ResourceGrpID. Multiple work centers per operation from VISUAL generate multiple JobOper rows in Epicor with the same OperSeq.

VISUAL's scattered BOM structure (materials attached to specific operations) requires reconstruction: we extract all material-operation pairs, then load Epicor PartMtl with MtlSeq and related back to the JobOper sequence where applicable. For multi-level BOMs, we explode the structure during the transform and write each level as a separate PartMtl group. We flag cases where the destination BOM structure is centralized and the customer's routing-specific material overrides require post-migration configuration in Epicor.

VISUAL Customer Orders map to Epicor OrderHed and OrderDtl records. Order headers carry customer, ship-to, terms, and carrier; line items carry part number, quantity, unit of measure, price, and promised date. EDI-ready CPO transaction set data from VISUAL transfers as OrderRel release records if the destination uses drop-ship or multi-release order patterns.

VISUAL Purchase Orders map to Epicor POHeader and PORel records. Line detail (part number, quantity, due date, unit cost) migrates as POLine, and release schedules migrate as PORel. ASN data from VISUAL's fixed-length file exports (EDI 856) transfers as Shipment records linked to the PO.

VISUAL invoices export as EDI 810 fixed-length files or Excel exports. We map header fields (invoice number, date, customer, terms) to InvcHead and line detail to InvcDtl. Custom invoice layouts or notes fields requiring special formatting are flagged as requiring post-migration review in Epicor's report designer. Open invoice status (paid, partial, outstanding) migrates with payment terms preserved.

VISUAL Item records (SKU, description, unit of measure, standard cost, revision) map directly to Epicor Part. We preserve revision control by mapping PartRev records where VISUAL uses engineering revisions. Custom properties and user-defined fields on Items require pre-creation of Epicor UD fields before migration. PartClass and Commodity Code mapping is preserved for costing and procurement categorization.

VISUAL Customer records map to Epicor Customer with contact and address detail. Credit limits, payment terms, and carrier assignments migrate as Customer fields. We cross-reference by customer number as the dedupe key. EDI trading partner assignments from VISUAL's separate configuration records are mapped to Epicor Trading Partner entities during the EDI configuration extraction phase.

VISUAL Vendor records map to Epicor Supplier with address, payment terms, and EDI configuration. Vendor number is the dedupe key. EDI configuration from VISUAL's separate records (partner ID, transaction set version, BOL formatting) migrates as Epicor Trading Partner configuration attached to the Supplier record. We flag duplicate vendor names for customer admin resolution before final load.

VISUAL Employee records (pay rates, departments, cost center assignments) map to Epicor EmpBasic. Where VISUAL uses effective-dated compensation history, we map the current active record and flag historical pay rate records that require manual re-entry in Epicor HR. Labor rates for job costing transfer to EmpBasic as HourlyRt.

VISUAL GL account structure and balances export via the database export tool or Excel. We map account codes and descriptions to Epicor GLAccount with segment structure preserved. Multi-company or intercompany account segments that use segment-level detail in VISUAL are flagged for segment-level configuration in Epicor's COA before balance load.

Open payables and receivables require balance verification during migration. We extract open invoice detail from VISUAL (invoice number, date, amount, balance, payment status), map to Epicor APInvHed (for payables) and ARInvoiceHed (for receivables), and flag records where partial payments have created split-balance scenarios requiring Epicor's payment application logic to reconcile.

VISUAL quality data (inspection results, non-conformance records) may exist in custom tables. We assess the schema during discovery, flag whether quality data is migratable to Epicor's QA module, and document any records requiring post-migration manual re-entry. If VISUAL uses the MES quality module, we map inspection data to QAGroup and QALog records in Epicor.

VISUAL document attachments stored in its file management system require a separate file-system extraction step. We do not migrate binary file blobs directly. We document the source file paths and advise the customer's admin to relocate documents to Epicor's document management module (DocStar or Kinetic EDM) post-migration. The file path inventory is included in the handoff documentation.