Migrate from etEngine to Acumatica

etEngine customers map directly to Acumatica customers. The mapping extracts customer name, address, contact details, and tax registration from etEngine's customer record and inserts via Acumatica's Customer master screen. Duplicate customer names are flagged for de-duplication before insertion — Acumatica enforces unique CustomerCD per tenant.

etEngine vendors map 1:1 to Acumatica vendors. Address, payment terms, and tax ID fields transfer directly. etEngine's vendor type classification (domestic vs. international) maps to Acumatica's VendorClass, which gates tax calculation behavior and AP aging reports. Additional fields like 1099 reporting requirements, payment hold status, and primary contact information also map to corresponding Acumatica vendor fields. If etEngine stores multiple payment addresses per vendor, FlitStack maps these to Acumatica's Address sub-records with the primary payment address flagged appropriately.

etEngine inventory items map to Acumatica inventory items. ItemID becomes InventoryCD, Description maps directly, and ItemType (stock vs. non-stock vs. service) maps to Acumatica's ItemClass hierarchy. etEngine's cost layer information transfers to Acumatica's cost bucket if the migration preserves historical valuation.

Open sales orders from etEngine migrate as Acumatica sales orders. Order number becomes OrderNbr, customer lookup resolves via email-to-CustomerCD matching, and order date maps to Acumatica's OrderDate. Order statuses are mapped value-by-value so 'Open' maps to 'Open', 'Fulfilled' to 'Completed', etc.

Sales order lines migrate as sub-records of the Acumatica sales order. Each line links to the parent order via OrderNbr, pulls the InventoryCD from etEngine's item reference, and maps quantity and unit price. Line-level discount amounts transfer as a separate discount detail row in Acumatica.

Open purchase orders migrate to Acumatica's PO module. Vendor lookup resolves against the vendor mapping, and PO date transfers as the OrderDate. Acumatica requires the vendor record to exist before the PO can be inserted — this dependency is resolved in the sequencing step.

PO lines map similarly to sales order lines, linking to the parent PO via OrderNbr. The inventory item reference maps to Acumatica's InventoryCD. Extended cost and quantity transfer as-is; branch-specific warehouse assignments are set based on etEngine's location field or a default branch configuration.

etEngine GL accounts map to Acumatica chart of accounts. Account code structure (segment count) is preserved — if etEngine uses a 4-segment account code, FlitStack configures Acumatica's account segments to match so GL account combinations remain valid after migration. Subaccount segments are also mapped to maintain the full account combination hierarchy. FlitStack validates that all etEngine account codes exist in Acumatica's chart before transactional records insert, flagging any accounts that require creation in the target system first.

etEngine user-defined fields attached to customers, vendors, or inventory items require Acumatica UDF creation before data can populate. FlitStack generates the DAC extension definition (PXString, PXInt, PXDecimal, etc.) based on the etEngine field type, and creates the UDF in Acumatica's customization project before inserting records.

Documents and file attachments linked to customer or order records in etEngine are extracted and reattached to the corresponding Acumatica entity via the NoteDoc DAC. Files are re-uploaded to Acumatica's file storage. The original file name and MIME type are preserved for reference.

etEngine user and owner IDs are resolved by email match against Acumatica's user list. If an Acumatica user account does not exist for a matched email, FlitStack flags the record for owner assignment — records can be assigned to a default Acumatica user or held for manual assignment.