Migrate from Total ETO to Acumatica

Total ETO Customer records map to Acumatica Customer entities. Address, contact, and payment terms transfer directly. Multi-location customers in Total ETO map to Acumatica's Location sub-grid on the Customer screen — we preserve all location addresses. The mapping also includes default shipping and billing preferences.

Vendor records transfer 1:1. Total ETO's vendor contacts and payment terms map to Acumatica's Vendor record with its Remittance Information tab. Vendor part numbers stored in Total ETO map to Acumatica's Vendor Inventory tab on the Vendor record. All entries are validated for completeness before import.

Total ETO items that are purchased-only (no BOM) become Acumatica Non-Stock Items. Items with BOMs become Stock Items. The item type decision is made per Total ETO part record based on whether a BOM is attached — we classify each record during the mapping phase.

Total ETO Job is the central project entity — it maps to an Acumatica Project with a default task representing the job scope. If Total ETO uses phases within a job, each phase becomes a separate Project Task. Project Status and PM are populated from Total ETO job stage and owner respectively.

Total ETO's single-level dynamic BOMs decompose into Acumatica's multi-level BOM structure. The top-level assembly maps as the BOM header. Sub-assemblies and purchased parts are child BOM lines. Each Total ETO BOM revision becomes an Acumatica BOM Revision with an Effective Date — revision history is preserved in the revision record.

Total ETO sales orders map to Acumatica Sales Orders with order type, customer, line items, and scheduled dates preserved. The order's linked Job becomes the Project reference on the SO line — line-level project and task are populated from the source order's job association.

Total ETO POs transfer to Acumatica POs with vendor, line items, quantities, and promised dates. If a PO is linked to a Job in Total ETO, the corresponding Project and Task are set on each line. Open POs and closed POs both migrate — status is preserved.

Total ETO labor bookings and material issues against a Job map to Acumatica Project Transactions. Direct labor hours with labor codes become labor transactions on the Project Task. Material issues from Total ETO inventory against a job become non-stock issues on the Project Task.

Total ETO's WIP view per job has no direct Acumatica equivalent — WIP values are preserved as Project Custom Fields (WIP_Amount__c) and updated via project cost transactions. We surface the WIP figure as a reference field so your PM can verify cost accumulation post-migration.

Total ETO estimates migrate as Acumatica Quotes by default. If your team uses estimates as the basis for awarded jobs, we can migrate estimates as draft Sales Orders with a custom Estimated_Flag__c field — your team decides the convention before migration runs.

Customer-facing contacts in Total ETO map to Acumatica Contacts linked to the Customer record. Name, email, phone, and title transfer directly. The Contact's Class defaults based on whether the contact is attached to a Customer or Vendor. We also preserve the contact's default communication preferences.

Total ETO's part history (previous project usage) is preserved as Acumatica's Inventory History records linked to each Stock Item. Transaction history for each part shows every receipt, issue, and adjustment with timestamps. The history includes lot numbers, serial numbers, and warehouse locations for full traceability.

Total ETO non-conformance records migrate as Acumatica Cases under the Customer or Project context. We create a Case with the NCR description, linked part, and resolution — your team configures the Cases module workflow for NCR routing before go-live. This ensures traceability and supports continuous improvement processes.

Total ETO users and job owners are resolved by email match against Acumatica user accounts. Unmatched users are flagged before migration — your team either creates Acumatica accounts first or assigns records to a fallback employee. Role and permission sets are not migratable.