Migrate from Total ETO to Microsoft Dynamics 365 Business Central

Total ETO Projects carry a full lifecycle from quote through delivery with status stages, owner assignment, and WIP visibility. In Dynamics 365 Business Central, Projects module Jobs replicate this structure most directly. In Dynamics 365 Finance and Supply Chain Management, Production Orders are the equivalent manufacturing record. We determine the destination sku during scoping and configure the corresponding project structure, preserving the project number, description, responsible person, and status as of the migration date.

Total ETO BOMs are multi-level, versioned structures that change as engineering change requests arrive during the build phase. We treat each BOM revision as a distinct Production BOM version in Dynamics 365, preserving the parent-component relationships, revision date, and engineering change reference. Flattening BOMs into a single structure at the destination would break downstream production planning. BOM routing (work centers and operations) migrates to the corresponding routing version in Dynamics 365. This is the highest-risk object in the migration and requires explicit BOM-version mapping before any production data moves.

Total ETO Part records carry a complete history trail including prior usage across projects, unit of measure, cost, and supplier link. We map Parts to Dynamics 365 Items with the Standard cost, unit of measure, and vendor cross-reference preserved. The part usage history (which projects used which revision of a part) migrates as Item Ledger Entry history linked to the corresponding Jobs. Any part that was discontinued or marked inactive in Total ETO carries that status into Dynamics 365 to prevent procurement of deprecated parts.

Total ETO Customer records include contact details, address, and account balance. We map these to Dynamics 365 Customer with the open AR balance preserved as a statement balance on the migration date. Customer payment terms and invoice address migrate to the corresponding Dynamics 365 Customer Card fields. If the customer uses QuickBooks or Sage with Total ETO, we scope whether AR balances are already reconciled in the accounting system versus held in Total ETO before deciding on balance transfer scope.

Total ETO Vendor records include purchasing terms, contact information, and any active RFQs or POs referencing specific parts and vendors. We map vendor records directly to Dynamics 365 Vendor with terms and addresses preserved. The open PO linkage to vendor records means vendor import must complete before any PO import to satisfy foreign-key constraints.

Open POs and RFQs in Total ETO represent live procurement commitments with line items referencing specific part numbers and vendors. PO import follows Part master and Vendor import in the migration sequence. Any PO line referencing a part not yet imported goes to an orphaned line queue for manual resolution before the PO import phase begins. Dynamics 365 purchase order status (Open, Released, Completed) maps directly from Total ETO PO status.

Work orders in Total ETO link to Projects and BOMs, tracking manufacturing operations by shop-floor routing. We map work orders to Dynamics 365 Production Orders with the project link preserved and operation sequencing carried into the routing. The operation-to-work-center mapping resolves from Total ETO's routing steps to Dynamics 365 work center capacity records.

NCRs in Total ETO reference specific parts, inspections, and quality issues logged from the shop floor, engineering, or procurement. We map NCRs to Dynamics 365 Quality Journal entries or Quality Orders (depending on sku) as standalone quality records, preserving the association to the relevant Part and Work Order. The NCR disposition (reject, rework, use-as-is) migrates as the Quality Journal resolution code.

Inspection records in Total ETO capture quality check results against parts and link to the inspector. We import inspection results as Quality Log entries tied to the relevant Item and Non-Conformance Record. Inspector assignment, inspection date, and result (pass/fail) migrate as log fields. The inspection template structure in Total ETO maps to the quality item specification in Dynamics 365.

On-hand quantities in Total ETO are tracked by location and linked to projects via reservation. We import inventory quantities, locations, and project reservations as Item Ledger Entries (positive quantity for on-hand) and Warehouse Entries (location-specific). Any negative quantities or over-reserved items are flagged during scoping so the customer can reconcile before import.

Total ETO integrates with QuickBooks, Sage, or Xero rather than maintaining its own GL, which means the Chart of Accounts typically lives in the connected accounting system, not in Total ETO. During scoping we determine whether account structures exist in Total ETO for intercompany transactions or cost allocation. If the customer moves to Dynamics 365 Finance (which includes a full GL), the Chart of Accounts is configured fresh rather than imported, with dimensions set up to match the customer's financial reporting structure.

Total ETO Employee records include time-entry data, labor class, and department. We map employees to Dynamics 365 Human Resources Workers with employment details preserved. The HR module must be enabled in Business Central or Finance before Worker records can accept the employment information. Time entries linked to Projects and Work Orders migrate to the corresponding Job and Production Order time registration.

Time entries in Total ETO are project-based and include clock-in/clock-out data. We import time logs against the corresponding Job (Business Central Projects) or Production Order (Finance). The entry date, hours, and worker assignment map directly. Time entries without a matching Job or Production Order go to a queue for resolution before import.

Total ETO stores documents linked to Projects, Parts, and Quality Records. We extract document references and file paths from the database. Actual file migration depends on the destination's document management capability. In Business Central, document attachments link via the Document Handling feature. In Finance, SharePoint integration or Teams attachments handle file storage. We preserve the entity-reference linkage so documents attach to the correct record at the destination.