Migrate from Total ETO to Epicor Prophet 21

Total ETO organizes all ETO activity under Projects with a lifecycle from quote through delivery. Epicor Kinetic uses Jobs (manufacturing) and the Project module for extended project costing. We map Total ETO Projects to Epicor Jobs for manufacturing work and to the Epicor Project billing module for project-centric revenue recognition where applicable. Project status, owner, and dates migrate as metadata on the Job or Project record. If the customer uses Epicor Project for revenue recognition on long-cycle builds, we configure the Project setup before migrating the first Project record.

Total ETO Part records carry description, unit of measure, standard cost, supplier link, and a complete usage history trail. We map these to Epicor Part records, preserving PartNumber as the primary key and stocking type (stocked, manufactured, or purchased). Part safety stock, lead time, and costing method migrate as PartPlant and PartCost records. We flag any Total ETO parts with duplicate numbers during extraction so that the Part master is deduplicated before BOM creation, preventing downstream assembly errors.

Total ETO BOMs are multi-level structures with distinct revision history that must not be collapsed into a single BOM at the destination. We treat each BOM revision as a separate Job BOM in Epicor, importing in sequence with revision dates preserved. The parent-component relationships, quantity-per, and operation associations transfer as individual BOM lines. Epicor's Engineering Workbench holds the approved BOM; Job BOMs hold the as-built version for each production run. We map Total ETO's approved BOM revisions to Epicor Engineering BOMs and each build-specific BOM to Job BOMs, maintaining the distinction between design intent and production execution.

Total ETO Customer records include contact details, address, and account balance. We map these to Epicor Customer records, preserving the account balance as open AR. Ship-to addresses migrate as Customer ShipTo records linked to the parent Customer. Open sales orders from Total ETO (if applicable) map to Epicor Orders. Customer credit limits and payment terms transfer to Epicor's Customer credit and terms fields.

Total ETO Vendor records include purchasing terms, contact information, and any active RFQs or POs. We map vendors to Epicor Supplier records, preserving PO terms and preferred carrier information. Active RFQs become Epicor Request for Quotation records; open POs become Epicor Purchase Orders. Supplier part numbers and lead times migrate as Supplier Price records linked to the Part master for each supplier-part combination.

Open POs and RFQs in Total ETO reference live part numbers and vendor commitments. They cannot be imported before the Part master is established at Epicor because line-item part references would resolve to null. We sequence migration: Part master first, then Supplier, then open POs. Any PO lines referencing parts not yet in Epicor are flagged in a pre-migration report and held until the part master is confirmed. Closed POs migrate as historical records if the customer requires AP reconciliation from Total ETO against Epicor's AP module.

Total ETO Work Orders link to Projects and BOMs, tracking manufacturing operations by shop-floor routing. We map Work Orders to Epicor Jobs, preserving the Work Order-to-Project linkage as the Job's ProjectCode reference. Operation sequences and labor class assignments transfer to JobOper and LaborDtl records. If Total ETO tracks sub-operations or outside operations, these map to Epicor JobOper with the Subcontract checkbox and outside processing reference. We validate that the routing operations in Total ETO have matching work centers in Epicor before migration.

Total ETO NCRs reference specific parts, inspections, and quality issues logged from the shop floor, engineering, or procurement. We map NCRs to Epicor's Quality Non-Conformance record type, preserving the part number reference, the disposition (scrap, re-work, use-as-is), and the NCR cause code. The NCR-to-inspection linkage maps to related Non-Conformance records in Epicor Quality. We flag NCR records with unresolved dispositions for the customer's quality team to close post-migration, since Epicor's workflow enforces disposition resolution before closing.

Inspections in Total ETO record quality checks against parts and link to inspectors. We import inspection results as Quality records tied to the relevant Part and Non-Conformance. Inspection type (incoming, in-process, final), measurement data, and pass/fail status map to Epicor's Quality Detail record fields. Inspector names resolve to Epicor Employee records by name or employee number match.

Total ETO tracks on-hand quantities by location and linked to projects via reservation. We import inventory quantities, locations, and project reservations into Epicor PartBin records, flagging any negative or over-reserved quantities that would cause inventory discrepancies post-migration. Warehouse and bin locations map to Epicor Warehse and PartBin bin references. Project reservations migrate as JobMtl reserved quantities linked to the corresponding Epicor Job.

Total ETO Employee records include labor class, department, and time-entry data. We map employees to Epicor Employee records, preserving labor class as the Epicor Resource Group or Labor code assignment. Employee status (active, inactive) migrates, and inactive employees are set to the inactive flag in Epicor to prevent time-entry assignment errors post-migration.

Time entries in Total ETO are project-based with clock-in/clock-out data and geolocation where applicable. We import time logs against the relevant Epicor Job and JobOper using the Employee mapping for labor class resolution. Clock-in/clock-out timestamps map to LaborDtl StartDate, EndDate, and PayHours fields. Any Total ETO time entries without a matching Epicor Job are flagged and held for the customer's project team to resolve, since LaborDtl requires a valid JobNum reference.

Total ETO stores documents linked to projects, parts, and quality records. We extract document references and file paths from Total ETO and map them to Epicor Document Management. Actual file migration depends on the destination's document management configuration — if Epicor EDMS is not enabled, we deliver a file mapping inventory listing source paths and recommended destination paths for the customer's IT team to implement post-migration. PDFs of inspection reports and NCR documents migrate as linked attachments to the corresponding Quality records.