Migrate from eFacto ERP to Acumatica

eFacto Customer maps directly to Acumatica Customer master (AR303000 screen). We import the customer code, name, class, status, billing address, shipping address, and primary contact. eFacto customer-specific payment terms map to Acumatica TermsID lookups that we configure before import. Contact-person records migrate to Acumatica's Contact (CR302000) screen and are linked to the parent Customer record.

eFacto Vendor maps to Acumatica Vendor master (AP303000). The vendor code, name, status, address, tax registration ID, and payment terms migrate. Acumatica's Payment Terms must be pre-created as TermsID records matching eFacto's term codes. Remit-to addresses in eFacto become Acumatica Vendor locations. Contact persons on the vendor side migrate as Acumatica Contacts linked to the Vendor record.

eFacto stock items with warehouse tracking become Acumatica Stock Items (IN202000). The item code, description, item type (finished goods, raw material), UOM, and cost layers migrate. eFacto's unit of measure codes map to Acumatica's UOM Schedule defined under IN101000 before the item import. eFacto's stock item attributes (size, color, style) are evaluated for Acumatica matrix-item setup if the item count justifies the schema complexity.

eFacto non-stock items and service items map to Acumatica Non-Stock Items using the same IN202000 screen with Item Type set to Non-Stock. These items are available for purchase and sales but excluded from warehouse tracking. eFacto's service-item flag is preserved as the Non-Stock item type in Acumatica.

eFacto Purchase Orders migrate to Acumatica Purchase Orders (PO301000). The PO number, vendor reference, status, order date, expected delivery date, shipping terms, and branch assignment migrate. Line items include the item code (linked to the Acumatica item record), order quantity, unit cost, and warehouse. eFacto's freight and tax amounts are imported as line-level extras and totals.

eFacto Sales Orders migrate to Acumatica Sales Orders (SO301000). Order number, customer reference, order type, status, date, branch, and payment terms migrate. Line items carry the item code, quantity, unit price, discount, tax, and warehouse. eFacto's order-specific custom fields are captured as Acumatica Usr- custom fields on the SO301000 screen. Back-ordered lines are imported with the original back-order reference.

eFacto Goods Received Notes against purchase orders map to Acumatica Purchase Receipts (PO302000). The receipt number, date, vendor, PO reference, and branch are imported. Received quantities update Acumatica's inventory on-hand for the target warehouse. If eFacto tracks lot or serial numbers at receipt, those migrate to Acumatica's Lot/Serial classes assigned to the item.

eFacto sales invoices migrate to Acumatica AR Invoices (AR301000). Invoice number, customer, invoice date, due date, payment terms, branch, and invoice totals migrate. Line items include item, quantity, unit price, tax, and discount. eFacto invoice adjustments and credit memos migrate as separate AR Adjustment documents in Acumatica. Original eFacto invoice dates are preserved in a custom field for audit continuity.

eFacto vendor invoices and debit memos map to Acumatica Vendor Bills (AP301000). Bill number, vendor, bill date, due date, TermsID, and line amounts migrate. Hold and open statuses are preserved. Prepayments and credit memos are imported as separate AP Adjustment documents. eFacto's GL distribution lines are evaluated against Acumatica's account segments to map eFacto cost centers to Acumatica branches or subaccounts.

eFacto GL accounts map to Acumatica GL Account codes (GL202500). Account number, description, type (Asset, Liability, Equity, Income, Expense), active status, and posting class migrate. eFacto cost center codes map to Acumatica subaccounts or branch segments depending on the Acumatica configuration. Account-based tax categories are assigned to matching Acumatica tax categories if eFacto stores VAT/GST codes on the account.

eFacto journal entries (manual adjustments, recurring entries, opening balances) migrate to Acumatica Journal Transactions (GL301000). Entry date, description, batch reference, and all debit/credit lines with accounts and amounts migrate. Original entry numbers and creation timestamps are preserved in custom fields for audit traceability. Reversing entries in eFacto become Acumatica reversing journal entries with the original-Entry-ID custom field cross-referenced.

eFacto custom fields on any standard entity (Customer, Vendor, Item, Order) are inventoried during the assessment phase. Each eFacto custom field gets an Acumatica Usr-prefixed custom field created on the corresponding Acumatica screen via the Customization Project editor. Field data type is mapped: text to String, number to Decimal, date to Date, pick-list to Acumatica Daclass field with value mapping. Custom field definitions must exist before data import runs.

eFacto's warehouse or location codes map to Acumatica's branch-and-warehouse hierarchy. Each eFacto location becomes an Acumatica Branch (LM101000) with an assigned Warehouse (IN204000). If eFacto uses a flat warehouse structure, we map each warehouse directly to an Acumatica warehouse. Multi-branch setups in eFacto require a pre-migration session to define how eFacto company codes map to Acumatica branches and which branch is set as the default for the GL.

eFacto payment term codes (Net 30, 2/10 Net 30, etc.) do not exist as records in eFacto — they are stored as field values. We extract all unique payment term codes used across customers and vendors, then create matching Acumatica Payment Terms records (CA205000) with the same description, due days, and cash-discount rules. The TermsID on each imported customer and vendor record is then set to the matching Acumatica term.