Migrate from Total ETO to Infor CloudSuite Corporate

Total ETO Projects organize all ETO activity from quote through delivery with status stages and owner assignment. We map Projects to CloudSuite Industrial's SFC Project module (or LN Project Management for CloudSuite Industrial Enterprise deployments). The Project status stages in Total ETO map to the SFC Project lifecycle stages at the destination. Project-linked Work Orders and BOMs reference the Project as a parent, so the Project import must complete before Work Order and BOM migration begins. Cost tracking data from Total ETO's job costing fields migrates to the corresponding cost roll-up fields in SFC Project costing.

Total ETO BOMs are multi-level, dynamically versioned structures. Each BOM revision is a distinct object in Total ETO, and we preserve that distinction by importing each revision as a separate BOM version in Infor CloudSuite's SFC BOM module. Collapsing BOM revisions into a single flat BOM destroys the engineering change history and breaks downstream production planning that relies on revision-date ordering. We import BOMs in revision-date sequence, map the parent-component relationships to Infor's BOM operation routing, and flag any BOM that references a Part not yet established in the destination as an import exception requiring resolution before proceeding.

Total ETO Part records carry description, unit of measure, cost, supplier link, and usage history across projects. We map Parts to the Infor CloudSuite Item Master with type (manufactured, purchased, phantom), sourcing rules, and cost element assignments. The Part master must be imported and validated before BOMs, POs, and Inventory can import because BOM line items and PO lines reference Item records by Part number as a foreign key. Any Parts with duplicate Part numbers across Total ETO contexts are reconciled during the Part master phase with a deduplication strategy documented for the customer's review.

Total ETO Customer records include contact details, address, and AR balance. We map to Infor CloudSuite's Customer master, preserving the AR balance as an open item at migration date. Customer addresses migrate to the Infor address structure with ship-to and bill-to designations. Open Sales Orders in Total ETO, if present, map to Infor Sales Orders with Customer linkage established through the Customer master import.

Total ETO Vendor records include purchasing terms and contact information. We map to Infor CloudSuite's Supplier master, preserving any active vendor-specific pricing agreements. The Supplier master must be established before open Purchase Orders and RFQs import because PO headers reference the Supplier as a required field.

Open POs in Total ETO represent live procurement commitments referencing specific Part numbers and quantities. We sequence PO migration after the Part master, BOMs, and Supplier master are established — without these dependencies, foreign-key violations block PO line imports. We preserve PO status (open, partial receipt), line quantities, and unit costs. RFQs are handled as a separate open-RFQ object with status preserved for the customer's purchasing team to convert or close post-migration.

Total ETO Work Orders link to Projects and BOMs, tracking manufacturing operations by shop-floor routing. We map to Infor CloudSuite SFC Work Orders with the Project and BOM version references resolved at migration time. Work Order operations (routing steps) migrate as sub-records of the Work Order. Any Work Order referencing a BOM revision not yet migrated is held in a dependency-exception queue and resolved before the Work Order import proceeds.

Total ETO tracks on-hand quantities by location and links reservations to Projects. We import inventory quantities by location into Infor CloudSuite's Inventory module, preserving project-linked reservations as inventory allocations. Negative quantities and reserved quantities that exceed available stock are flagged as exceptions requiring customer review before the inventory snapshot is committed.

Total ETO NCRs reference specific Parts, Inspections, and quality issues logged from shop floor, engineering, or procurement. Infor CloudSuite Industrial Enterprise includes a Quality Management module with NCM tracking; CloudSuite Industrial SyteLine requires configuration as part of migration scope. We map NCR status, disposition, and root cause to the QM NCM record, preserving the link to the relevant Part and Work Order. NCRs without a corresponding Quality Management configuration at the destination are flagged for manual setup or a separate QM configuration engagement.

Total ETO Inspections record quality checks against Parts and link to the inspector. We import inspection results as Quality Inspection records in Infor CloudSuite tied to the relevant Part and NCR where the QM module is configured. Inspection pass/fail status and measurement values migrate to the inspection record. Where the QM module is not configured at the destination, inspection results are exported as a structured data file with a mapping guide for the customer's Infor consultant to configure the module.

Total ETO Employee records include labor class, department, and time-entry data. We map to Infor CloudSuite HCM Employee records, preserving department and labor class assignments. Active status and employment dates migrate. Time-entry logs (clock-in/clock-out, project assignment, hours) are imported against the corresponding Project and Work Order, with labor class determining cost allocation at the destination.

Total ETO integrates with external accounting systems (QuickBooks, Sage) rather than maintaining its own GL. We scope whether the customer's financial records (account balances, open AP/AR) live in Total ETO or in the connected accounting system. If the destination is Infor CloudSuite with full GL, we coordinate the Chart of Accounts migration from the connected accounting package (not from Total ETO, which does not hold GL data). Account balance carry-forward requires a period-end reconciliation from the source accounting system before GL go-live.